I find it very readable and think it fits really well, actually.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
If you scan a bank and find an invalid opcode, then it probably doesn't have any program data in it.Lolwut? Err, no. Please actually look at a gb game once in a while before giving out this kind of misinformation.
Actually that wouldn't work with the games I chose. Pokemon Red / Blue are known for plopping data sections scattered all throughout the ROM. It's known for it's disorganization and all the data is highly compressed meaning there's a very large amount of data sections. To add to the mess and data section's Pokemon games have several other data types besides pictures, text, and music that are specific only to Pokemon games in general. If your the type of person who likes a tough challenge then you see why I chose Pokemon Red/Blue specifically instead of the others which were simplified.While RBGY feature programming abomination after abomination, they are not particularly different from other games in their data management ― meaning it isn't particularly scattered just to be scattered. It just seems the compiler/programmer did a really bad job of organizing things every once in a while.
I'm trying to make a very advanced tracer that traces every function call and jump, disassembles the opcodes, and breaks it up into function blocks.So another IDA Pro?
The leftover data is placed in a separate file to be linked in the exact same position as the original game.Won't work. Once you edit it and some banks cannot hold data anymore, what do you do? You will have to move data and update all references, some of which might be circumstantial base offset trickery with multiplication etc...
Comments will be placed for the obvious lines like changes to a gameboy register.Shouldn't it work the other way around? Place comments for things that aren't obvious?
All variables will have their own file named by their starting position in hexadecimal.I think you mean variable name and not file name. Or are you going to extract RAM maps, too?
The purpose of this project is to fulfill a need for one. There is no program like this as far as I know, in case your wondering why you would ever need something like this is because it greatly if not admirably simplifies rom hacking. basically everything is done for you - all you have to do is skim through the disassembly and make sense out of it with the added bonus you have the full disassembly. No more spending days and weeks getting a memory map and how the sprites and graphics are generated and their locations.This still requires much effort on the part of the hacker. You won't find a program that will tell you the how and the why of most things. You should IMO strive to be very good at identifying all pointers etc, since those needn't be in any native format at all, or needn't be immediate values somewhere. Instead, it can use an id, multiply it by some factor, add an offset, flip some bits and voila, pointer ready. You will have to account for those things... or at least you should.
Haha, yeah. I was really tired when I did that, and couldn't think of a homonym for "movement power" at the time that didn't sound Engrishy. Mobility works just fine. ^^;
And yet, Assassin is a homonym.
Hahaha! Whoops. That's what I get for posting directly after waking up.
I meant synonym. [...]
Alternate, in EUC format since the Shift-JIS version doesn't like to display properly in the last JWPCE for some reason.
I also think the dissapearing/reappearing thing is caused by the compares. Problem with FE is that if you remove the handakuten compares, the whole text routine screws up.
Yeah, her name is definitely Sheeda. Dunno where you got Caeda. >_>
Also, is it just me, or does the text look funny as it's spilling out?
Someone might want to double-check me on this, but I think it's right. The bytes "42 26 31 32" insert the player's name, and there might be a blank space opcode in there. The bytes "20 22" seem to be a carriage return command.
Well, actually, I take back the one-byte observation -- looking at this again, the character "い" repeated in Jowy's textbox only matches up if the first Kanji, "気," is interpreted as a two-byte value. Is it possible Hiragana and Katakana are one-byte values, with two-byte values reserved for Kanji and certain text display opcodes?
QuoteIt shows the dexterously of the character.
Change "dexterously" to "dexterousness."
I never thought I'd see the day where people were harassed online for using proper formatting.
ISO 639 recognized languages only for Translation classification. Anything else would be classified as a Hack.Why not use the private area of ISO 639-3 resp ISO 639-2? All codes starting with q are reserved for local use, so there should be no problem with that.
|Esperanto||epo resp. eo|
|Ido||ido resp io|
|Interlingua||ina resp. ia|
|Lingua Franca Nova||lfn|
|Lojban||jbo resp. io|
|Occidental||ile resp. ie|
|Volapük||vol resp. vo|
In the defense of keeping it in the database, it is a translation to another language. A fictional one sure, but translatable nonetheless.