Gameplay-hacking Aladdin

[Jedi QuestMaster]

While graphics hacking Aladdin (this game), I decided to split the project into two hacks: gameplay and graphics.

But before getting started, I'd first like to know which version of the game I have. I can't find it anywhere.

It seems to be this one:

• 1995 Copyright
• no weird number designations in the title
• music plays normally throughout the game

Anyway, gameplay mechanics I'd like to fix are:

• switch A & B buttons
• change running physics
• 'rug-gliding' speed (the way it works in this game makes it almost entirely useless)

[Sik]

How about just posting a MD5 checksum of the ROM? Somebody can probably try to hunt it down then.

[Jedi QuestMaster]

Because... I don't know what an MD5 checksum is.

And I think I may have overwritten my rom.

[tepples]

Use the Google.

• MD5 article on Wikipedia
• md5sum article on Wikipedia

[Sik]

And I think I may have overwritten my rom.

How are you making IPS patches then? o_O (you need the original ROM to base the patch on)

[tepples]

Apparently the different dumps are so similar that an IPS patch to one applies cleanly to the others. It's like Game Genie codes that work on more than one revision of a ROM.

[Jedi QuestMaster]

How are you making IPS patches then? o_O (you need the original ROM to base the patch on)

I haven't made an ips file since this screw up. So for now I'm good.

By the way, I think FARID found what I'm looking for: Aladdin (Unl) [p1][hM04].nes

Edit: The exact one I was using is Aladdin (E) [p1][hM04], and the only difference between this and the (Unl) one is byte 06, which reads '40' on the (Unl) one and '41' on the (E) version.

By the way, what does [p1] mean? I assumed it meant 'pirate' but wouldn't that only be used if the game is further pirated from its original state?

[Dwedit]

The original game wasn't MMC3.

[Jedi QuestMaster]

This one is hacked to mapper 4. But what was the original?

Would a graphics patch not work correctly for both? I do recall reading that there's a graphical glitch on the ending screen due to this.

[Sik]

I imagine the original was a custom mapper.

[tokumaru]

Or maybe that crazy Mapper 90.

[lidnariq]

Yeah, it was mapper 90.

[OneCrudeDude]

Speaking of gameplay hacking, the game can and will freeze under varying conditions. Once I managed to jump down, following a path of gems into the area where the snakes pop up, and the game froze. I also jumped on one of the enemies while I was close to a wall, and Aladdin jumped in a wall and crashed the game.

These were observed in FCEUX, so no telling if it's the emulator or the game doing it.

[Jedi QuestMaster]

So I assume the mirroring values are arbitrary because there's absolutely nothing else different between the two roms.

Speaking of gameplay hacking, the game can and will freeze under varying conditions. Once I managed to jump down, following a path of gems into the area where the snakes pop up, and the game froze. I also jumped on one of the enemies while I was close to a wall, and Aladdin jumped in a wall and crashed the game.

These were observed in FCEUX, so no telling if it's the emulator or the game doing it.

Either way, it'd be a good idea to playtest this on real hardware. I've noticed the game freeze a couple of times. Once on the Genie's lamp stage. I think it may have had to do with the enemies on screen.

By the way. I know jack about hacking buttons. How would I go about this? So far I've found that changing address 03D0A5 from 80 to 40 makes the 'B' button throw apples, but not while he's running.

[Sik]

That probably means the game has a different check for throwing apples while running. Yeah, there isn't much more to it, just keep looking around.

The game is storing the controller input in some byte in RAM then checking it afterwards, right? If so, just look for places in the code that attempt to access that byte. Not sure how easy you have that though, but it'll most likely show you all of the code accessing the controller.