ZGB VS sprite

This is a game jam where you make a Game Boy game in three months. If you don't know a lot of programming you can use GB Studio, you can learn the nitty gritty of how the Game Boy works by using assembly programming with RGBDS, or you can use C with GBDK or ZGB.

As of right now, I'm using the ZGB because it seemed simple enough, and I like C. And I'm using Gameboy Tile Designer for my sprites. I know that my player sprite's collision box is defined in the .gbr.meta file, and I figured out how to adjust the collision box dimensions like so:

If you'd like to learn to code (and I totally understand if that seems daunting or you just don't) there are some options short of coding it all yourself - for one, there are other, possibly more flexible engines. One I considered for a bit before rolling my own was https://github.com/Zal0/ZGB - he has several games with source available to help people get started.

It might not be the fastest or most accurate, but it's mine. I simultaneously worked on a C++ prototype and the actual emulator to have a good debugger. I found a few bugs in my programming language that were easy to track down and had to invest some time into optimizing the virtual machine to achieve the native speed of 60 fps. The idea of running an interpreter inside an interpreter, both written by me, is quite cool.