[Help]Player 1 size modifier code - Tiny Toon Adventures: DofU(PS2)

[LucybonesSquirrel]

So, GScentral.org has been almost dead for a long while now, so I thought it was time for me to move on to this place instead.

Anyway, I have been attempting lately to make a Player 1 size modifier code for Tiny Toon Adventures: Defenders of the Universe for PS2(it's an unreleased game, just to clarify). So far I have found the floating point values that sets the size of the player for his/her X, Y, and Z dimensions(3F800000 by default), which when set differently will also cause the player to run slower/faster and jump lower/higher, with altered collision box to compensate for the new size. Example image of the desired effect below:



Now, the problem is; their offsets doesn't always stay the same, which makes it troublesome to actually get a code that works all the time. I'm not very experienced in areas like ASM and pointers. I can modify ASM instructions already present in a game, but that's about it. Speaking about pointers, I seem to have found one which can give a clue or two about where the data for Player 1 currently are located in RAM, 0x04063E4 00??????(where "??????" could be any offset, usually around at 0x5?????-0x7?????). I know it could be useful in someway to make a size modifier, but I just don't know exactly how.

The only tools I have at my disposal for hacking PS2 games with are Renegade, which is mostly useful for finding simple codes(that also stays static), Tsearch, and PCSX2 1.2.1. If there's any other tools I should use, then tell me about those.

Would be glad to get some help or advice from people more experienced within this area.

[dlevere]

This is a GameShark tutorial...

But it may help you.

:::Hacking Size Modifiers:::
By: Goldenboy
For: Nintendo 64, PSX, Saturn

=======================
Vital Code Info:
=======================
Difficulty: 8 (out of 10)

What it is: A size modifier is just that. It modifies the size of an object, person, or character in a game.

Does every game have one?: Most likely. 3D games always have them, but 2D games are less likely to.

=======================
Before you start:
=======================
You need to figure out what you want to make a size modifier for (an object, character, etc.)

=======================
Know this*:
=======================
A Size Modifier can be a pointer or it can be an actual size modifier. Usually, a pointer is an 8 Bit code, and an actual Size Modifier is 16 Bit.

The default Size Modifier value is usually 3F80 (16256) in games. It is not known as to why developers choose this value over others (instead of 0000 for example).

Some of the size mod values that I've seen:
3F80 (16256), 3C00 (15360), 3E80 (16000), and 3DCC (15820).

What are pointer Size Modifiers? They are usually 8 Bit codes that point to certain addresses with the Size Modifier value. Example: 0=size 1, 1=size 2, etc...

*In most, but not all, games.
=======================
Hacking The Code:
=======================
Method 1 (unknown):
+++++++++++++++++++
Important! The following search should be done in 8 Bit AND 16 Bit, because you could find a pointer Size Mod, or an actual Size Mod.
1. Start an unknown value search.
2. Do something that will make your object change in size (i.e. shrink or get bigger).
3. Do a Different To search.
4. While still that size search Equal To.
5. Do a couple of more Equal To searches (if possible).
6. Change size again and search Different To.
7. Do a Equal To search while still that size.
8. Change size and do a Different To.
9.Repeat steps 2 through 8 until code is found.

If you believe that you've found you code, turn it on. Now do something that would normally change your object's/character's size. If his size stays the same, then you've found the code.

Method 2 (blind hacking):
+++++++++++++++++++++++++
1. Find the coordinates of the object/character (see hacking coordinate mods).
2. Go into the memory editor near the area where the objects coordinate mods are.
3. First, look for 3F80 (change to 3FF0)... If no 3F80 values are present, look for some other obvious values (mentioned earlier).
4. Change some of the values then go back into the game and see if the object's size has changed. Go back into the memory editor. If the addresses that you have changed have gone back to normal, those might be size mods. In this case, you'll need to turn that address into an actual code, by reseting the game, typing in the code with it's new value (i.g. 3FF0). Start the game and if the size is NOW changed, then you'll have to do this with the rest of the Size Mods you find.

=======================
History:
=======================
Started: 8/13/01
Finished: 8/13/01

Source

[LucybonesSquirrel]

Well, I made my own test by seeing if a character's Y-size changed when getting flattened, but it stayed at 3F800000, so the size of a character doesn't seem to change. The issue is that the location of the Player size values won't stay the same; the true offsets always differ after each playthrough.

I will have a look at the tutorial though. Maybe I can learn a thing or two from it.

[rimsky82]

LucybonesSquirrel

Welcome. Some of those involved with gscentral.org and our site may still have their differences, but for the sake of the scene I welcome any regulars of that site to reside here until they come back, and even after if they so desire.

So please, make yourself at home. I'm happy to see some work being done on the PS2, something I have not yet attempted myself.