' Seriously? The scripts they put up are supposed to be compatible with all kinds of data.rsdk version files, given some might have missing things, such as some Sonic 2 rsdks not having Egg Gauntlet (this is a topic for another time.

But I know I'm not the only one who thinks this in the people who follow me. But hey, it is useless for me to dwell on this subject. People did not want to fully respect SEGA's EULA, consider the scripts to be theirs and the modifications but the reality is quite different. And I don't really care what people think about that. 'Your previous actions from not too long ago are the reason why SIR, as well as the old Decomp Refresh project to completely shut down and give you such a bad reputation.'. Strangely enough, the people doing mods on CrossCode or mods on Minecraft (best example) for instance don't have this problem: just that they are more orderly and more logical in their way of doing things? Think in the spirit of a Minecraft Modder and you will understand. What do you think? That each OS environment does not update by changing the version of its libraries? Well, it's the same for mods. Before making mods, you will have to understand the concept of version before creating them. Welcome to Programming World ? It is not an issue for me. So if you think about it, if you made a whole mod that is just a bunch of patch files, including patches for scripts, and you want to make a tool that can extract the scripts from the bytecode of any version rsdk of Sonic 1 / 2 mobile, then you'd have to make patches for EACH file variant. This is apparent especially in the Rom hacking scene in Mario 64. This causes issues even if the file's contents are near identical to what you'd want. Why? Because all files within each RSDK have different hashes. 'Also, patches will never work for mods on the decomps, like SoN1C here mentioned.

Sonic 1 sonic sprite sheet