The project is hosted on a git repository on GitHub, under the ShiningForceCentral account :
The main purposes of SF2DISASM are :
- to produce tools and sourcecode capable of building a bit-perfect replica of the game,
- to identify, split, label, comment and document the game's content,
- and ultimately, to provide a flexible way of creating new games, hacks and mods based on Shining Force II.
Original post :
Here is what I just set up : https://github.com/ShiningForceCentral/SF2DISASM
Two main places :
- The repository contains the disassembly in ASM text format. No IDA-related stuff in there, just text and some scripts to build a bit-perfect replica of the game, and possibly starting new hacks from here. Anybody can easily get the repo's content, as it has a direct download link : https://github.com/ShiningForceCentral/SF2DISASM/archive/master.zip
- The associated wiki, which I hope will be simple enough for anybody to contribute with anything possible ! I have only started with a few easy lists from BNC's notes (address maps, indexes ...) but really, anything can be written in this wiki as long as it can be of any use in the SF2 community.
Other functionalities could be used, like issue tracking for requests or problem-fixing related to the disassembly.
Along with this repository, I have created the ShiningForceCentral github organization account, so that any other similar project can be created. I still think we can get a lot of inspiration from what the Sonic retro community has been doing for years now : https://github.com/sonicretro
I had never used GitHub before today, but it looks like it is the most appropriate place for what we need.
I hope you guys will agree and contribute by giving your opinion on how to have a proper use of github according to our needs. Maybe the wiki is not simple enough for quick note writing, or is too tedious for proper formatting. Maybe we can use the repository also for documentation in txt files, I don't know, so yeah all of this is open to discussion really
I'll be glad to give control of the sfc github organization to proper SFC mods if they ask me, as I think this could be used for any other SF-related project.
So yeah, erm, discuss.
Maybe I should give a bit more details about the disassembly that can be built, because there is some funny hacking potential here :
With this repository's content and the original rom, anybody can build the game from the ASM code.
And ... anybody with a bit of ASM reading/writing skills can try to modify the game's code in ASM, instead of tedious hex editing !
Beware though : since the disassembly is far from complete, a lot of instructions and data chunks need to be properly formatted before you can really do anything you want. What I mean is that it might be a matter of trial and error to see what is feasible and what is not.
And this is where the issue tracking function of GitHub could be useful if you want to share what limitations of the current disassembly you've found, and where it should make progress to become easier to edit.
Just a quick example of ASM editing for beginners, search the following line in disasm/sf2.asm :
- Code: Select all
mulu.w #5,d2 ; THE MOST TERRIBLE BUG OF VIDEO GAME HISTORY
Currently it should be at line 11021.
Change "#5" value with "#7" instead, save, build the rom (after splitting the original one of course), and there you go, battle chest bug is fixed, you are an awesome ASM hacker now.