Archiving Memory Addresses. (Gameshark)

[Trege]

So Chiz and a few other people have started doing stuff like this, so I figure I'll join in as well. I'll be archiving my codes here in hopes of it hopefully helping hackers find a way to eventually mod the game if the interest is high enough. It'd be great to someday have fan created content in the official Legends 1 or 2 games.

The Codes :

Currently I'm seeing a trend and I have no idea if I'm right or not, but most moveable objects seem to be using slots and the slots are shared between different areas.

[*Hardcore_Mode] (Basically just a reversed invincibility code you never blink after getting hit or knocked down.)
300B52C0 0000

Downtown (Affects every car even in City Hall or Uptown, but car design is different per area.) Results may vary by gameshark version.
[*Police Car speed]
8009D2F0 0000

[Decides whether the police car will stop for stop signs or not.]
8009D2F1 0000 = (Slow down for turns and stop for signs)
8009D2F1 FFFF = (Never slow down and never stop for signs.)


[*Police Car Acceleration]
8009D388 0000

[*Grey Car?]
8009D0D8 0000

[*Grey Car acceleration?]
8009D170 0000

[*Blue Truck]
8009D3FC 0000

[*Blue Truck Acceleration]
8009D494 0000

[*Red Car Speed]
8009D1E4 0000

Updated!
[Car Lighting modifier] (This code is pretty fun to mess around with it changes the lighting colour of a car, the car it affects depends on your story progress oddly.)
8009D254 7700
8009D256 0077




[Car Pattern Selector] (This Code appears to modify the spawning patterns of cars, however if the wrong pattern is used, stuff happens... I still
don't fully understand this code)
3009D2B8 0000
3009D2B9 0000

These car speed values above also affect how fast some Reaverbots act or run (Sometimes even their bullets), which is what makes me think slots are being used, or some form of data sharing.
These codes have yielded pretty crazy results, such as below.



I'll be adding more codes to this thread as I discover them.


Added : 3/20/2017 3:01AM


Enemy Scaling Code
Using HEX calculation I discovered a way to find enemy model scaling addresses.




Enemy 1's HP in HEX = 0295F176

Enemy 1's HP in Decimal = 43381110

+0235

Turns it into Enemy 1's X Scaler in Decimal = 43381345

Convert that to hex and you should get
0295F261 (The enemy's X scaling address.)


Each scaler is 2 digits apart, anything between those 2 digits should be left alone.

Example
X Scaler = 0295F261
Y Scaler = 0295F263
Z Scaler = 0295F265

When you convert their Current HP address to a decimal just add +235 to the address then convert it back to HEX to find their scaler, this is for the PS1 version however it does not always work.
Keep in mind that every enemy in Megaman Legends 1 has two HP addresses, one for their current HP, and one for their previous HP. You want to convert their current HP address to decimal then add +235 to the address not their Previous HP address.

The Previous HP and Current HP are 2 byte addresses in cheat engine.

Address Examples :

Cheat Engine :

Current HP
0295F176 0000

Previous HP
0295F1BA 0000

Gameshark : (These are 16 bit addresses, the last 4 digits of each are the HP amount for Enemy #1.)

Current HP
8009F176 1E61

Previous HP
8009F1BA 1E61

Those Gameshark values should be consistent across NTSC-U versions of the game.


If you're using an emulator the first few digits will always be different from the last time you ran the game, only by converting cheat engine codes to Gameshark can you keep consistency the easiest way to achieve this is to use a Gameshark scanning plugin for your emulator, and to set it to some absurd value then search for that value in the Gameshark scanner. (Chiz's idea.)


The pattern is applied to the enemies I've encountered so far, in theory many things in MML1 should be tracable once you find just one value the object is connected to.


The new Gameshark Codes :
(The last 4 digits are the scaling amount.)
Enemy #1 X, Y and Z Scaler.
3009F261 0001 <= (The last digit should always be larger than 0)
3009F263 0001 <= (The last digit should always be larger than 0)
3009F265 0001 <= (The last digit should always be larger than 0)

(This code usually changes the scaling of the first entity you encounter. basically whatever order the entity was placed in.)

Enemy #2 X, Y and Z Scaler.
3009F621 0001
3009F623 0001
3009F625 0001
(Exactly the same as the first code, but for the 2nd enemy instead.

[Rockman Striker]

Awesome! I'll definitely try to play in hard-core mode someday, it looks painfully fun.
If you find the code that controls the jet skate's speed, that would be even more awesome!

[Sybillian]

Suddenly I want someone to speedrun the game using the Flash-cars as a strategy to get around quickly.

[Trege]

Added : 3/20/2017 3:01AM


Enemy Scaling Code
Using HEX calculation I discovered a way to find enemy model scaling addresses.

Enemy 1's HP in HEX = 0295F176

Enemy 1's HP in Decimal = 43381110

+0235

Turns it into Enemy 1's X Scaler in Decimal = 43381345

Convert that to hex and you should get
0295F261 (The enemy's X scaling address.)


Each scaler is 2 digits apart, anything between those 2 digits should be left alone.

Example
X Scaler = 0295F261
Y Scaler = 0295F263
Z Scaler = 0295F265

When you convert their Current HP address to a decimal just add +235 to the address then convert it back to HEX to find their scaler, this is for the PS1 version however it does not always work.
Keep in mind that every enemy in Megaman Legends 1 has two HP addresses, one for their current HP, and one for their previous HP. You want to convert their current HP address to decimal then add +235 to the address not their Previous HP address.

The Previous HP and Current HP are 2 byte addresses in cheat engine.

Address Examples :

Cheat Engine :

Current HP
0295F176 0000

Previous HP
0295F1BA 0000

Gameshark : (These are 16 bit addresses, the last 4 digits of each are the HP amount for Enemy #1.)

Current HP
8009F176 1E61

Previous HP
8009F1BA 1E61

Those Gameshark values should be consistent across NTSC-U versions of the game.


If you're using an emulator the first few digits will always be different from the last time you ran the game, only by converting cheat engine codes to Gameshark can you keep consistency the easiest way to achieve this is to use a Gameshark scanning plugin for your emulator, and to set it to some absurd value then search for that value in the Gameshark scanner. (Chiz's idea.)


The pattern is applied to the enemies I've encountered so far, in theory many things in MML1 should be traceable once you find just one value the object is connected to.


The new Gameshark Codes :
(The last 4 digits are the scaling amount.)
Enemy #1 X, Y and Z Scaler.
3009F261 0001 <= (The last digit should always be larger than 0)
3009F263 0001 <= (The last digit should always be larger than 0)
3009F265 0001 <= (The last digit should always be larger than 0)

(This code usually changes the scaling of the first entity you encounter. basically whatever order the entity was placed in.)

Enemy #2 X, Y and Z Scaler.
3009F621 0001
3009F623 0001
3009F625 0001
(Exactly the same as the first code, but for the 2nd enemy instead.

Note #1 : There appears to be a pattern in the two scaling codes, or maybe I'm over thinking it, but I'm leaving this note here in case someone figures it out.
Enemy #1 X, Y and Z Scaler.
3009F261 0001
3009F263 0001
3009F265 0001

Enemy #2 X, Y and Z Scaler.
3009F621 0001
3009F623 0001
3009F625 0001

[Rockman Striker]

You're creating the foundations of what could become a beautiful new "Megaman should die" difficulty mode. I'm just hoping these mods don't make the game crash.

[Trege]

Nah, it should be fine. It's not editing anything the game doesn't already do itself, every object spawned has a predefined scale it's just hijacking the scaling multiplier basically. Plus I've played through the game multiple times with all of these enabled the entire time while finding new ones and it hasn't crashed yet.

The more complex codes that change enemy models into other in game models though, that has crashed a few times. But that's far more complex than altering the X, Y, and Z scale.

An example of the scaling MML1 was already doing was in the start menu when servbots kept changing sizes. You can sorta tell the Capcom Staff was having fun and testing things at the same time with it, given Mega Man Legends was the first 3d Mega Man game if I recall.

[Trege]

Hope you guys don't mind if I bump this, it's a rather important find.


Z Scaler Decimal
43780325
-347
43779978
Object Type Decimal


Convert result to hex to achieve the object type.

029C078A 0003 <=== 0003 = Zakobon
Code was found using PCSXR so the first 4 digits always change.



Gameshark Code : Due to a crash the gameshark code is for a different enemy slot than above.
300A078A 0003 <== 0003 = Zakobon (Trying to spawn a reaverbot outside the ruins will crash the game until a workaround is found.)
This allows you to change which Reaverbot spawns for this enemy slot, however only reaverbots that belong in that area can be swapped around currently.

[ShadyRounds]

I did this with an entirely different game back in the distant old days (the hex-editing, I mean), and remember seeing Tau post a lot about these. It was mind-blowing. To think that you actually dove deeper down the rabbit hole, is even more mind-blowing. It also gives me something to do in my free-time, with randomly modified enemies (if that's even remotely as cool as you make it sound).

As far as the spawning in an enemy, and it being area-dependent, I think that's normal since area codes exist, and as area templates load in and out, the assets an enemy use probably load in and out as well. I have no way to know how one would change this, is there a way to load one area using another area's assets (like a subgate in a broken state that loaded textures and enemies from subruins instead)?

You run the risk of highly destabilizing the game by doing it, but I suppose you could collect a massive capture of code-loading, and find whatever one area loads, different from another, and try to load one area while in another area. It might break the assets, trigger the blackout-loading-thing (you probably want to try intentionally not triggering the blackout), but it might just might "load two areas assets at once" and that would let you load reaverbots in city or something.

I wonder if you can load multiple "bank robber cars" this way? Just a thought. I'd bet you can, if they load it similar to how they do "reaverbots". If not, I'd reckon it has to do with a special "downtown bank robber chase" loaded-area that isn't the same downtown that loads when you enter the city.

[ShadyRounds]

Not to resurrect this or anything, but gameshark codes starting with 80, lead to psx ram values, so the ram values for city-automobiles come well before the npc-blocks? Do they share a similar area with old city dogs and other interaction objects like trash cans?