melee VS slippi-ssbm-asm

They're ~11% of the way there https://github.com/doldecomp/melee

Not sure if this is what you're looking for, but helping with this open source project could probably help towards your goal!

And, of course, look at the github for more information: https://github.com/doldecomp/melee

This is a WIP decompilation of Super Smash Bros. Melee. The purpose of the project is to recreate a source code base for the game from scratch, using information found inside the game along with static and/or dynamic analysis. It is not producing a PC port. however, such a thing could possibly be made once the decompilation is complete.

Mate, you don't have to take my word for it. You can look at the GitHub repo for slippi ASM and see that they are putting in desync detection through ASM in the game itself. https://github.com/project-slippi/slippi-ssbm-asm/pull/99

Currently, much of Melee modding (including all of the advances done in Slippi) is done by manually poking the memory using raw assembly. As a result, development is slow due to the higher barrier to entry and lack of information about what the game is really doing. Most improvements were found by dynamically reversing the game and keeping track of what happens in-memory while the game is executing.

https://github.com/project-slippi/slippi-ssbm-asm#build-instructions

Besides the scarcity of resources, I think the biggest barrier to entry for complex melee modding (e.g. stuff like adding new gamemodes or completely new features) is Assembly code. Recently I have been working on a small quality of life Slippi feature that fixes an issue where if one is player pauses then leaves in direct connect mode, the other players is left stuck unable to unpause the game, and therefore must restart the emulation. On paper this fix is as simple as (1.) detecting when a player has both paused and disconnected and (2.) unpausing when this condition is met. Let’s look at the assembly I had to write (and yoink) to sketchily fix this issue!

here's the commit