gbdk-2020 VS sm64

If you want to program the Gameboy or Gameboy color with C or C++ the SDCC compiler is typically used: https://sdcc.sourceforge.net/ There's a ton of good info and dev tools here: https://github.com/gbdk-2020/gbdk-2020

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.

I was messing around with GBDK just last night, so I'm in no position to poke fun at you ;)

There is a c library for this. https://github.com/gbdk-2020/gbdk-2020

If you have some programming experience, you can make your game using languages ​​like C and assembly. However, you don’t need to know how to code to start making your own game. There’s a free and open source game creator named GB Studio, that allows you to create your own title using a drag and drop tool. In this case, I decided to use C with the GBDK 2020 library for my project, as it gave me adequate flexibility without the need to dive into a low-level language like assembly to do so. You can read this guide to choose which tool suits you best.

Last year i got started making Gameboy homebrew games. As a way to better learn the process, i decided to try re-making some classic games. In addition, i would post a tutorial. They say "In learning you teach, and in teaching you learn". This rings true for me, as in writing these tutorials it forces me to really analyze what aspects of game development i understand and what aspects i do not. Most recently i remade Space Invaders using GBDK-2020 and C. All source code and assets are available for free on GitHub.

To fix this, some very recent communities are working on updated versions of the library without these issues: GBDK-N and GBDK 2020. I've personally moved on to the latter, but any tutorials for the original GBDK are still valid, such as the rudimentary ones on the GBDK wiki, or most notably Gaming Monsters' Youtube chanel (which sadly didn't exist when I got into GB development lol).

The SM64 is still going strong https://github.com/n64decomp/sm64

Nintendo won't allow any binaries floating around though.

Romhacks are typically modifying the compiled binary ROM image. Kaze' work is based on the painstakingly disassembled code from the n64decomp project[1]. He's working in C, modifying the game and compiling it again for the original hardware. Not sure I'd call that a "romhack".

Great videos though!

[1] https://github.com/n64decomp/sm64

A team or something reverse engineered super mario. I think that's the repo and it's mostly in C

From course_table.h and course_defines.h we can find that: COURSE_MIN == 0 and COURSE_MAX == 25 - so it looks like every secret stage is a full-fledged "course" for the purposes of counting stars, bringing us to 25 courses + castle stars (COURSE_NONE). So, the maximum possible value for starCount should be 7 * 26 = 182.

Multi-year decompilation project: https://github.com/n64decomp/sm64

The port source code of the decompilation is still up on github and Nintendo hasn't taken it down in years, cause they can't since everything has been done with legal methods

This is false, the source code never leaked; it was meticulously and painstakingly decompiled by hand.

It sounds like, rather than a ground-up rewrite, COBOL should be treated as an object-code language, and "hand-decompiled" (ala efforts like https://github.com/n64decomp/sm64) into an HLL that can, at every point, be losslessly transpiled back into the original COBOL.

I know the tooling for doing that doesn't currently exist... but paying someone to develop it would be cheaper than any one of these ground-up rewrite projects!