If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below. Also, before requesting
codes, note that there is a main site, which may contain what you
are looking for already. Also, if you know what you want, feel free to
search for it directly.
Here is my first WTW code for a 3D game.
Thanks for the link though, I've tried before to make the game think I'm not near or touching a wall but to no avail.
Every game uses a coordinate system to position a given object or character. These coordinates are located on a set of invisible axes. Two-dimensional games use two axes, referred to as the X and Y axes. Three dimensional games rely on three axes, referred to as the X, Y, and Z axes. The X axis is used for left/right movement, the Y axis for down/up movement, and the Z axis for near/far movement.
As an object's X coordinate increases, it is moved to the right, and vice-versa. The same rule applies for the other axes. It is important to note that these axes have nothing to do with what is shown on the game screen.
For example: the Y coordinate measures an object's absolute height, as opposed to how high the object is relative to the ground. It is recommended that 32-bit searches are used for three-dimensional games if the emulator or trainer has that option, although 16-bit searches will work just as well.
For two dimensional games, 16-bit searches are usually sufficient.
Identify the target object or character, preferably one whose movement can be controlled by the player. Begin an unknown value search.
Identify the target axis. Hacking with only one axis in mind is much easier than attempting to keep track of movement on multiple axes. Remember that causing a change in the character's Y coordinates requires movement to a higher position in the level, which may not be easily accessible, so choosing to hack the X or Z coordinate may be easier.
Move the character several game "feet"/"meters" to the left, right, away from the camera, or towards the camera. Perform a Different To search. It's important to move the character far enough away from the original point if doing a 16-bit search.
As each coordinate is usually 32 bits in length (in three-dimensional games), it's extremely important to move the character so that the first half of the value changes.
For example: 0x12345678 would need to become 0x1235789A (or higher) so that a 16-bit search registers the change and doesn't discard a potential code. This is not an issue with 32-bit searches.
Move the character in the opposite direction, keeping the above warning in mind. Perform another Different To search.
Repeat steps 3 and 4 until there is a manageable number of results, preferably less than 20 or 30.
Test each code until the target character's movement on one axis is restricted.
Now the codes for the other two axes need to be found. They will usually be in close proximity to the code that was just hacked. On some systems, one can usually find another part of the code by adding or subtracting 0x04 to or from the newly-found code's offset. The offset containing the X coordinate is usually first, followed by the Y coordinate, and then the Z coordinate. Note the existing values for the surrounding offsets and enter those as codes.
If the character is unable to move to the side or toward the game camera, then the correct code for the X or Z coordinate has most likely been found.
If the character is unable to jump, then the correct code for the Y coordinate has most likely been found.
The first 16 bits of the value are usually enough to change a character or object's position, so assign those to a code and enjoy the results.
Due to their nature, position modifiers are very easy to find usable values for. Simply view the offsets from each of the codes for the target character/object's coordinates, and apply those to the target character/object's position modifier, or a completely different object's position modifier.
The WTW code I found for the HM games works fine, the hardest code to find was one that made him walk in air. I searched at least 8 hours before I found it, I found the Y position of Hitman and thought I could make a walk on that way but as far as I got was a slow decent code. The only way I found a walk on air code was by measuring his drop speed, one I found that it was all I needed, the walk on air code I made basically stops him from descending, a bonus of the code is that he actually is walking/running instead of his usual fall animation. I would love to make these codes for Blood Money but it's too slow and the screen goes black on pcsx2 when you get in a a level. Hitman Contracts has the same problem, the only way the WTW+on air code was made was by finding the same/similar values/hex patterns.
Move off of start then move back and a hand will pull you in and you can play the level.
Not tested on worlds other than 1. If it doesn't seem to work at first, wait a little while on the map screen then move back to start, seems to have timing issues.
Move off of start then move back and a hand will pull you in and you can play the level.
Not tested on worlds other than 1. If it doesn't seem to work at first, wait a little while on the map screen then move back to start, seems to have timing issues.
47iscool have you tried DarhkDiaz's code that lets you enter any spot on the map i remember using that code and a walk anywhere on the map on a real system with good results
ESKKKTEY
47iscool have you tried DarhkDiaz's code that lets you enter any spot on the map i remember using that code and a walk anywhere on the map on a real system with good results
ESKKKTEY
Yep, NB82 pointed me to that code. If I'm correct it only lets you replay levels that you originally could.
Comment