And just as a heads-up, some share-alike licenses, like the GNU GFDL, also have specific clauses which can make author-defined sections mandatory (non-removable and non-editable), called invariables. This means, if we wanted to be truly evil about it, we could write nasty things about Rune/GSCentral and make them invariable. This is a bad idea for several reasons, but it is an extreme option that may be necessary due to Rune/GSCentral's recent behavior regarding our work.
Well, we should include a history section, we could tell the tale of how fucked up Rune is, along with the hacking highlights and other interesting info/events through the years we've been on the scene. The GSC - Interact association, the ownership of the GS name, device history, etc.
Finally, Macrox is attempting to get the copyright loophole settled. The old documents will be a good source of reference, but copy-pasting things into a new XHTML format just will not work (at this point, I'm willing to consider this plagiarism in the interest of our license and authors). We still have to finalize the authoring guidelines before any of that work can be incorporated, any way. That will all be some time in the future, and in the meantime there are still plenty of other higher priority things to get polished.
I already wrote examples for most of the useful R4300i hacks. I don't intend on doing it from fucking scratch a second time, nor is it easy to find different games to write the same type of examples for in some cases. I can only hope that mac is able to fix this copyright problem. Then at least some of us can clean/update and reuse some of the shit we already spent so much time on. I don't think anyone wants to completely rewrite the code types info for stuff like GBA ARv3 (written by Kenobi, I believe). Most of those are pretty detailed explanations already, it would just need reformatted for XHTML and cleaned up.
Could PC hacking fit in here somewhere? I would love to see this document be a one stop for all that is game hacking. There are plenty of things that could be explained for PC such as code injection and in-game trainers and even how to make a basic trainer. If PC makes its way in we could all contribute functions that could be added into a trainer project to help people make trainers. Functions that you could pass a window title to be trained and pass addresses/values/codetype to be written.
Damn! I'm glad someone remembered that. We do need PC hacking info. Some guides on doing basic x86 hacks, maybe a trainer source code example, getting around games with hacker unfriendly code, etc.