sm64 VS CnC_Remastered_Collection

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!

That's just a clone game though. And the originals were actually made open source with the release of the remaster.

Not most, but quite a few legendary ones were released in a "source available engine, paid maps" kind of way. Check out Id Software's github for a couple versions of DOOM, Quake and Wolfenstein. EA has released Command & Conquer's source code (here).

You could just look through the source code and see if you can spot anything though.

If anyone curious about some historic examples here is the pathfinding code from the C&C/Red Alert games

>The path algorithm works by following a LOS path to the target. If it collides with an impassable spot, it uses an Edge following routine to get around it. The edge follower moves along the edge in a clockwise or counter clockwise fashion until finding the destination spot. The destination is determined by Find_Path. It is the first passable that can be reached (so it will handle the doughnut case, where there is a passable in the center of an unreachable area).

https://github.com/electronicarts/CnC_Remastered_Collection/...

https://github.com/electronicarts/CnC_Remastered_Collection/...

That being said bespoke development being done badly is the source of horror stories. It's like old games C++ being notoriously "horrible garbage hacks" and yet, code like this or this is very well documented and not bad.

What do you more than this? https://github.com/electronicarts/CnC_Remastered_Collection

I merged the upstream branch of the source code into my mod branch, did a new build, moved teh required files into the mod folder and confirmed the mod worked locally.

The source is wrapped up in DLLs so it can run in their frontend, but all of the old game source is there: https://github.com/electronicarts/CnC_Remastered_Collection

As a specific example, the code for the Command & Conquer video games was released by Electronic Arts awhile back. Looking at some of the code for C&C: Red Alert (https://github.com/electronicarts/CnC_Remastered_Collection/tree/master/REDALERT), I was struck by how many comments were included. For example, this is a snippet from one of the source files (HOUSE.CPP):