zelda3 VS pokeruby

Zelda3 - Zelda 3 clone. C, SDL2

here’s the GitHub link to it. there is also a native PC port of Ocarina of time called ship of harkinian. I highly recommend playing these games in their native pc ports for a more modern way with some QoL changes.

The Legend of Zelda A Link To The Past Decompilation: https://github.com/snesrev/zelda3

Have you tried to follow the instructions from the Zelda3 official GitHub page?.

I recently imported US version so I can have a legal rom for the PC port. Highly recommend, runs awesome, with widescreen support etc.

i have looked into reverse engiring games from things like the legend of zelda project of RE games. i came across the port of ALTTP which is here: https://github.com/snesrev/zelda3. im intrested in both learning how games work and more importantly porting them into a more readable langauges. I havent started learning anything as i want to understand the fundamentals and the back bones into creating a port. While i started on looking into programming langauges i found actually picking one diffecult. They all seem to have diffrent use cases but i want one that is easy to start off with, i was thinking of either c# or c++, even after picking a code language to settle on, with a port of older games, how does a game engine come into play? iv seen people talking about unity or unreal, but im a little confused on that. can i create a game entirly without a game engine? is porting a game without an engine a good idea? it says the ALTTP was made in c but does it use a game engine or not?

An amazing version right now would be the unofficial PC port based on a decompilation of the actual SNES game. It has a bunch of additional features like widescreen and MSU support.

Let's not forget this, either: https://github.com/snesrev/zelda3

Pokémon Ruby/Sapphire, Pokémon FireRed/LeafGreen and Pokémon Emerald.

The Ruby/Sapphire disassembly on GitHub lists the parties and IVs: https://github.com/pret/pokeruby/blob/master/src/data/trainer_parties.h (use control + F). The IVs are given as numbers out of 255, so multiply by 31/255 and round down to get the actual IV. For example, if the IV is listed as 200, then the actual IV is floor(31 * 200 / 255) = 24. The disassembly also contains other information like items: https://github.com/pret/pokeruby/blob/master/src/data/trainers_en.h. Unnamed grunts are only identified by a number, but you can compare them with the parties of grunts listed on Bulbapedia.

https://github.com/pret/pokeruby/blob/master/src/wild_encounter.c Here is the dissasembly as well.

here

You could always take a look at these decompilation projects on GitHub by Pret (it’s pretty interesting IMO!)