SCHG How-tos

Before we start adding more things to this category, might I suggest:

• We establish some consistency in page titles, because it's not remotely clear at first glance which how-tos belong to which game.
• Somebody posts a list of all the outdated garbage we no longer need. So I can delete it.
• We work towards more "open" solutions to problems, rather than "this is a guide made by XXX give me all the credit in the world I am so great". Perhaps it could be a hacking guide maintained by the community.
• Formatting, images etc. - lots of its sucks, but that's what happens when you mash 15 years of work together without maintaining it properly.

I would also quite like to group these depending on what each guide is trying to achieve, specifically separating bug fixing from adding new features. And really assessing whether we need to care about new features, because theoretically you could add anything to a game - when does it end?

I think a much better plan of action is to say "here is a game" (e.g. Sonic 2), and "this is how it works", as opposed to "here's how you change parts of it".

So perhaps you could have a high-level plan of the retail binary file and point out where the code lives, or where the art is, and how it's executed... or go into agonising detail with the most recent disassembly as a reference. I personally don't know how you would begin to describe "how it works" but this wiki could do with trying to answer that question. People presumably know at least part of the answer otherwise these guides couldn't exist.

And cruicially in the Mega Drive games' case, "how Sonic 2 works differently to Sonic 1". Things non-hackers (like myself) might actually be interested in.

Equally I want to document "how it doesn't work", which means joining up Sonic the Hedgehog 2 (16-bit) bug list with the bugs these guides claim to fix. But getting the four points above sorted is more of a priority -Black Squirrel (talk) 10:52, 25 August 2018 (CDT)