top of page
Search

[154] 3/2 Baked

  • Writer: Conlan Walker
    Conlan Walker
  • Apr 25
  • 2 min read

For the past month, I've been working on a software framework of sorts that solely uses the Win32 API to function. Specifically, GDI and WinMM for graphics and audio respectively.

I just finished a little maze game made in this framework!


It's not great, but I did crunch hard to get it done in basically 2 days,

namely Wednesday and Thursday in time to post this blog on Friday:

The main problem graphically is when textures are being stretched past the canvas.

It technically works, but it looks noticeably blocky.

It is reliable though and doesn't write past video memory, and that's good enough for me!

(Maybe I'll fix the drawing routines later, I dunno.)


Here's the line count for the game (almost 7.5k, though less than a sixth is the actual game code probably, with the rest just being supporting library stuff):






Notably, I made all but one of the wall textures (one is generated at runtime) in a paint program I also made, which you can see here:






Also, as a side project I made in a few hours, I wrote a python script that will generate text based on text you give it. This may or may not count as machine learning, so I'm calling it CrapGPT, in no small part because I literally came up with the idea in the bathroom.


Here's what it spits out when I train it on one of my friend's discord DMs.

Warning: strong language (if anyone cares lol):

What makes it funny is that sometimes it occasionally makes sense, before going right back to being incomprehensible.





And because I think it's funny to watch someone scroll past a monumental wall of code, here's the code from the 3 projects.


Let's go from the smallest up. Here's the code for CrapGPT:






Next is the paint program (This technically isn't all of the code, but all of the other code is also included in the maze game too!):






And finally, all of the maze game's code:


 
 
 

Comments


bottom of page