A Whole Game in One File? | Code Review with Anton

Added: 2026-05-09

[00:00:00]So, we're gathered here today to review the game and the code of one of our members called Spike. And we've got ourselves a nice 5,000 lines of C code, one file apart from the renderer.

[00:00:17]Renderer is another 3K because it's Vulcan. It's verbose. But here, we're going to review mostly gameplay code and take a look at how it how it generally functions. And we're going to start off by looking at the game itself.

[00:00:32]So, thanks a lot for Spike for submitting the code for the review.

[00:00:36]Thanks a lot for Anton who's showing up to critic the code. Critique code >> and I need to have my tea to >> without but this was German and critique was the French.

[00:00:54]>> I don't even know man. It's just European. All of Europe's just one.

[00:00:58]>> It's European language.

[00:01:00]>> It's European language.

[00:01:01]>> What's the language? It's European.

[00:01:05]>> All right. Uh so let me first share the screen. Here is repository. It's actually public. So everybody can go and take a look.

[00:01:16]>> Follow along.

[00:01:18]>> Follow along. Start. Of course, I am not logged in because like I so I need to be signed. But please >> stars, >> please start this repository.

[00:01:27]>> Star and subscribe.

[00:01:29]>> And here there's a bit of a read me.

[00:01:34]The game is a suck band style game, meaning we will have uh as I will pull this over here. Here we already set up in the in the level that showcases some of the features, right? We're not going to spend too much time on walking through the overlord overworld and how how the game works. It's a sooan game with lasers. You see that there's this one lighter cube, which is the first one, and the other one is a backpack.

[00:02:08]And I can walk through here and stop the lasers from beaming. And my goal teleported. And my goal is to, as usual in Sakaban game, move around the objects on the scene to make something happen and solve solve the puzzles. And since I have a backpack, I am constrained in my movements because you can, as we'll also see in a sec, it's um it's a 3D game. It's a 3D plane.

[00:02:44]Like it's not only 2D. So, I can't now turn down. You see?

[00:02:50]>> See the small wiggle? The side wiggle.

[00:02:52]>> Yeah, it's frustrating.

[00:02:54]>> But here, >> you can do it there. Yeah, >> here I can. So, >> tricky.

[00:02:59]>> And now, now I can go to a special mode debug pines.

[00:03:10]It was controlclick.

[00:03:13]Hi everyone. Let me take a break to thank members of the show who made this conversation possible. Members get earlier access to videos, including longer unedited footage from live streams, as well as they're invited to our private Discord server. If you want to support the show, there is no better way than becoming a member on YouTube or Patreon. Thank you so much.

[00:03:37]I will move it up here.

[00:03:38]>> What's the goal, by the way?

[00:03:42]So, normally you have a you start off from putting the box into a square like a proper soccer game. Yeah.

[00:03:48]>> And now you do the same thing with lasers and you need to put the lasers shoot the lasers to the proper position.

[00:03:57]>> But where are they? Like in this level, where do they go? Where are they supposed to go >> here?

[00:04:03]This is a this is a debug level >> made especially for us for this stream.

[00:04:10]Oh, okay.

[00:04:11]>> So, got to got to appreciate it. And uh this is a debug level that showcases some of the things like here you have the ability to take the take the objects and put them on the level. And I can even uh I can even add things to remove things from the board like you see >> built in level editor.

[00:04:36]>> Removing cubes >> hard pivot to Minecraft.

[00:04:41]I can keep the mouse button and terrorize the entire level.

[00:04:47]>> Okay. Okay.

[00:04:50]>> Even enter a special view mode here.

[00:04:54]>> Okay.

[00:04:55]>> To show what it's really like.

[00:04:58]>> Oh, is that like the actual game game?

[00:05:01]>> Yes.

[00:05:03]I unfortunately broke it because I spammed my keyboard because I don't remember the key bindings. Well, >> well, I think we got the gist of it. Or did you want to show off some other bits before we dive into code?

[00:05:17]>> No, this was pretty much it. Uh, >> okay.

[00:05:20]>> We we're not going to be covering like we need to focus on something. We're not covering uh rendering part at all. We have one file.

[00:05:29]>> We have one file. I can show later on the renderer at the end, but it's a lot of Vulcan code. So um what my plan is given what we saw right given what we expect this sock game to be um what first of all what do you expect from the code what should be there in terms of like state management or like resource management what would you expect to be if it's going to be uh in a C language >> and it's one file >> and Then we're going to go through and see like some parts, some bits of it. Of course, we can't be diving too much, right?

[00:06:14]>> Yeah. I mean, you can fit a lot into one file.

[00:06:17]>> Oh, yeah. Oh, yeah.

[00:06:18]>> There's a lot there's a lot of room in there. You can you can put whole games in a file if you really know how to pack them, right?

[00:06:26]>> So, this is as m as much as it's possible. This game I actually didn't didn't show it off properly. Uh, so this game has a overworld in the style of I messed up something and I can't really boot up the game again. Uh, so this game has a overworld, meaning you go in this like meta level and you can drop into a level and then do the puzzle then and then you go back up and you go through this, right? So it has these two modes of playing like there's an a a meta level called overworld >> in the same fashion as order of sinking star from Jonathan Blow now >> or like games like Baba you where you have a bit of an like a overview where you can walk but by more >> exactly >> riptop serious >> by the way how do you pronounce serious >> I think it should be serious >> do you know what it is >> unless it's kus If we're talking in European language, do you know what it is?

[00:07:37]>> No idea.

[00:07:40]>> So now, now I can I can't remember the exact name, but it has like a it's like when you have a biological categorization of uh different >> Yeah. Like tonomies kind of thing.

[00:07:54]>> Yeah. Yeah. Yeah. Yeah.

[00:07:55]>> And you have under species there's something that starts with a G. Do you remember >> genus?

[00:08:03]>> So it's a genus of cactus.

[00:08:07]Absolutely unrelated.

[00:08:10]>> Okay.

[00:08:11]>> Toan.

[00:08:13]>> I mean unless it's this is like a reveal you haven't actually gotten to in the end.

[00:08:17]>> That might be it.

[00:08:19]>> Yeah.

[00:08:21]And all the levels I saw I looked at the code a little bit. It's like all the level data and stuff is in data files.

[00:08:26]So sometimes >> people you were not supposed to what?

[00:08:31]>> No, no. I just downloaded the zip cuz I was like, "Oh, I don't know if you're if I'm going to drive the code or you." So I just downloaded the zip and looked at the directory structure.

[00:08:42]So all I know is we're not looking at like level code cuz sometimes when people do simple games, they just like shove the level in line into the source as well.

[00:08:52]So that's why it's so small cuz there's a lot of levels but they're they're separate.

[00:08:56]>> No, no, no. We we are serious here.

[00:08:58]Okay. We're serious.

[00:09:00]>> Serious.

[00:09:05]>> All right. Uh tell me what are your expectations? Like what do you expect to see on the on more a detailed level?

[00:09:12]Like it's Sakaban game. What do you plan to see?

[00:09:16]>> Need things man. There's going to be things. And I think the the question is going to be is it like a densely stored 2D board full of stuff or like 3D board or is it more just like uh just a pile of entities and every cube is an entity cuz you can kind of go either way. There's not that many cubes in the end. So you can just shove them all in and then deal with that. Or you can just do like X, you know, width by height, maybe a little bit of height, little depth, I guess in this case.

[00:09:48]um that gets you easier collision detection right out the gate kind of thing, but then you have to worry with fixed sizes and and so forth. So, I don't know that that's kind of what I would probably start with if it was me.

[00:10:02]Um are we going to try to do code rating like we did for the other >> rating? What's code?

[00:10:09]>> Like when we rate the code, we have to like rate the code >> rating >> because it's a review, right? We got to know like is this going to be is this going to pass? Is it going to be rejected? which which PRs are going to be blocked.

[00:10:20]>> Yeah, but we have only one file. So, it's going to be tricky like how we're going to have categories like we can't be just like reviewing one.

[00:10:27]>> We can just if defaf any code that is is blocked just if defaf it out. No, I'm just kidding.

[00:10:37]Um, given that we're we're like rapidly transitioning into the AI era, I propose that the measurement of of code review is how many clawed hours a piece of code would take to write. So we like if it's really >> what >> high quality code it will take like many clawed hours and if it's like ah you know we don't need this then it's like low clot hours. What do you think about that metric?

[00:11:03]But you mean like verbosity or?

[00:11:06]>> No, just like quality. It's like if it's good code, it it presumably it can't be written by Claude very quickly. It's obvious everything can be written by Claude already. Like we're already past that, right? So every but it's a question of how long would it take Claude to write. So like the best quality code would take infinity time because it just can't write it and then it sort of goes down from there.

[00:11:28]>> Okay, >> it's like man hours except it's clawed hours. Okay, so let's do it like this.

[00:11:33]We're going to measure this in clock hours. Uh we're going to review it and at some point we're going to be like, okay, we've seen a system, right?

[00:11:42]>> So we're going to do the rating and then we're going to end up with a couple like at least three. Three is a magic number.

[00:11:49]Okay, we can't have less. Like that's it has to be three >> and uh at least three. So then we have like three things scored in clawed hours.

[00:12:02]And probably people would be like but which which model actually you know like it depends but uh okay oh somebody is suggesting Anton hours it's good we should keep that and see see what happens next. Maybe maybe this one claw hours.

[00:12:18]>> I have to put put my money where my mouth is if I do that.

[00:12:22]>> Yeah.

[00:12:23]>> All right.

[00:12:25]I wrote like just a couple of notes. Oh, these are yours would be like, hey, first like that's what I've done like to to prepare a little bit like I got handed the code and I'm like okay what is this right like where do I go? Yeah.

[00:12:40]>> So, uh since like it's not a PR that we're reviewing but like an entire thing, uh you need to understand like what is the what is the place where people decided to split the files and like some sort of modules and whatever here.

[00:12:54]>> Is that how you usually review things?

[00:12:55]Is that like you start high level >> if you like I got I got couple of submissions like four or five I think recently. Uh and I needed to be like hey what is it right? Like first of all run the thing see what is it doing >> so that I know like from the what it's aiming to do and then I try to map this >> to to what I see which is like the division split. I just go line by line.

[00:13:23]Like I'm like, "Oh, what's up with that first line?" And then I just go in. I just follow the >> I just find Maine and then I go I'm like, "All right, let's see where this >> find you need to have this like structure of like where do I start?"

[00:13:39]Like, >> yeah.

[00:13:41]>> So quick quick look.

[00:13:43]>> Yes, >> this might be not not visible and I don't know how to make it bigger. Um, so one build script, >> right?

[00:13:54]>> Good.

[00:13:54]>> Yeah.

[00:13:55]>> And this is because it's because it's uh uh Vulcan, >> we're compiling our shaders.

[00:14:01]>> Sad times. Sad times.

[00:14:04]>> Okay.

[00:14:04]>> It's going to be mostly in in a handmade fashion.

[00:14:09]>> Let's say compilation. You put your basically couple of >> Yeah. Just go for it.

[00:14:18]>> And bye-bye. Right.

[00:14:20]>> No logo, 360, no scope, no mistakes.

[00:14:23]Let's go.

[00:14:26]>> We have a render series.

[00:14:29]Actually, we have this this guy here.

[00:14:32]So, this gives us a bit of an interface for what's going to happen, right?

[00:14:36]>> Yeah.

[00:14:37]>> We have two things that are related to Vulcan submit frame Vulcan draw. This is this is the render part. There's game redraw and this is for the resizing.

[00:14:48]>> Mhm.

[00:14:49]>> And there are two things that we're going to focus on kind of uh game initialize which is the startup code and then game frame expected.

[00:14:59]>> I appreciate the lack of the lack of variable names. I'm feeling it.

[00:15:04]>> Yeah, I know what that is. That's going to be the time. But that's like a bold move. It's like yeah, just give it a double. Why not? Vulcan submit frame bool.

[00:15:14]>> That one not so much. Let's let's let's let's play a quick game of guess the bull. Um what do you think the bull is?

[00:15:23]>> It's going to be some sort of force like >> force something >> force parameter do is I don't know what we can force here but >> I think it's going to be initialize.

[00:15:36]>> Oh like cuz there's no Vulcan in it. So, I'm wondering if it's just like a knit on first frame kind of pattern or like restart some kind of restart or but then it would have been first. It would have been the first arc. I don't know. I'm gonna put my money on something like reinit or innit or restart cuz we get like n draw commands.

[00:15:57]We get int and then camera.

[00:16:03]>> The int is probably the number of draw commands.

[00:16:08]Ah, because it's a C. Yeah. Yeah. Yeah.

[00:16:10]So, this is an array. This is camera.

[00:16:13]So, for the for the transformations and >> the pool is mysterious, man. It's like a Yeah, maybe it has something to do with the camera.

[00:16:21]>> Yeah. Okay.

[00:16:23]>> Uh, should we do then the quick check?

[00:16:27]Oh, there is a Vulcan initialized. Never mind. It's probably not in.

[00:16:31]>> This is Vulcan bridge.

[00:16:32]>> Chat, what do you think? What's the bull What's the bull do?

[00:16:36]M >> we can move on and leave it as a cliffhanger for later. Maybe we'll figure it out from the game.

[00:16:44]>> No, I want to know now.

[00:16:46]>> You want to know now? Impatient.

[00:16:49]>> What was the Vulcan? Submit.

[00:16:52]>> Submit.

[00:16:53]>> Yeah.

[00:16:58]>> Render models. Unexpected.

[00:17:03]Highly unexpected.

[00:17:06]somewhat expected for for for Vulcan cuz it's like you make all this stuff and then you're like, "Oh god, I didn't this is just I got to do this thing sometimes. All right, screw it." And you've been wrestling with Vulcan for like 3 hours and you got to go to bed and you didn't get anything done. So you're like, "Fuck it, random models.

[00:17:23]Let's go." That's my experience with Vulcan.

[00:17:28]>> Vulcan is a bad language for hobby development. That's what I not language API. That's what I really I tried to mess with it for like several years.

[00:17:37]>> Do experimental shaders. Yeah. Yeah.

[00:17:39]That's what this is what I'm saying.

[00:17:40]It's like >> cuz you're like, "Oh, I didn't make my PSO and I need to make a whole new PSO, which means >> Vulcan, >> calm down. Calm down. Close the file.

[00:17:53]>> Close the file. I've got to go away now." Okay. Got Vulcan PTSD. Vulcan was supposed to save everyone.

[00:18:00]>> No. No. No. We don't. We don't go. We don't go there. We don't go there. Okay.

[00:18:03]Okay. We don't go there. Game play code.

[00:18:09]>> Okay.

[00:18:09]>> Okay. Okay.

[00:18:10]>> Uh I I suddenly found myself here >> in time. Yeah. Just got out. It just got out.

[00:18:15]>> Open the first door that you saw.

[00:18:17]>> So you can rant here. I would say way too many characters. Way too many.

[00:18:24]>> You ate. You're You're more of a I ate you ate kind of guy.

[00:18:28]>> I am like this.

[00:18:30]>> Okay.

[00:18:31]I like >> um I've kind of I I've entered inner peace and I I can even go like my code is now mixed. So I have UA and A and U8 U and A T and I'm like yeah it's all good. They're all the same. They're alias in my >> family. They're family.

[00:18:47]>> They love each other.

[00:18:48]>> Pick whichever one looks better in the context.

[00:18:54]>> Here my question, my immediate question.

[00:18:57]I see this as a higher level uh uh not in the language not like a quality but programmer where where are my operations man where my like pluses >> see man you don't you don't get operators in C >> I know >> but if you use the clang extension you could so there's a clang vector extension that will give you >> the glsl vector types in C I think it's C99 extension that. But then it's like it starts to feel like uh if you're doing C99 with extensions, you're basically doing C++. You're just sort of in self-denial at that point. Like it's >> No, maybe you want to have like 40% quicker compile times.

[00:19:46]>> Yeah, that's true. That's probably true.

[00:19:48]>> And you don't want to be tempted by >> you want to resist the urges. Uh I think it doesn't give you int or bull types I'm guessing. I think it's just probably floats. Maybe it gives you ints. I don't know. Um yeah, the operators are going to be functions, man. Not going to get This is basically the reason I don't use C in practice. I end up using C++ basically for operator overloads on vector types. That's like 90% of why I use C++ because I want to write math code that is both easier to read and also it would I I do a lot of cross compile. not a lot, but I do some cross compiling between um C++ and GLSL or whatever shader language is. And so I just like to include the same exact code on the CPU and GPU, especially for things like random numbers and that kind of stuff. So having operator syntax is like pretty key for that. Um also just hate typing mole add and all that. But I don't know, it's a personal thing.

[00:20:50]I uh somebody mentioned that I my my mic is lower and your yours is higher. The only thing I can do is lower Anton's mic. So I did that and uh yeah I cannot I cannot put more power. I can only scream.

[00:21:07]I >> So people my my take here would it mean then like add should be here like a function definition like at least declaration shouldn't be here.

[00:21:20]>> I mean you never know if you're going to need ad. You might not need ad for all of these. Just just do it as you go, man.

[00:21:26]>> Really?

[00:21:26]>> We'll find we'll find out. We'll find out.

[00:21:30]No, I So my guess just reading from this since you know I think Spike mentioned this is like he's just starting out with this this feels like following along from Handmade Hero kind of vibe and so I suspect this is the beginnings of like building out that library, right? Cuz um it's got a couple of these but not like all of them. And so I suspect it's like all right, let's start building out my log cabin vector library. and just hasn't gotten to the the operators yet.

[00:21:59]But we shall see. We'll find out.

[00:22:01]>> We shall see.

[00:22:03]>> Maybe he's like a raw dog vector kind of guy and just goes goes for it with with the raw member variables everywhere.

[00:22:09]We'll all right this was this was types and you remember that we had also world states strcts and apart from these two separate files we just serious C. Okay.

[00:22:23]>> All right. Should we check the strruct header or do should we just go straight to the to serious?

[00:22:29]>> I think we should check this and then >> let's do it. Let's find out.

[00:22:32]>> Spend spend all night there.

[00:22:36]>> Okay.

[00:22:36]>> Okay.

[00:22:38]>> So, >> Windows is defining void to void.

[00:22:42]>> No idea.

[00:22:43]>> Windows. I have no idea.

[00:22:45]>> Windows naughty naughty Windows.

[00:22:48]>> What's going on? Anon. Anon. What is going on?

[00:22:51]>> So, Windows.h. So, somebody included Windows.h. But this is a little bit sketchy because like why did we include Windows.h somewhere? That should be only inside the wind32. So, I guess maybe this goes into the >> who included it.

[00:23:05]>> Serious.

[00:23:06]>> And I see the comment temporary next to it.

[00:23:10]>> Yeah. Yeah. There it is.

[00:23:12]>> For debug. Oh, no. Um, yeah. So, Windows defines all manner of crap and it just like trips you up. Like it defines like rectangle, I think. So, then you you inevitably someone tries to make a class called wrecked or rectangle and then you get like these Byzantine compile errors because it's a Windows macro and you're just like, what is happening?

[00:23:37]So, anyway, so people just undef stuff, but that's why you don't want to include Windows.h anywhere. Um, all right. So we got some platform render handles. Okay.

[00:23:50]>> So this one this one actually is a big one. So we might not need to go through all of it. There's one thing here that is for me skeptical and I need advice from >> Anton. Okay.

[00:24:01]>> Sure.

[00:24:02]>> So let's go. So we have couple of strcts. We go there.

[00:24:08]>> Sprite ID perfectly normal.

[00:24:11]Understandable. Cube model.

[00:24:14]draw command sprite ID S type this is like okay we don't do we don't do rendering so we're not going to spend too much time here we have camera yes okay that's all that's more our zone but generally speaking we'll come back on the gameplay code I think and then we go tick input and then I do papa >> oh okay >> papa >> okay >> papa You're okay.

[00:24:47]>> So this to me >> uh-huh >> is wasteful in terms of memory. you have a lot all of them and you share bool which is like one bite eight bits and you can have this packed into bits separately right that's one case >> and then >> maybe because I'm just too library skewed but at this point like it feels like hey we're doing our framework and we're defining everything right >> if you were to do your project If you're doing this handmade way, that's that's the way to go, right? You need to build yourself everything, right?

[00:25:30]>> But at the same time, where would you go for a library to handle some of this stuff?

[00:25:39]>> You mean if you're building the library for where you pull this kind of stuff out?

[00:25:44]where if you if you go for a project, right, would you consider doing things like, okay, hey, I'm going to need this and that library and I'm going to so to avoid doing this, right?

[00:25:59]>> Yeah.

[00:26:00]>> Or you're going, hey, I need all of it and I'm going to even handcode the nine press case for my tick input. That's that's like to at some point you need to stop because like whatever you're doing is not going to ship if you're like I actually need like 16 press case for like this very particular specific platform. So for me it's like when do you say okay uh I'm not going to bother with this until I reach this case.

[00:26:31]Well I mean there's like two separate things going on. One is that this is wrapping the raw input coming from Windows, right? So, it's sort of like repackaging it as a massive bull struck.

[00:26:45]Um, that's not a good idea. This is this is sub one hour claude code.

[00:26:56]Um, so but like forgetting the bid packing side of it, which you can do to save space, but it probably won't matter in this case. Um, often you want to write stuff like, you know, when when you're writing especially debug or or simple code, you're like, oh, if the user pressed something between 0 and 9, take like the key they pressed, subtract zero, and that's like your index between 0 and 9.

[00:27:24]So that's really useful for like hotkeys or shortcuts or or if you want to do really simple text input, you just say, oh, what's the in what's the letter? Oh, is it a keystroke? Subtract like ask key A. And now that's like my character code or whatever.

[00:27:40]So having it with bulls precludes you from being able to do these kind of like index based things around um the key presses. So if you look at like SDL or GLFW or any of these frameworks, the reason they define all the keys as enums is because there's like naturally useful ranges in there where you can just be like, oh, if I know the key presses within this range, subtract the beginning of the range and now that gives me the index inside the range. And you can do some nice coding compaction based on that. But this is nice for autocomplete. You're like, what what's it called? Is it SDLKM or is it SD keym?

[00:28:18]I never know, right? And so this would be like inputs dot and then it's like which key do you want? M press. I got it. So I think it's coming from that vibe where it's like I don't want to remember no enums. I just want it documented. I don't know man. You do you. But until you until you find like yourself feeling like man what I really want to know is it like between zero and nine then you start anything programmatic. Um but in terms of like should you wrap it? I I think it's actually not a bad idea to wrap it somehow. Even if you're using something like SDL um just pragmatically, I've had projects that sort of lived on for years and then I had to swap from GLFW to SDL or from SDL to GLFW or to something else and it's convenient to just be like, yeah, yeah, yeah.

[00:29:07]So this is always as an example given on the internet and I'm like bro if you're serious about the project and you're like 3 years in and you have like a production case and you have clients like are you going to like switch from GLFW to SCL like at this point like I I always like for maybe hobby projects or like something you know >> this I understand but >> this case like always like Oh, it's going to be so nice. We're going to draw the UML diagram. It's going to be an abstract interface and it's going to replace like >> you don't need the abstract interface, but it's useful to know like SDL is huge. DFW is huge and if your app is only going to use a tiny portion of it.

[00:29:54]Um, I mean, yeah, it's questionable. Uh I guess all I'll say is I have projects in which I you like ages ago. Let's say I take like a project for from 10 years ago or something like that and it's written on top of SDL2 and it's got SDL2 code everywhere and the key strcts are using SDL key enums and the this sound is the SDL sound. I'm like ah this project sucks man. I don't want to like I never want to revive that, right?

[00:30:24]Because you're like, "Oh, I have to >> get So, if I ever want to modernize some piece of that code, it requires me to to fix up a lot of SDL stuff." Whereas, if it was put away, I just be like, "Oh, I'll just fix, you know, my input.h or my input CP or whatever." And then it's fine. And also, SDL and GLFW are kind of like allin-one things typically, right? So you got your graphics, SDL also have sound, you got your input, but if you ever want to like put it on another platform where those are not part of the same library, then having your own platform layer is handy.

[00:31:00]It does feel like wrapping a wrapper, but I don't know. I think for longevity, it's not a bad idea. I just wouldn't quite do it like this. Uh, now I'm gonna be sneaky because I've seen parts of the code and I'm going to talk a little bit about things that we didn't didn't show yet. But this stick input is actually a parameter to G game frame.

[00:31:30]>> Okay.

[00:31:31]>> So, it's not like there's an instance and you switch what's pressed.

[00:31:36]It's actually being copied every time there's an invocation for a frame.

[00:31:41]Okay, thoughts.

[00:31:44]>> It's fine. It's not going to kill anyone.

[00:31:47]>> It's huge, but there's one tick per frame, right? Presumably.

[00:31:52]>> So, yeah, it's a whole pile of stuff on the stack, but it's all fine. You have a lot of stack space. It's not a big deal.

[00:32:00]Not a big deal.

[00:32:01]>> Damn. I expected like a huge Ah, that's sketchy. Ah, >> I mean, just pass it by pointer if you you don't want to. Yeah, it's okay.

[00:32:11]These are not the things that will sink you.

[00:32:17]These are these are shallow bugs or or shallow kind of like issues, the stylistic issues.

[00:32:26]Okay. Um, Windows.h on the other hand, like that man, you include that, that'll get you.

[00:32:35]You don't know what's coming in with that. Oh, for macro.

[00:32:40]>> Why do you why do you say that? Uh meaning you I know that's like a easy thing to say.

[00:32:51]First of all, Windows.h has been the go-to way of interfacing with Windows like yeah >> two decades ago, right? Since then there's a special flag called like win and mean lean and mean.

[00:33:07]>> Lean and mean. Yeah. Yeah. Yeah. Yeah.

[00:33:08]>> Yeah. It's like oh now it's going to be better.

[00:33:10]>> But at the same time the Windows 8 was split into various headers >> like manip or whatever depending on what your use case right >> sure >> but are you saying including any of them is very sketchy?

[00:33:25]>> No you have to include them somewhere.

[00:33:27]>> Yeah. You just have to include them in their own little like self-contained bubble so that nobody else includes them. Like that's the first thing you want to wrap is is that stuff cuz I mean Windows.h just has everything in it which is convenient because you know you kind of just want everything and you don't want to always look through the docs and be like oh I need to get this Windows H file. It's like okay I get it. But it means that if you put it into a major header or your main file, you're now incurring like a bunch of crap into every file and it will mess up. It will come with surprising gotchas and stuff and uh I guess lean means probably better. So I I just I make it a point to be like, okay, I would only include that inside win32 serious or something and just only keep it there.

[00:34:16]>> Never let it leak out. not in the like crossplatform part. Uh >> yeah, just the platform layer for wind32. Never like bleed it out of its its own file. Ideally, just one file or whatever just so that it only pollutes the one place. And if I search codebase for Windows.h there should be exactly one file that includes it is sort of my my general policy. That's I mean >> that's the case because here's here's Q is commented out and the other one is not commented out.

[00:34:47]>> Another one I saw the is that oh the one in series is commented out. Yeah. Good.

[00:34:51]So there you go.

[00:34:51]>> So basically that's it.

[00:34:53]>> Yeah.

[00:34:53]>> It's also a bit easier if you have two files like >> those are in those are globals though.

[00:35:00]That's a little bit weird.

[00:35:01]>> Oh I guess it is global window handle.

[00:35:03]Okay. All right.

[00:35:05]Uh, that's probably why it's leaking out for debug.

[00:35:10]>> Also, was bleeded out a reference to I think Linking Park or >> No, just just imagine it spewing from >> Okay. From from a tightly contained place.

[00:35:25]>> I need your thoughts on this one.

[00:35:27]>> Hey man, I wrote a loop macro for my old projects. I'm I'm all for it. Try it out. See how it goes.

[00:35:33]>> I'm all for it.

[00:35:36]Um, I think in practice this doesn't play out. I think it makes things harder to read, but I think it's fun to play with.

[00:35:45]>> Like over time or what? Like when the project or what?

[00:35:50]>> No, just like over time. Like I I thought this was cool back in the day and then cuz I kept typing it over and over and over. But then what I tend to find is that there's enough of them that are different uh as you start doing more and more complicated for loops uh and then it becomes weird cuz now you have your simple for loops and your complicated ones and then it's like why do I have two things you know so that's kind of same same problem I have with like for each I've tried to use for each in all its C++ incarnations like tons of times and every time I write it and I'm like, "Oh yeah, I just want to iterate the stuff and like call update on it or whatever." Great. And then every time something is like, "Oh, I need the index of the item." And it's like, "Damn it, now I have to change it to a standard loop." Or it's like, "Oh, but actually I want to skip some items." It's like, "Damn it."

[00:36:50]So yeah, basically I just almost never use that at this point unless I'm like you know you using some kind of standard container cuz I'm being fast and loose and I'm like I have no idea how to iterate a standard hashmap. Let's just do it and just all I need is to print things out or whatever. But generally I just write the raw for loops because of that.

[00:37:13]>> Okay, >> direction. Okay, now this is where I'm going to uh stop scrolling and jump directly to main because I think it >> but these are important.

[00:37:26]>> These are useful.

[00:37:27]>> Yes, but there's a lot of them.

[00:37:29]>> Yes, there's a lot of Okay, but let me glance at them at least so that I know what we're dealing with.

[00:37:33]>> Okay, >> just scroll down and I'll just sort of >> Okay, >> take take a slow trip down to Maine and I'll narrate the slow trip with with things that I'm that I'm spotting. not main it's win main and it's different file but okay >> okay okay okay >> let's do it so type dev enum since it's since it's a c >> we don't know what it is yet >> see we'll see on the at the end >> see you on the other side >> I guess zero >> and this is what you meant right like you're going to say here >> this >> and now you can do like source white minus >> source red and be like >> that kind of stuff is good for keys as well. Yeah.

[00:38:16]>> Okay.

[00:38:16]>> So, >> so I saw the direction. Can I see the direction real quick?

[00:38:22]>> Can we just start from the very Yeah. No direction negative one is already giving me like a red flag of like better watch out for direction. Anytime I have to compare things to negative 1, it's like why is north zero? Probably cuz it's in an array and they wanted to use zero.

[00:38:37]We'll find out. I'd rather burn an array slot for the zero slot than than deal with negative one these days. But but I get it. All right, you can keep scrolling. I'll just keep talking while you scroll.

[00:38:48]>> No, actually now we have like direction >> and then we have up and down >> because we in 3D, right?

[00:38:57]>> Right.

[00:38:58]>> Okay. like this we need to remember but it's not 2D because sometimes up it would be up but like it's actually >> dimension >> and I am okay so when I see this now uh >> in my like proprietary code at work >> I'm like hey can we not express an invalid state and get away with having an enum for a state that's very often like you have an enum for something that's related to the state. Can we just like not express an invalid state anyway and have it always be valid?

[00:39:40]>> Meaning like skipping the non or like non-existent or invalid things for the things that cannot be invalid through the lifetime of our application.

[00:39:50]>> So here it's like a sentinel value but maybe here >> like what if what if we never had this value to begin with? Yeah, that one that one that's why I'm saying in particular for direction I think I'm a little bit concerned.

[00:40:04]We'll see. We'll see how it's used.

[00:40:06]Also, I I think I prefer to put those kind of things at the end, but it depends. So, like I would make no direction be like six or something or I would add like direction count. Yeah.

[00:40:21]Yeah. One sec. Let me let the cat out.

[00:40:23]Cat is trying to escape. Let the cat Let the cat out of the box.

[00:40:30]Oh, look at this. Anton has like a steering wheel wheel.

[00:40:36]Yeah. Like the reason I like to Oh, yeah. Yeah. Yeah. Yeah. No, I thought this would happen. Yeah. It's kind of like it's basically used as a value for I I don't know which way I'm going. I didn't get a response. That kind of thing.

[00:40:50]>> Yeah. But like you cannot be rotated in a direction of no direction, right? So like even if you don't know then you can signify this with an error. It was with an invalid state and like hey your call didn't succeed.

[00:41:07]>> Yes.

[00:41:08]>> But as far as the values are whenever you have them there should be >> you don't like it >> functional. At least I that's my like give if you have a system where you cannot be in the invalid state why would you add another thing that you need to always keep in mind and always check for >> and your entire application should never ever use it anyway. That's >> I think I I agree with you at a high level, but when I'm going fast, sometimes I'm like, >> "No direction. Let's try it. Maybe it'll work this time. Come on. One more try, bro. Going fast." Yeah, I'm going fast.

[00:41:53]Sometimes you don't know. But yeah, I think you're right. It's It's very often doesn't pan out. So, we'll find out through the code.

[00:42:00]>> So, for example, here if whatever happens here, here maybe it always sets the direction. Let's say go else we here but we never hit this one. We actually go next section. Let's say that there will be a case where we exit this function with no direction. Now we need to check in whatever was calling this function.

[00:42:22]>> Totally.

[00:42:23]>> All right.

[00:42:27]Uh where are we?

[00:42:29]>> No color >> tile type. It was style type each enum.

[00:42:33]>> Mhm. Then we go enam color. No color again. Skeptical.

[00:42:40]>> Not a fan.

[00:42:41]>> Let's leave that down. Struct.

[00:42:46]Okay.

[00:42:48]>> This is green. I'm assuming green laser.

[00:42:50]And Spike told me lasers are new. Okay.

[00:42:54]So there might be some rough edges lasers.

[00:42:57]>> So it's only green lasers that do things.

[00:42:59]>> Yeah, exactly. No, actually they have No, they have different >> um mechanics. Green one is the one that teleports you.

[00:43:10]>> You can you can teleport.

[00:43:12]>> The other ones uh do things with the um >> I see >> with the mirrors.

[00:43:18]>> Okay.

[00:43:19]>> Uh reset info.

[00:43:24]>> Mhm.

[00:43:25]>> Reset blocks which aren't currently active in the game. Chords are integer coordinates of the entity position known as floating point world space likewise direction six direction past renderer.

[00:43:38]Uh since since since since Spike mentioned world space I have a question.

[00:43:44]So if you are in gamedev world, >> you have various coordinate systems >> and often you represent a position or rotation um through a vector.

[00:43:59]>> So you never know what is the coordinate system of a given vector because it just floats. And if you're using an engine like Unity or something, there are some sort of conventions that you can adapt.

[00:44:14]If you're making something from scratch, uh I would expect that there is an answer for a user of the code like developer to know at what coordinate system we are at any point in time either through a convention of like prefixing names or whatever or something. What's your take on this?

[00:44:37]>> Yeah, you have to have that. It will save you save you time in the end code.

[00:44:43]Would you encode it in a type or something or >> No, no, no. Never the type you because a space is not really a type, but definitely a prefix or a suffix um is is sort of my convention. So I follow like what's called the domino convention.

[00:44:59]Um so if you have for example like a typical do you know about the domino convention for multiplication? Okay. So, so you have a bunch of m so typically in a game or any 3D application uh eventually you render in something called clip well your graphics will end up in clip space or NDC or all these things right and so it's something like at a high level you have your projection matrix then your camera matrix and then like your model matrix so sometimes people call model view projector projection not to be confused with model view controller different place. We have model view projection up in here.

[00:45:42]>> To be more confusing, you often spell it out as PVM because you need to change the direction.

[00:45:49]>> Yeah. So, so here's what I would propose to you if you want to like type really quickly and then you will see the light immediately. So, you're going to have some kind of matrix which is called like projection, right? So, or maybe I can can I hijack this screen briefly or do you want to do you want to type cuz I'll this will save you time. This is a good convention.

[00:46:09]>> Let me type like one one.

[00:46:13]>> So, just like get a bit of blank space and then I'll show you some kind of like how this arrives. So, so you're going to have a projection matrix somewhere, right? So, let's call that projection for now cuz you're like typed one like this.

[00:46:26]>> Yeah, let's just call it projection.

[00:46:30]Right? You're going to have uh a mat for uh view and then you're going to have another mat 4 which is like model.

[00:46:39]And so typically model is going to be like where's my model in world space and view is like how do you go from you know world to view and then projections like what's my FOV and all these things right? But notice you have no freaking clue what is it view is it is that like the position of my camera in world space or is that the matrix that takes me from world space into the view I don't know and that's what you're talking about right and then you have position which is like let's say it's like a vertex inside your model or something right or like a point inside your model so now leave that there as a point as a place of shame and then I will type the correct convention for you below it's going to be more wordy but you have matt for projection from view like projection underscore from view and then view becomes uh matt for view from world and then matt 4 world from model and then lastly vec 4 model position or Pause.

[00:47:52]Right. So now using those domino pieces I just gave you, can you construct me the model position in projection space?

[00:48:04]>> Of course.

[00:48:07]But how do I need to name it?

[00:48:09]>> So now you call it model projection.

[00:48:13]>> Ah because we we we have the suffix.

[00:48:16]>> Yeah.

[00:48:20]Okay, there you go.

[00:48:30]I think I see the pattern.

[00:48:32]>> Yeah, >> raw model.

[00:48:38]>> Congratulations. You're now a graphics programmer. You'll never make a mistake with spaces ever again. Like, and you've used zero brain power to figure out. And now you can be like someone's like, "Hey, can you get me the position in view space?" You're like, "No problem."

[00:48:52]Or like, "Hey, I've got a position in clip space. Can you take it to model space?" You're like, "Sure, I'll just invert a couple of things." So when you invert something, it flips the from order.

[00:49:02]>> And then you can look at any piece of code and if the view if the two things on the domino ends don't line up, you've got a bug 100% every time.

[00:49:13]And so like whenever I would go to studios and I would do like VR debugging like when VR first started coming online and people until VR this you could kind of get away with being like well I got three matrices I'll just figure out the order and usually they have a little bit better naming than just view. Um but sometimes people like to use model to world and if you do that your dominoes don't line up. So if you imagine cuz the like if you had view to projection or view to world or something or world to view it doesn't line up this way cuz you the multiplies go to the right. So the from is the kind of key thing that tells you oh things on the right go to the left.

[00:49:52]>> So I fixed a ton of bugs just renaming vector. So I'd show up and they'd be like we have a bug with our VR projection. I'm like show me your matrix names. And they'd be like all random.

[00:50:01]I'm like we're going to rename matrices.

[00:50:03]Like no let's just fix the bug. I'm like, "No, no, no. Rename the matrices.

[00:50:06]All the bugs will just fall out." And then it's like, sure enough, many bugs would be discovered and just fixed immediately. And uh so that's the correct convention. Um the the last ve 4 thing is kind of annoying.

[00:50:22]Sometimes I do position underscore model because it's like but this is the one that is is is the most um you mean position underscore model here.

[00:50:36]>> Yeah. But then you already will get the heebie-jebies cuz you're like ugh everything lines up so nicely except for that one. But people like to have the more kind of like because then everything just becomes everything is model something or local something or world something and it's like when you read it's like world and you're like gh >> so it's kind of annoying. So for those things it's it's annoying but for matrices it's 1 million% worth it. You will it will save you from many many bugs. Um >> okay nice. Yeah, I actually when you started saying this, it's like oh actually it's super easy you remember that model is this and the model is that and then I realized that I made this mistake when like I had a model matrix and when you think about this model as a model you have a object space but it's not easy to understand that the model goes to the world space right and it's >> and exactly >> yeah so I think that's and it's even more the case with cameras cuz it's very common for people like half the people will think of cameras as as like a position in in world space somewhere which is like the more intuitive things like where's my camera floating in the world but typically the the traditional view or camera matrix is actually like a look at matrix which is actually the inverse of that matrix and so you just never know you look at a piece of code and you're like that's the camera matrix you're like which one I I don't know >> and then you name it this way and you're like world and then it's really easy like if you have an entity it's world from camera. Oh that's your camera matrix. Oh great. Well how do you take things into camera space? Well you invert world from camera becomes camera to world multiply by any world vector.

[00:52:20]Now it's in camera space.

[00:52:23]Yeah. Nice.

[00:52:25]Nice. We're reviewing strcts.

[00:52:28]We're now reviewing stracts. We didn't got to main yet but we've got a lot of tangents. So here we have a cool one entity.

[00:52:40]Entity first of all already done. This is like the classic fat scenario >> where you start to dump all your like okay I have this kind of corner thing I need to store. Okay let's go.

[00:52:55]>> It's in there. There's the space for it.

[00:52:57]Removed >> rotation. Yeah I mean all looks looks about right. Next level 64.

[00:53:05]Oh, it's like next level name or something >> to do make level names as enam. So don't need to carry around 16.

[00:53:12]>> Yeah, it's fine. You don't have that many entities.

[00:53:15]>> Yeah, it's all good.

[00:53:18]>> Now here one >> two. Now that's a buffer right there. D That's not actually 2 megabytes.

[00:53:29]That's 2,000 by two. That's 2 million bytes.

[00:53:33]But but all right. um uh okay >> so we have we have a world state >> world entities right so this is like the thing we're going to get into okay I'm not going to spoil it okay you're not going to spoil it >> but you they're going to h they're going things going to happen okay >> okay two bytes info per tile okay and it's a buffer two 2 megaby dense buffer representation of the level encoded by coordinates encoded by coordinates.

[00:54:09]So is this like okay so m maybe it's x and y indexes into that but why is it a u8 okay question marks will be left around that area okay and then we have a player we have 64 boxes 64 mirrors 64 things of stuff and solved levels is 64x 64 so it's just a bunch of names yeah I mean I would probably make those 64s into a define of some sort, but that's just me.

[00:54:41]Um, let's see.

[00:54:44]>> So that you can reference the max one.

[00:54:48]>> Well, it's just because here you've got a bunch of 64s and here some of the 64s mean 64 characters in a in a name and some of them mean 64 entities. And at a glance, if I was modifying this code and I'm like, "Oh, you know, I want to make my names long, well, I want to make like more entities or whatever, I might accidentally hit the other 64s cuz they're not like the other 64s." So, that's kind of >> my my question is, are you pained that all of them do not share like one single array with a type?

[00:55:27]>> No. And then no, it's totally switch.

[00:55:30]>> No, it's all fine. That's all right. I'm much more pained by bad matrix naming than I am by by this kind of stuff.

[00:55:38]Yeah, why not?

[00:55:40]>> So, we're not like we're not uh lamenting that we didn't find this like thing. I don't mind. So, I think it's it just it depends on how you want to think about it. And I think >> I mean I guess one thing I'll say is that it's a little strange that it's this and that it's one fat strct cuz you might as well just have boxes box types and just have 64 boxes if you're going to go this way cuz they're not sharing any stuff. But I suppose it's convenient to pass things around by entity and have like some type eraser that way. Um, but I think having things sorted by type, if that makes the code easier, cuz if you're iterating over types of entities all the time, and that's an easier way to think about it for you, that's fine. Where this starts to fall down is if you want to do something to all the entities. So, you end up having a bunch of code which is like render all my boxes, render all my mirrors, render all my sources, and it gets a little bit repetitive. And I don't like managing that kind of boilerplate. It slows me down to like insert that kind of logic in multiple places. But until somebody feels that pain and considers it pain, like you can't convince them that this is a problem. So like I'm kind of, you know, >> slow potato.

[00:57:05]>> Yeah. It slows me down.

[00:57:07]>> We got to go fast.

[00:57:08]>> We got to go fast. Um, so I think like that first talk I saw from from you with like Billy Basso, he talks about using a macro for this kind of stuff because he basically has this structure, but he's like my solution to being slowed down is I'll make it a macro and then it inserts in four call sites at once. I'm like, yeah, let's do that. That's good. So I I would say that's the that's the next evolution in that Pokemon tree where if you want to go named separate arrays like Billy got you covered and if you're like I don't want those macros I just want one thing of things. It's like all right that's like more of more of my camp.

[00:57:46]Okay we're going to come back to world state.

[00:57:50]I'm going to keep this in mind. Um, okay. Now we have couple of things. Uh, trailing hitbox animation.

[00:58:03]I think we can come back to with the gameplay code push result.

[00:58:08]>> Okay.

[00:58:08]>> In terms of pushing the the pushing the box, right? It's a soccer band game after all.

[00:58:15]>> Yeah.

[00:58:15]>> Got to push.

[00:58:16]>> Got to push.

[00:58:19]um pack turn state. So pack is a short for a backpack >> short for the thing you carry meaning the other one. So you you play as a player and then you have >> uh >> that's your backpack >> backpack.

[00:58:38]>> I thought it was like the packed state and I was like oh we're doing some bit packing but not really. Yeah, it's it's the pack >> game progress world zero world one gate one.

[00:58:49]>> Okay.

[00:58:49]>> Editor structs edit buffer editor mode.

[00:58:52]So this game features undo and then reset level.

[00:58:59]>> Okay.

[00:58:59]>> So all of the all of the levels and movements are um serialized and so >> good. Her state writing field camera mode rcast hit pop-up type >> cheat mode >> popup >> lasers does cheat mode toggle >> yeah laser color >> that's a color >> questionable >> well you know things things are >> I guess this allows for you know reddish green lasers which is good like you can have las yellow lasers by doing a red green >> almost immediately you would like you would like to have a normal color representation via vector so that you have your own operations on the vector for colors and then you can have couple of constants with like hey this is my green for laser this is my red >> well it depends on what this is for if this is like the color visually that's true but if this is Um, if this is the logical version, which is like, you know, the game logic version, like you're saying the green lasers operate differently than red ones.

[01:00:20]Then you don't really want this to be a VEC 4, right?

[01:00:24]Or a VC 3.

[01:00:25]>> Yeah, but I would say like this is the visual representation. Maybe >> I don't know what it is yet.

[01:00:31]>> It could be visual. Sorry. If then then it should be an enam for the type.

[01:00:36]>> Who knows? We don't know yet.

[01:00:38]>> Or may be it should be a trait, right?

[01:00:42]Because it can be both.

[01:00:44]>> It is.

[01:00:45]>> That's what I'm saying. Maybe green l maybe something can be green and >> red. We don't know.

[01:00:51]>> Okay.

[01:00:52]>> Can't judge too early. We can't judge prematurely and then we will judge hard hard. And we need to at some point we need to do like the claw hours estimate.

[01:01:02]I don't know what how to do it.

[01:01:03]>> I think this has very high claude hours because I'm not sure Claude would like this has a lot of game knowledge baked in. So I think this is a this meaning what >> like everything we're reading so far although it's kind of like just enums instructs this contains like the design of things.

[01:01:27]>> You know what I mean? to get to get this printed by Claude would require like lots of prompting and lots of back and forth between Claude.

[01:01:34]>> So even though there's not a lot of lines, >> we're going to do undo. Then we do only these three strcts and some functions, but not like all of them, right?

[01:01:43]>> Yeah. And we need laser colors as opposed to like, hey Claude, wrap SDL input into a bunch of pools.

[01:01:50]I would do it right away for you. This one is like I don't know. What >> was this accent?

[01:01:54]>> That's my That's my Claude accent.

[01:02:02]Claude hours ranking. All right. So we have wrapping input hash custom >> input >> systems.

[01:02:18]Actually that's hashtag. It needs to be like this.

[01:02:21]>> Yeah. Um, so and then we're going to have type defin all the >> you know you remember this meme of like all the things and like yeah that's that's the reference. Okay, your how we're going to doing the estimate chat chat, we need your estimate.

[01:02:46]>> We need your estimate for cloud hours of prompting like relatively high cloud. Okay, we're not going to do like, you know, high cool clots.

[01:02:57]>> Um, wrapping input custom input system.

[01:03:01]Um, how much hours of workload to do it, right?

[01:03:06]and you also think about it. And then let's do like let's do the countdown and then we both type in chat.

[01:03:18]>> Okay.

[01:03:19]>> Okay.

[01:03:20]Oh, are we going to Oh, I I'm not signed into chat. I'll just say it.

[01:03:25]>> Okay.

[01:03:26]>> I don't know.

[01:03:28]So, I think for wrapping input, >> are we doing discrete hours? Like it's got to be at least an hour.

[01:03:37]>> Yeah. Okay. Yeah.

[01:03:43]Okay. I have one.

[01:03:45]>> Okay.

[01:03:47]Three, two, one.

[01:03:49]>> 1 hour.

[01:03:50]>> One. One hour. Definitely.

[01:03:52]>> Okay. Okay.

[01:03:52]>> Yeah.

[01:03:53]>> People are like 40 minutes.

[01:03:54]>> I mean, yeah, it's probably like more like 10 minutes or 20 minutes or whatever, but we're going to >> 1 hour.

[01:04:00]>> We have a lot of credits, you know.

[01:04:01]We'll we'll ask it to make no mistakes.

[01:04:04]zero bugs, man. Like all >> be like write the tests, you know, do all the good stuff. If it's less than an hour, just spend the rest of the time making it better cuz it can always be better. So >> it can always be more std as you know after your recent experiment.

[01:04:21]>> Yeah.

[01:04:22]>> Okay. type deving all distracts then like the thing is I am a little bit skeptical here with the the claude hours analysis because it w did not come as a single task >> right >> you know it was it was a part of of implementing a let's say undo system so you only do undo once >> but if it was like hey I need to lay down the foundation okay just in like abstract way >> do all is how much do you think would have been in CL hours? You can tell me your first uh impression and then I would tell you mine.

[01:05:04]Well, I think that's the thing is that if uh the first draft is always 1 hour, the interesting part is how long it takes to get to the real result because like you get really good oneshot things from Claude all the time. Um, and if it succeeds in the first try, you're like, great. But if it doesn't succeed, that's where I feel like all hell breaks loose because it's either going to make it there in a couple of tries or it's just going to be spinning and you're going to be spinning and >> spinning tokens, >> spending and spending those tokens. And so I feel like Yeah.

[01:05:45]So I I mean I think the initial I don't know. We'd have to get to the main. Did we get through all the type defs almost? I think.

[01:05:55]>> Yeah.

[01:05:56]>> Uh I think we stopped on something like 350.

[01:06:03]>> Yeah. My my feeling is that it it would be faster for you to type the strcts than it would be for you to def to actually describe all of these strcts.

[01:06:16]That's my opinion.

[01:06:18]So I think you'll sit there for an hour typing in specifications, but I think the overall thing is going to be like effectively as fast as you typing the strcts, >> which might be hours.

[01:06:33]>> I think this one is something between 10 hours to 20 hours.

[01:06:41]>> Yeah. And my take is that whatever you're going to do through clo it will add the things that cloth thinks should be there >> that is not at all aligned with your vision and the more time you will spend just understanding and way I actually don't need that at all like but it looked really good like it looked really nice like from an example but like no actually I don't need that >> so it going going to be more like messy to to handle though handle >> what is going on.

[01:07:17]>> All right.

[01:07:19]And did we should we breeze through the rest of the strcts and get to the get to the code now that we kind of get know the lay of the land a little bit? So and stuff when and stuff finishes and like we can we can look at and uh separately I think as a system >> and now we enter into globals and then functions.

[01:07:43]So globals everybody this >> tow spotted I'm I'm on it.

[01:07:48]>> I I'm two pie team.

[01:07:50]>> Oo I'm a tow kind of guy.

[01:07:53]>> Okay.

[01:07:53]>> Okay. very well. Um, display.

[01:07:59]>> Mhm.

[01:07:59]>> Okay. Ton tons of constants. I don't think we're going to go through them each one by one.

[01:08:06]Camera sensitivity camera. Oh, and one thing that it's important to mention that here are the uh is also the state initialized, right?

[01:08:20]>> What is it? I actually don't see it now.

[01:08:24]Ah here >> right.

[01:08:28]>> So it's all zero. Yeah.

[01:08:29]>> World state. So this is zero initialized.

[01:08:32]>> Yeah.

[01:08:33]>> As expected from a clear handmade hero descendant.

[01:08:38]>> Yeah.

[01:08:39]>> Zero initial.

[01:08:39]>> You don't even have to do the little zero, right? Because >> um you mean this >> statics are zero by default. No statics are zero by default. And see >> okay. But um I like the explicitness cuz it's basically kind of saying hey it's going to be zero. So this is basically in the program our like entire state right and >> given that we have one file.

[01:09:07]>> Mhm.

[01:09:10]Pretty much. Why would we do this through static?

[01:09:14]>> I don't know.

[01:09:17]So, I'm not sure, but and I also saw like a surprising lack of statics in the platform layer, but um honestly, I'm not I think that there might be things in C with static that I maybe I'm forgetting.

[01:09:32]So, I'll kind of chalk it up to that, but I'm I don't really know why why that's there.

[01:09:43]>> Okay, we'll just leave it. This this basically makes it like global but at the same time you have a draw command >> but the globals don't matter right >> yeah okay good >> yes someone pointed out in chat that's a good point the downside of this is that you can't hot reload using this this style of way of doing things well I suppose you can just pass the old state into the new thing but >> I guess you can't reload this whole C file yet cuz it's >> because you have to be passing yeah has that >> global Yeah.

[01:10:16]>> Yeah.

[01:10:19]>> Yes. Okay. We have all the other state.

[01:10:22]I don't think we should spend too much time.

[01:10:25]>> And now we have helper and helper functions.

[01:10:29]>> Hey, camera basis from yaw.

[01:10:33]>> Yeah. See, this is the kind of thing where you can just be like make Oh, so good. That's why you're the host.

[01:10:44]Um, I call it make uh camera from world or make world from camera cuz again like I don't know which one this is and so I just kind of have to hope um >> cam >> so from world like this >> or yeah or world from camera like I would call like make >> but it should be one of those two. So, and then all of your matrix functions can just be that and then you're never confused.

[01:11:22]So, yeah, here we have this this this this issue with like losing the understanding in what's basically.

[01:11:30]>> Also, this one is a little skeptic cuz you got yaw right and forward, but I guess that's probably the useful thing for the game. So, that's okay. You know if that's um >> okay quaterturnian from axis angle >> yeah classic expected >> turnian is zero is a sketchy function to have uh so I'd probably audit where that is but I guess maybe if it's like it might mean that's uninitialized quitterian or something it's that's okay but I might rename it to like well yeah anyway cuz you never want to check against zero with floats. But >> uhoh. Uhoh. He's going to be pissed.

[01:12:17]Look at him. Look at him. He's going to be furious.

[01:12:21]>> Not Not thrilled. Not thrilled about that. We'll have to >> This is similar to here is zero. So I think this is a bit of a logic mistake.

[01:12:31]>> Uh >> questionable. Um, I don't I mean it depends on what zero quitterian means, but I'd rather it not mean anything. Um, also quitterian subtract.

[01:12:47]What does quturnian subtract mean? And this is a rotation.

[01:12:52]>> Is that like the angle between two?

[01:12:55]Oh god. Quian subtract between two angles. Okay. I thought it was doing Oh, that's okay. Oh, this is real.

[01:13:02]>> What? What is quturnian subtract >> million subtract?

[01:13:06]>> What?

[01:13:08]>> What?

[01:13:09]>> Uh-oh.

[01:13:11]>> That's not logic. That's not logic.

[01:13:13]>> What is quitterian subtract? That's not a thing you do. What does that do?

[01:13:17]>> So this is >> quitterian multiply by a scaler.

[01:13:20]>> This is uhoh.

[01:13:22]>> So illegal.

[01:13:26]>> What are we doing here?

[01:13:28]>> Not defined. Quitterian ad is is also not a thing. Um >> not real quaterians made up math.

[01:13:45]>> I mean you can do that but I don't I actually don't know what it does. Um scalar multiply.

[01:13:53]So maybe maybe uh maybe you should tell why.

[01:13:58]>> I mean I'm not an expert on quitterians.

[01:13:59]So all all I know is that the operations you ought to have unless you're an expert is like multiply and conjugate which is like the inverse or really you should have in inverse which is the conjugate divided by the scale or something I forget exactly but um really you probably just want quitterian like lurp quitterian angle between make quitterian from axis angle and kind of treat generally speaking quitterians is like black boxes encoding rotations.

[01:14:32]Um, if you start getting into like raw quitterian math, you better really know what you're trying to accomplish here.

[01:14:40]Um, which is incredibly rare in game math, especially like hobby game math. Um it's like quaternian's definition involves imaginary numbers and uh if you like you're not supposed to treat w as a as a real thing like it's not the coordinate system. It's not like 4D coordinate system. So let's go and the these operations are pretty much undefined as far as I know as far as I remember.

[01:15:12]>> Yeah. I mean the other thing is >> if you add those two you don't get anything useful like >> yeah because >> whatever it was like for >> right like yeah exactly like quatern I don't know what the the correct math language is but they they form a specific kind of group I believe right and then you want to make sure that they remain normalized probably you can do a non-normalized quturnians but like for scale but you got to make sure you do it carefully There is a great video of three blue one brown.

[01:15:46]>> Yeah.

[01:15:47]>> With the visualizations of like hyper planes and how they change. So like not every not every combination of these numbers will be valid. As Anton mentioned you need to keep them normalized. So it's not like if you add two together like this is basically vector adding but it has nothing to do with quitterians.

[01:16:04]>> Yeah. Yeah. So I mean I I think personally quitterians should be their own type. I think using vec 4 as a quitterian placeholder leads to mistakes more often than not. Although I kind of also get it because in graphics typically like in shader programs it used to be common to use ve for quitterians and shaders because blah blah blah but um yeah I think it's a bad idea. So I would have quitterian as its own type for this reason. So that way you can have separate math functions for your vectors and your separate math functions for your quitterians.

[01:16:46]This is not isolated occurrence.

[01:16:50]>> So it looks like it's doing a lot of >> animation. Yeah. So it's doing reormalization after the add. Okay. So it's look scaler multip. Yeah. Okay. So this is doing the equivalent what's called like an end lurp. So I would um I would re uh I'd repackage this whole thing. Quitternian normalized quaternian add quitter scam.

[01:17:14]That whole thing if I if I'm not mistaken is what's called an nlurp as opposed to an slurp or slurp. And nlurp is this idea that you just take two quitterians and you just lurp between them and then you renormalize.

[01:17:27]And it actually produces pretty nice interpolation. So, a lot of people knock and they think like slurp is better, but nlurp has some nice animation qualities because it's got like a baked in easing effect into it. So, I actually like endl scaler multiply.

[01:17:49]Uh, I think it's a little too raw for me for my taste. I would just make an quitterian and llurp function and then it's clearly documented what it's doing.

[01:17:58]Um, and then a quitterian slurp. There you go.

[01:18:02]>> This would be an LAR.

[01:18:04]>> Yeah, exactly. Is that from Claude?

[01:18:11]>> No, I just wrote it down from memory.

[01:18:13]>> Oh, damn.

[01:18:15]>> And this slurp.

[01:18:19]>> So, yeah, probably best to be have this isolated. But I don't know whether this will this is what we'll get from these.

[01:18:26]It doesn't >> Well, you've got param look. So I'm just like I'm using my pattern recognition.

[01:18:31]So you got PAM param is probably the parameterization of time cuz look you got frame index + 1 / animation time. So that's probably forming something like a 0 to1 scaler. And then I'm seeing the canonical lurp form which is like a * 1 minus p. And if you scroll to the right I suspect there's going to be scaler multiplied by param. There it is. So that's your front that's your inline lurp. It's >> lurp between a and b is a * 1 - t + b * t. So that whole thing is a lurp and then it's wrapped with quitterian normalize which is probably just a normalize. And so then really it's just lurp the quitterians normalize which is nlurp. Oh wow. Okay. Yeah. It's my reverse compiler. It's like nice. That's a Yeah.

[01:19:29]And LAR got it.

[01:19:32]>> Um, perfect.

[01:19:35]Quitian dot also. I think you have Well, anyway. Yeah, that's probably quaternian dot. You have to be a little bit careful because of the double wrap on quitterians as well. But I don't know if I can do that one off the fly to know.

[01:19:53]Okay, we need to go back to >> something like 500.

[01:19:58]Where were we?

[01:20:00]>> We saw the quitterian questionable functions. And so yeah, okay, but that's a that's that's way way uh it's good that this is what happened with the quitterian add and quitian subtract because initially I was terrified but yeah but now like okay it makes sense. They just need it as part of a lur.

[01:20:23]>> Yeah, it just uh uh more verbose and not uh extracted as a function.

[01:20:31]>> Yeah. So with quitterian dot I I my brain says we have to check whenever we use dot and compare things we we should consider whether it's the absolute value because there's some double cover stuff going on. And then quitterian conjugate scares me slightly because um conjugate and inverse are usually not what you want or sorry conjugate and negate you probably want inverse which is conjugate divided by the scale of the quturnian.

[01:21:09]Um, and you don't exactly want to normalize cuz when you compose a bunch of Quitterians, you want there's like a numerical stability that's famous in Unity. If you do a bunch of Quitterian math, at least in the old Unity, they used to slowly get denormalized and like grow in size.

[01:21:28]And so everybody had to keep reormalizing them all the damn time. But it was all coming from the fact that the inverse was defined as the conjugate rather than the conjugate divided by the length.

[01:21:39]Okay. So, watch out. Probably use inverse instead of conjugate, but a lot of like tutorial content talks about conjugate.

[01:21:49]Um, and what why why is normalize doing that?

[01:21:59]Length squared. Oh, I see. So, it's just doing >> length squared.

[01:22:04]>> So, it's just basically saying don't normalize. Yeah.

[01:22:07]>> Yeah. So a better form of this is um just yeah no I mean that's fine that so it basically returns identity. Yeah, if it's if it's too small to normalize, that's fine. We'll live with that.

[01:22:23]Cross product. Sure. Okay. Now we enter from quadrian. We enter vectors.

[01:22:31]Rotate by quitterian.

[01:22:37]I guess I guess it's correct. I don't have compiler in my eyes. This is the part this is the part that we >> there's lots of different versions of rotate by quitteria as well and but there is a cute one where it's just the quitterian multiply.

[01:22:54]So there's a version where you can like you have the quitterian multiply function and the the one that I like because it's cute. I don't even know if it's faster. um you can pack a vector into a quitterian and then just pretend it's a quitterian and then multiply it and then that is the vector times quitterian multiply.

[01:23:21]So I don't know what that formulation is and I'm reading the chat it's like yeah you're probably right that it's probably a division by square length squared or something. Yeah, I'm probably wrong about that. I don't I just remember there's some length involved that if you don't take into account the length you slowly get drift over time.

[01:23:38]>> By the way, on a unrelated note because it's C, you need to first define a function that you're going to use below, right?

[01:23:47]>> So all of this needs to be in a specific order >> of first happening there and then we do cross product >> so that we can do the cross productd here, right? So like >> you don't have to do it that way though because you can forward declare all the functions. So just on a kind of tidiness level this is the stuff that I would put into types. I would rip out all of the actual names of the functions. I would put them into one block of declarations.

[01:24:16]So then it's easy to read kind of what's in your math library. And then after the declarations I would actually do all the implementations of the functions and you keep them in the header so it's in line so it's fast for math. So that would be like how I'd structure the vector library.

[01:24:32]Math helper functions and chords to norm.

[01:24:42]>> I don't know about that one.

[01:24:43]>> To normal to to float to float >> float float.

[01:24:47]>> Yeah, >> this stuff's hard to name.

[01:24:50]>> Norm int.

[01:24:53]>> Yeah. Floor >> with the floor. with the floor. So this is like implicitly saying round to nearest cords within level bounds. This is by the way like when I was doing this type of code for some whatever experiments or games or like things that happen on 2D squares.

[01:25:13]There's so many little conversions of like is this on the tile like in the center of the tile or is this on the edge or is it in the corner and >> to the point where I invented up like a new coordinate system. So like I didn't I have if you have like even 3D things that are happening on the grid like here uh I had the normal like uh MVP free coordinate systems but I also had >> system on the tile directly right like the center of the tile and then the corner of the tile >> and I could move between those like as coordinate systems because like I needed to have this defined clearly where am I that >> I think that's a very good idea. I don't know if I would do it with a coordinate system, but I mean that's for 3D that that does make sense. And that way like you can use suffixes to know which one's which cuz you don't want to mess those up in graphics. These are like the half pixel errors that you get. Like famously you UV coordinates for example are meant to be corners of well UV boxes are corners and then UV samples like S fragments or centers of pixel and if you mess that up then you get all sorts of really subtle artifacts. So yeah, I think I usually have a function which is like convert from centers to corners or corners to centers and then I suffix my things with corners or centers um similar to the spaces and then try not to mess that up especially in code that's really careful there.

[01:26:44]So here I'm assuming you need to kind of remember this when within this code like >> yeah and it's using the level dimensions that are global. I don't love that but we'll roll with it.

[01:26:56]>> This one. Yeah. So it's basically saying there's a level and then we're just going to check it. But because in C you don't you don't this is another place where I like C++. This is a case where objects are handy. It's like I have a level object. Is it level cord contains or whatever. That's like nice. It's nicer than having a global cuz now you know if your level dims are not set right. It's like uh it's not clear that you have you should have set the level dims or maybe you're checking about a different level and you accidentally I don't know. So you kind of want to pass the level in but then that becomes cumbersome. So okay equality >> negation >> is zero.

[01:27:45]>> Yeah.

[01:27:46]>> Int is zero. This is this is float zero.

[01:27:49]So this is >> yeah. So a better format for this is is returning a bool three. So if you look at how glance that ends up being better. So you return a vector. So when you compare for for all of your comparisons, whether it's zero or equals or less than or whatever for your vectors, you return a bool of that same uh dimension. So it's like a vector 3, you return a bool three. And then you can define things like uh there's an all operator which just basically says x and y and z. And so the syntax ends up being if all vector equals vector, it's let you talk about the components. Um, yeah. So it's like if all vec A equals veg B.

[01:28:46]Yeah.

[01:28:48]So that for example would say if all the components of vec A are equal to vec B and then you get zero for free because you just say ve a equals vec zero.

[01:28:59]Um but then the other one you have is any which means uh that's a common one like if any of the components are equal to zero you do some logic. So that covers a lot of your cases without having to write like all these permutations. Um, and any of Yeah.

[01:29:31]Yeah. Yeah. Yeah. I think so. Yeah.

[01:29:34]Perfect.

[01:29:36]Stolen. It was stolen.

[01:29:39]Um, but you you know you mentioned this kind of fiddly code on grids and it's pretty typical that you have this kind of thing of like you're checking something inside bounds and so the code becomes if position greater than or like if all position greater than or equal zero and all position less than or equal dimensions >> and then that types out all of the four checks that you have to do along here. So that's kind of nice.

[01:30:13]>> Like add and subtract subtract.

[01:30:16]>> Yeah. Yeah.

[01:30:16]>> Victory amps a >> multiply.

[01:30:22]>> Put it into vehicle it >> inner product aka dotproduct.

[01:30:30]But if you're going to call it inner product then you should call cross productd outer product.

[01:30:34]Be consistent. Damn. Damn. What a review comment, man.

[01:30:42]>> But I had no idea that that product's in a product.

[01:30:46]>> Yeah. I always >> That's why like John Blow used to have a column called the inner product or something on on game uh Gamma Sutra magazine.

[01:30:55]>> It was all math.

[01:30:57]>> I didn't know.

[01:30:59]>> Vic length.

[01:31:03]Vic length. But I can see ve length squared >> sign length.

[01:31:08]>> I would I would I would probably suspect if we're doing this already like we're making a library >> like you can have this.

[01:31:17]>> Yeah. Make that library. Yeah. You need that squared >> and then you can repackage it >> because >> this is the kind of code that Claude can probably generate but I'd be scared. I'm like equally scared of writing it myself and generating it >> like but if you have enough tests then I suppose it's all fine. I don't know. I written like I used I had my own math library like this and after probably eight or nine projects and years and years of using it. I discovered my dot product was actually left-handed instead or my cross product was left-handed instead of right-handed and just like never came up. And then I kept chasing this code. I'm like what is happening?

[01:31:54]Why is it reversed? And then I was like, it's the cross. And then I found the bug in my cross product. So it's real. But I don't regret it. I regret nothing.

[01:32:03]>> But this is always with these like base libraries for stuff >> and it's always and it it really is painful to discover this over time.

[01:32:13]>> Yeah.

[01:32:13]>> Just today I like did in like code at work. I I spent like 3 hours understanding why there's a crash at runtime and like everything should be fine. there was this like templated service registry where where you have multiple inheritance it didn't work but if I had single inheritance it worked and I found out after hours that there was a reinterpret cast instead of dynamic cast >> so if you put as a first base class it worked but if you put it as a second one and then you ask for this type it would give you but the offsets were So if you want to access the function you have a runtime error. It was like this is like this base level because like we made this super generic thing >> that is supposed to handle all the cases >> you know and then you just >> you forget about some because C++ is not >> a normal language. No, >> B for real programmers >> uh signed length.

[01:33:23]>> This is like akin to my remember that function we found in in my code which was like reduce by or whatever and we spent like 20 minutes figuring out what by meant I think this has that flavor >> like cuz what is assigned length? That's not a standard concept but >> um >> ve length it's a float. Okay. And then it's like if it's equal to the apps.

[01:33:52]>> Whoa. What >> I guess I guess it would be easier to see where it's used. I guess it's like >> I guess sometimes it might be useful to have already like you're doing something in a direction, right? and you need a length and then if you compute the length and it's always positive now you need to be like okay if it was this direction then I need to minus one it and like blah blah blah.

[01:34:22]>> Yeah. I mean yeah but I get the vibe but three abs.

[01:34:32]So it's basically saying if it's in the if it's in the positive quadrant then it's length >> but in any other quadrant it's negative length.

[01:34:45]>> Oh that's that's not uh that's not mirrored. No >> it's not mirrored. It's just one quadrant or the other three.

[01:34:52]>> That's most likely going to be a bug.

[01:34:55]But it wasn't used in this other the fourth quadrant. I forgot.

[01:34:59]>> This is this is my my bad. I think it's used in quadrant like two and four or whatever like >> the quadrants.

[01:35:07]>> Quadrant four is waiting.

[01:35:15]>> Okay.

[01:35:15]>> All right.

[01:35:16]>> Normalize.

[01:35:17]>> Okay. Normalize >> hatamard here.

[01:35:20]>> Oh. So it's not outer like went full hatamard but hatomar product. Oh no no no. Yeah. So yeah this is the hatomar product. Yeah. Sorry. So yeah. Yeah. So you got to do the outer product for your cross product.

[01:35:35]>> What can you explain this?

[01:35:36]>> Hadamard is component-wise multiplication aka the the standard thing. But if you want to go full math style hatamart is just you just multiply the things.

[01:35:50]It's almost never used because I don't think I don't it's for scaling matrix.

[01:35:55]It's multiplied two vectors component-wise or two matrices component-wise.

[01:36:00]>> And when is it being used? You mentioned skin skinning.

[01:36:04]>> Uh probably it's you can like for color scaling or for tinting. Color tinting.

[01:36:12]>> This tint color tinting. That's right.

[01:36:14]Multiplying. Yeah. Yeah. Yeah.

[01:36:16]>> Yeah. Okay.

[01:36:17]>> But you can do it on matrices, too.

[01:36:18]That's why it's got a math name.

[01:36:21]>> Ah.

[01:36:22]>> So the the Let me see if I can get this right. So the the hat had product is the standard multiply of matrices by components almost never used in graphics never as far as I know. And then the outer product the inner product is the standard matrix matrix multiply I think. And then the outer product I forget what that does but maybe someone in chat knows but basically all these are defined for matrices as well.

[01:36:48]>> Okay.

[01:36:50]Okay. We go for the sake of time like we go. Yeah.

[01:36:54]>> How where's your when's your deadline?

[01:36:57]>> Got about 40 minutes.

[01:36:58]>> Mhm.

[01:36:59]>> Speed up. We got to speed up. Uh quartz the buffer index type.

[01:37:05]>> Yeah.

[01:37:06]>> Quartz the buffer index direction.

[01:37:08]Uh okay. Set tile type.

[01:37:12]>> Yeah. Let's just move past the helpers.

[01:37:13]I think I think we got the gist for it.

[01:37:16]>> Okay. Then we need this. We need Claude's ranking >> of helpers.

[01:37:23]All the mathy helpers.

[01:37:27]Claude estimate chat. You got to vote as well. Drop a number of hours that you expect Claude and you prompting Claude to take generating the function functions that we've seen the helpers for quotians vectors pretty much math library and signed length >> and signed length that one is going to be. So I my suspicion is it's like one hour for everything, you know, cuz that's our minimum, but then kind of like an extra 8 hours to do the signed length and other non-standard >> to force to force Clark to do something weird for a quarter in one >> good clone. GLM. Yeah, there you go.

[01:38:16]>> Okay. My take is is actually one hour.

[01:38:22]>> I think it's a barebones thing. Like everybody in the C++ world, everybody at some point like >> I'm going to do my m my vector map library.

[01:38:32]>> So like there has to be like thousands of examples for this.

[01:38:36]>> Yeah.

[01:38:40]>> Yeah. 1 hour above buggy possible.

[01:38:43]So now I'm going to look up here win main.

[01:38:52]And here we go. This >> I don't know any I don't know very much about win code.

[01:38:59]>> I'm not going to be >> this is Casey introduces in the handmade hero >> which I'm assuming this is why it's here. Not not like this is the the proper entry point on Windows.

[01:39:09]>> Yeah.

[01:39:10]>> But you can use main from the standard library and use it.

[01:39:14]>> Yeah.

[01:39:14]>> Every time I read this code and I do it and then it just exits my brain >> like >> I think that's that's what's was supposed to do like the the design design is for you to do it. So I'll just this the kind if someone's handing me this review I just be like LGTM man like let's we'll find the bugs later one can never know if there's bugs in this code it's impossible >> here is here is one thing that I wanted to mention before we go to game initialize right >> query performance counter >> do you want to have a bit talking about that >> uh that's what I use so is it bad No, it's just that as far as your ability as a programmer to get readings from the machine what happened and how much time it took, right? There's no like clock meaning like clock we wall clock we have on the on the wall like you you have a CPU based counters and one very basic thing is a RDTSC assembly instruction to read >> RDTSC to read wall clock time. That's like the real wall clock time, right? Or is it Or is it the uh >> It's in the cycles.

[01:40:32]>> Yeah.

[01:40:33]>> And it What do you mean it's a wall clock?

[01:40:38]>> I don't know enough about it, but you tell me. I thought RDTSC was like the internal set clock of um like Well, any go on and then I'll >> The tricky part is that this can be different for different coursees because it's not shared, right? So this is a tricky thing to use because you're you can have inconsistent readings >> and this is why a better way to measure anything is to do query performance counter which is the unified one for all the cores if you have you have in CPU right >> yeah if you want time time relative to >> yeah but that one is not in like actual you know system time or whatever >> and here there's a query performance frequency where you use to actually measure me the frequency of your computer because you don't want to hardcode the CPU and clock rate of your CPU.

[01:41:29]>> So you just measure it for like 100 milliseconds or something and you get an estimate and then you use this as an estimate of frequency and then when you have timing.

[01:41:39]>> Yeah, let's get to the game, man. Claude can review this part.

[01:41:44]>> To review game code, not >> game initialize. Uh >> yeah, there we go. Oh yeah, there we go.

[01:41:49]>> God.

[01:41:52]So now now my like vim bindings are just messing with me.

[01:41:57]Ah okay.

[01:42:09]Serious serious.

[01:42:11]>> There we go.

[01:42:12]>> Here. Okay.

[01:42:13]>> Okay.

[01:42:14]>> Here we go.

[01:42:15]>> We go. You need undo buffer.

[01:42:18]>> Okay.

[01:42:18]>> Recalate the buck start chords. Why not?

[01:42:21]Initialize state. Initialize state.

[01:42:25]All right. Initialize state zero. World zero.

[01:42:30]This was a little bit confusing.

[01:42:32]Read over world zero's word state from file on startup. So it's kept in memory.

[01:42:39]>> Used on restart.

[01:42:41]>> So it just basically kept keeps it >> it copies it to or world zero. So then if you ever need to reset it, you just slam that memory back in. All right. So, it saves it all. Yeah. Okay.

[01:42:53]>> And then game initialize state for the actual level you're in.

[01:42:57]>> Yeah.

[01:42:58]>> I like it. Let's go.

[01:42:59]>> Redraw is related to to the thing. So, we go.

[01:43:02]>> Yeah. Yeah.

[01:43:08]>> Okay. Pack is the backpack. So, it's basically your >> two entities, right?

[01:43:14]>> Okay.

[01:43:15]>> And we pretty much initialize things with copying me copy >> and we put the state uh we have the double buffering of state.

[01:43:27]>> Yeah, >> that was that was this should be much more like hey this is a huge reveal of this stream. I should have played it more like hey the dreams like double buff of the state what but that's that's that's the intention as far as I can >> but that's probably for the interpolation for the animation right >> this I don't know actually >> but the you generally put things in the in the world state and then you copy over the >> copy over the to the to the to next frame.

[01:44:05]So you have >> here we initialize the world state.

[01:44:11]>> Yeah. I So for me I of this is one place where I like C++ because I often not often but often enough I I make mistakes in forgetting size of or mis mistyping one of these things. So, I try to structure it in a way where I don't have to type size of and I I like the built-in equals operator in C for this kind of stuff that just sort of handles it. It's easier to read. Um, but you know, >> is this it is what it is.

[01:44:46]>> Is this Windows 8?

[01:44:50]>> Flo.

[01:44:51]No, that should be stdiodio.

[01:44:55]>> Okay.

[01:44:55]>> Yeah, it's all right. It's all right.

[01:44:56]>> Spooked me with the upper case.

[01:44:59]>> Yeah.

[01:44:59]>> No.

[01:45:01]>> RB+.

[01:45:03]>> So, we load the level, the binary representation of the level.

[01:45:10]>> We close the file immediately. We're super >> job done. Clean it.

[01:45:15]>> We initialize things to zero. So this just straight loads the file like So this doesn't have any backwards compatibility which I guess is a little bit unfortunate, right?

[01:45:27]>> What do you mean?

[01:45:27]>> Or load buffer in.

[01:45:30]Oh no, no, sorry. I thought that was from the for some reason I thought that was the um the file load. I guess we we can see the file loading a different time.

[01:45:38]Um >> Oh, there's our four macro. There we go.

[01:45:44]>> Yeah.

[01:45:45]>> Okay. Max entity instance count.

[01:45:48]>> Yeah.

[01:45:50]>> We do actually have couple of divines here.

[01:45:53]>> Yeah. Just don't use them.

[01:45:58]>> Why do I go here? Why this like they don't extended.

[01:46:03]Ah, okay. Game initialize state.

[01:46:08]>> Yes. Let's go.

[01:46:11]So we initialize initialize all the entities now to minus one >> that's the ID I yeah I would uh suggest using a define there for like null ID or no ID or some version thereof because you might find yourself wanting to switch that to something other than negative 1 later and it'll just be a basically a nightmare to to try to change it cuz you can't search for negative like negative one's everywhere.

[01:46:42]So I think um I'm okay with negative one but I would want it to be named in case you know for example you want to start making things zero for for um for null or nil or whatever that would be a change that'd be really hard to make here whereas semantically what you're trying to say is okay initialize it to something that's invalid.

[01:47:03]Okay.

[01:47:05]Um here we have initialization of the board.

[01:47:13]>> Yeah, >> we have this huge buffer contents.

[01:47:16]>> Yeah, >> of the buffer.

[01:47:19]>> And then we want to pack the memory of the tiles, right?

[01:47:34]We go through the We want to We have the huge buffer.

[01:47:43]>> Mhm.

[01:47:44]>> For the level.

[01:47:45]>> Yeah.

[01:47:45]>> We go through all the dimensions and we fill out the type of the tiles to match what we've loaded.

[01:47:58]>> I see. So the tile buffer is basically a uh dims by dims x by dim y by dimz. But why is there two?

[01:48:08]>> Why is there two?

[01:48:09]>> Uh there was two.

[01:48:11]>> There was some note on >> the two all about is that like previous and next?

[01:48:23]>> Uh I don't remember. There was a next >> there was a comment somewhere where >> I don't like it.

[01:48:29]>> I don't like it.

[01:48:30]>> World state >> but for two bytes per tile.

[01:48:35]>> World state. Yeah.

[01:48:36]>> Two bytes info per tile.

[01:48:41]I think this is a excessive e excessive bitteness. I would just make it a strruct make a strct tile, you know, make it make it a 2D array.

[01:48:55]Don't don't linear pack it. You're just causing yourself headaches, I think, cuz it's fixed size anyway. So, just make it I guess in this way you can >> 3D array.

[01:49:04]>> Yeah, 3D array. I guess you this way you can change the sizes and still be fixed.

[01:49:09]So, I guess that has some benefit.

[01:49:11]>> Oh, Spike mentioned one bite is for file type, one is for the direction.

[01:49:18]But if you want to add more bites, like I want to add like broken tile and colored tile and slippery tile and it's like h it's like true false found. Remember that meme?

[01:49:33]>> True, false, found, not found.

[01:49:36]>> Yeah. Yeah. Yeah. Yeah. Look it up.

[01:49:38]>> Like you add more states to the bull.

[01:49:40]>> There there's like Yeah. This is like an ancient article where like someone discovers this enum which is like enum whatever and the values are true false and file not found. It's like a bool enum bool like in C and the values are true false file not found.

[01:50:00]I remember countless discussions at work. Uh what does it mean to have optional of pool?

[01:50:08]optional pool >> like like what what is what what what you wanted to represent with the null that uh >> yeah no I think I would if it was me I would just make tiles I kind of I I know where this is coming from though cuz I' like I've written these sorts of tile things and then you're like oh I'm going to pack everything into eight bits and then you're like oh it's kind of annoying I'm going to make two bytes and it's like you kind of either I think the one way you go is that you say Okay, there's just going to be generic data.

[01:50:41]Maybe it's an int or or like literally a bite array, but you still make that a tile and then you write a function which is like pack it and then you pack the bits and if you're really going to keep it tight, you you make it into a single function and you pack all the stuff or you just make it a strct and you set the fields. Um, but the in between world of like I've got three bytes and by three is this and doing that logic in line tends to kind of cause more bugs than it's worth I think.

[01:51:08]Okay, moving on.

[01:51:11]Now we're in the like speed up mode.

[01:51:13]Okay, we need to be super quick as if we're like >> high level high level LLM. Okay.

[01:51:20]>> Yeah, high level LM.

[01:51:22]>> Um, >> high quality. Um, okay. This is still everything initialization, right? Load win blood pass locked info pass load reset block pass camera main waiting alt waiting ah because we have different cameras right >> al from alternative I'm guessing >> mhm >> okay and the world state equals next world state we flipped the world okay >> I think we can go to game frame let's do it I That's going to be the meat of it, right?

[01:52:02]>> Frame game logic.

[01:52:03]>> Delta time like we thought. Delta time.

[01:52:06]Oh, I thought it might be time.

[01:52:08]>> If delta time is bigger than 0.1, delta time is 0.1. There's your frame rate limiter, man. Oh, no. I guess not. It's the other way. It's like if you want to go much farther, it's like no, you can't. 100 milliseconds is all you can do.

[01:52:24]Physics accumulator delta time. Okay, >> so this is for stable a stable delta time >> fix time.

[01:52:33]>> I don't understand this >> actually. I don't know. It sounds like it's probably going to get passed in as a variable, but we'll see.

[01:52:39]>> Yeah, if it's checking how big it is, then it's basically saying like what this is for is I suspect on the outer loop it's saying, okay, what's the time of the first frame? What's the time of the next frame? Subtract them. That's delta time. But then if you like alt tab out of a window and then come back a minute later, the delta time is going to be like a minute. And if you attempt to simulate that in physics, it's just going to be bananas. And so it's basically saying, "Oh, your delta time's huge. Just advance by a little bit." So it's preventing these giant steps of delta time.

[01:53:14]Oh, branchless.

[01:53:16]Branchless, >> bro.

[01:53:19]Save some save the prediction.

[01:53:22]>> I think this is this is for me like >> you like that.

[01:53:25]>> Maybe maybe it depends on maybe it's a preference. Maybe I don't know if it's really readability.

[01:53:30]>> You know how to write quitterians from scratch. So you're >> but I did but I almost did this. So maybe maybe actually it's better.

[01:53:39]>> Okay. And we have physics accumulator.

[01:53:42]And so we have like a separate one for physics like we don't base off for delta time but this means we have a variable delta time for physics.

[01:53:54]>> Yeah.

[01:53:54]>> So that's yolo like you have you need to have a proper integrator and >> well I'm I'm hoping that we're just interpolating between integer states which I'm guessing is what we do.

[01:54:05]>> We probably wait for some amount.

[01:54:08]>> Yeah >> something. So, we have accumulator, but then we have time step that is different. Default physics time stamp.

[01:54:15]Okay. Okay. I'm not going to skip past this. So, we're going to go slowly.

[01:54:21]>> It's probably fine.

[01:54:24]>> Troll command camp.

[01:54:26]>> LGTM.

[01:54:28]>> Next world state player. I'm Why are we taking from next world, not the current world?

[01:54:34]>> Cuz I that's who we're going to write to probably.

[01:54:38]But this is like sketchy. I would have I would call it like player next or something or pack next cuz it would be easy to I think make a mistake there cuz you don't want to read from player at this point. Camera input always at 60 Hz.

[01:54:53]Never drop frames.

[01:54:56]Don't make no mistakes.

[01:54:58]>> We make no mistakes. No drop frames.

[01:55:01]Solid 60. Yeah. Edit state. Edit mode.

[01:55:06]No mode.

[01:55:08]YOLO >> your camera sensitivity. So this is to to control the camera.

[01:55:15]>> Camera control. Yeah.

[01:55:17]>> Mouse position assuming in screen coordinates. I'm guessing >> that's fine.

[01:55:26]>> Camera pitch.

[01:55:28]Okay. editor state if it's no mode and if it's not select right which means it's not mode or select right okay all right camera basis for basis camera basis okay this is camera code I'm skipping past this >> there you god control >> loop yeah looks good >> handle writing once Once per present frame select right.

[01:56:08]What are these modes?

[01:56:10]What is editor mode?

[01:56:12]>> No mode. Place like I guess maybe it's I don't know actually.

[01:56:26]We don't know.

[01:56:29]We'll find out.

[01:56:32]Okay, I'm coming back. Maybe it's like add blocks, remove blocks kind of thing or select blocks. It's probably something of that nature.

[01:56:42]All right, close. And this one camera moves. This is camera. This is select.

[01:56:49]Okay. Writing to field. Get entity from ID. Selected ID. Writing field. Next level. Take input. Enter. Press this frame.

[01:57:00]So here's okay. Enter. Press enter. It's like you pressed and enter. Now we want to execute this part. Okay.

[01:57:10]So here.

[01:57:13]Yeah. I feel like it's a a little bit mixed in like the the input logic is mixed in with the >> Yeah, but it says that. So it's it says it says this is a bit messy. So what are you what are you complaining about?

[01:57:25]Look, there's a comment.

[01:57:29]It says what it is. Like, you didn't come here for some clean code. This is a little bit messy code.

[01:57:37]>> At some point, probably in the future, like if you had going to have more than one input method, like more than keyboard and mouse, you would need to abstract it anyway into actions, right?

[01:57:49]be like you would have one place where you define what what are the actions that you want to do and then >> what will contribute to this action and then it's a little bit easier if it's even only for the keyboard you already have this like mentality of like okay what is this action that I'm performing right here it's a bit press this frame or like you have shift entered or whatever this one I don't understand at all >> I think it's probably just trying to slam that change in immediately or something cuz you changed some things and then I don't know I'd have to read more to to understand. Okay. So this is like if you press enter but if you don't then doesn't happen mode toggle select right we change gameplay mode change place break >> select >> uh down physics >> modes are probably these like are you playing >> are you clicking in the editor and >> no mode's probably play mode >> no mode is gameplay mode change >> yeah It's game mode. Yeah, game mode cuz it's no no editor mode and lack of editing means it's a game >> break is not it's like place slash break not both place break.

[01:59:08]>> Yeah. So it's like left click place right click break probably or like add remove mode or something.

[01:59:13]>> And this is select mode. Damn. Nice.

[01:59:18]>> Speed up slow down physics tick. Okay.

[01:59:20]Now, now we're going to like we're almost at the end and now we're going to enter like the actual discussion >> and like now it's going to be like oh actually it's accumulating times like oh this is not deterministic.

[01:59:33]>> I think we have to I think we have to skip this. It's too good. It's too hard.

[01:59:38]We're just gonna have to like spin up an agent and be like, "Claude, please check for me if this is correctly handling time steps."

[01:59:51]Yeah, we're we're not going to go through this, are we? Like we're not I don't think we'll make it through all the all the details >> because this is this is this is interesting. Physics time step divided by two physics time step times two if you comma press. So I'm assuming this is like slow down speeds up speed.

[02:00:10]>> It literally there's a comment and I just discovered it.

[02:00:14]>> Yeah.

[02:00:17]>> Yeah.

[02:00:18]>> Physics accumulator is more physics time step.

[02:00:23]>> Okay. So this is a tick like this is what happens.

[02:00:27]>> Like >> we map the new world state to the next world state. I think like should it be the opposite?

[02:00:33]I feel like we always write to the next world state and then at some point we're like >> we flip it back. I think the idea is that you're going to write to the next one. So you initialize the next with the current update it and then flip it and then you have the previous to do your interpolation.

[02:00:50]So it's not quite dream style because in dream style you you you save the copy by writing directly to the next state. But this is sort of like the the simpler version.

[02:01:02]It doesn't matter because we have 64 entities, right? Like our max entity count is 64.

[02:01:08]So that's why I like to read the strcts because then it like colors my perception of how to judge the rest of the code.

[02:01:14]>> But isn't isn't this like a starting value and I will doing development and then you realize actually I would like to like have an order of magnitude more.

[02:01:25]>> I guess that's what happened to the soabon John's game, right? Like we were going to have one level at a time and then there's an overworld. So now we have 60,000 entities >> or whatever, right?

[02:01:38]>> Okay.

[02:01:39]>> Yeah.

[02:01:40]>> Then you just got to roll up your sleeves. I think we need to start wrapping up.

[02:01:45]>> Unfortunately, we couldn't go through the entire frame, but we've seen a lot and I think we can go into sort of uh closing statements.

[02:01:56]>> Okay. Anton, from what you seen >> on this code, what would you say like are there any large scale adaptations that you would do?

[02:02:07]>> I changes like big changes I >> I think generally um uh I I I would start by kind of doing like a Casey style compaction of common functionality that has shown up. So that's like a pretty mechanical task to like factor out some functions and that will make make it a bit easier to read through and you might find some bugs along the way. I I don't know if there are any but that's a good um >> you're saying this about like quotian LAR situation or >> all the math bits can be >> you suspect the game logic as well. No, I think game logic is really hard to compact honestly, but if you can pull it off, like I guess it depends on what it depends on what the the next problem is, right? So like if the question was, hey, does this work? I'm like, I don't know. Like you'd have to read it and figure it out. So there's no real sense in code reviewing it like that because um you know, you can't just look at the code and figure out if it's going to run or not. So you have to kind of pick a goal, right? So if the goal was to um add more logic or add more items, I would probably do some rationalization of how the current items work. Maybe use like more more like a trait based approach as opposed to the enums. I would probably do the thing you said which is try to use um if you can try to use less enums that have like magical negative values and things like that and try to make it so that you avoid those negative or the avoid the invalid cases. So you definitely could could use a little bit of that kind of massaging if you want to add more things because it at least for my brain it's it's at a sort of critical capacity where I feel like every time I'd add something I'd probably add a bug somewhere. That's sort of what I'm feeling. Um, so and and that would also be true for all the copying like there's a lot of inline mem copies which again is fine like you're going but as the code break base grows it's easier to it's better to factor that stuff out I think. Um, I probably I don't I don't know enough about it, but I might consider reformulating the next and current state as a just write to your current state. Like at the beginning of the frame, make a copy of your current state and call it previous state and then just write to your current state and then at the end you have your new current state and then you have your previous state and then you can do your animation relative to that. I don't know if that's how the animation is actually done. I'd have to look at it more. Um, but I think framing it as like next.

[02:04:56]Well, I don't know. It depends. Maybe that maybe that's for the undo buffer being applied. So, it's like a command pattern kind of thing where it like applies it and then you get the next state and then maybe undo. Um, for this particular game, um, because the state's minimal, I would re I would probably implement undo as just like a straight up copy of the entire world state. And that might let you simplify your undo code. So if your undo code's giving you trouble, I would just make a straight up buffer of like 64.

[02:05:23]>> Really? Like copy everything?

[02:05:26]>> Yeah, why not? 64 entities, man.

[02:05:30]>> 64 entities.

[02:05:31]>> You're hung up on this. Like, but what about the buffer for level? Like it's bigger.

[02:05:39]>> It's fine.

[02:05:39]>> YOLO.

[02:05:41]>> Count your memory and be like, can I allocate 500 megs? Probably, right? Like nobody has less than a gigabyte of RAM.

[02:05:48]like you'd have to be hardpressed if you're running on a you're you're on Windows anyway. So it's not like you're running on Raspberry Pi Linux or something. So like just revel in the address space of 64 bits and just allocate a bunch of space. Now if you want infinite undo then you know I'm not sort of knocking it as a technical decision but depends on what you want to do. If you want to learn about undo then great. If you just want undo, copying your entire game state is is a perfectly valid thing, especially when your game state's already a nice clean strct of just stuff. So, that's that's a thing you can do to reduce um some of the complexity.

[02:06:31]Uh but yeah, the if the math I I'd clean up the math stuff, but that's not really game important.

[02:06:38]You know, if if the game's running, then it's running. Um, but if you start having math problems, I guess it's with all these things like if you start having math problems, probably rather than fixing the math problems, it's better to just take a step back and fix some of the math cleanliness on the whole and see if you can abstract away things like endlite to fixing math bugs because you want to do a little bit of house cleaning and then the bugs will become apparent.

[02:07:09]Likewise with the state, if if there's like state bugs, do some house cleaning on the state first and that might illuminate the bugs and then as a byproduct you get cleaner code like in the Casey compression version. Um that's that's sort of what I do. But it it's it runs it ships. That's great. I love it.

[02:07:32]All right. Awesome. Thank you, Anon, for joining me for the review. Thank you, Spike, for submitting the code.

[02:07:41]Thanks everybody who joined in and tuned in to stay with us and look at the code.

[02:07:47]Thank you everybody.

[02:07:49]>> Thank you all.