[haxxxen]

@bungholio
real time memory edit is useless if you do not know the offsets. so you still have to use ida pro. do you even have tried it? guess not...

[gingerbread]

Originally Posted by haxxxen @gingerbread , you have not noticed the edit on my post about the codes not working. silent hill downpour BLUS30565 the speed modifier aka faster gamespeed only works as eboot hack and not with codeunique

Thanks for pointing it out to me. Out of curiosity can I add a second line to that cheat "000030000 00000000 00000000" so that the tool tip is flagged as eboot only.

[haxxxen]

of course you can
i am using 00000000 00000000 00000000 codes as spacer for descriptions

[anamsel007]

Excuse me, sorry, I was just learning, but I do not know, how do you find the code number to be changed, because I wanted to learn to know!

For example, I've decrypt eboot.bin into eboot.elf I open a hex editor, but I do not know which numbers should I change? anyone can help me?

thank you very much in advance

[gingerbread]

I have updated the repository.

PHP Code:

Version 0.98 (Feb 15, 2013) - 521
- Added Hitman Absolution JP // xtatu from CMP
- Updated Silent Hill Downpour US 


PS3 Cheats Editor by Aldo (Latest Version 2.6.3)

http://aldostools.org/temp/PS3_Cheats_Editor_installer.rar

[bungholio]

Originally Posted by haxxxen @bungholio real time memory edit is useless if you do not know the offsets. so you still have to use ida pro. do you even have tried it? guess not...

What does "don't know the offsets" mean? Offsets of what? I haven't tried it, but all you are doing is looking at game memory while playing and modifying it. If you can modify while playing, you can modify game ASM while playing to get address locations of things in memory, and those are the only offsets I can think of that people are talking about.

[haxxxen]

the problem with this is, the memory/values is/are constantly changing. i cannot determine anything from this, but maybe it is only me. i think you still have to use the real time disassembly.
trial and error also does not work, as the game freezes if anything wrong will be changed, so it takes a lot of reboots.
it was the first thing i thought of when dex was released. unluckily it is not like the old psx xploder real time memory edit, which was so easy with its own search engine.

i guess i have still to learn a lot of stuff about this, but it is not easy for me getting along with a disassembler and ppc instructions. i always loose my patience with this.

[bungholio]

I just went through the long thread for this on the NGU forums to see if there was some mention of "offsets" being a problem. All I could see is that they have a different idea of the meaning of offset than me. From what they were talking about, just having trouble finding the correct addresses in memory for codes. Some games will use DMA crap to have games change the address of things in memory while playing, others don't. For some CodeUnique codes, some codes for a game will be constant writes to a memory address that always seems to be the same place every time for everybody, other codes for the same game may change from something as simple as restarting an entire game, loading a checkpoint, dying and restarting, going to another level, or all kinds of different things. In that case you just find the pointer or pointers. The tools have the ability to set breakpoints or other things, and those are perfect for stopping a game the instant something you select changes, like pointers. If you get bored dealing with the pointers, you might get away with just making a code out of the ASM code the first breakpoint you set finds, and be done without it affecting multiple things like enemies too instead of just players, and even if that occurs maybe you can check how many functions jump to the function you ended up in and then cancel the right 1 and it will only affect you.

I wouldn't be surprised if games changing locations of things in memory while playing chases everyone away, it's an easy way to weed out the many who don't know how to do anything beyond searching for themselves having $999 and then buying a few things and ending up with a code in just a matter of seconds. They start up the game and realize that the code only works some times and not others, they think to try again because they made a mistake. They play again, same problem, and they give up. All it could have been was 1 simple pointer at an address and things would work perfectly every time. No matter how much things move around in memory while playing, many things will always be constants that never change. You might find that one address that changes in memory, and that address contains another address. You go to that address, and somewhere nearby it is another address, and that address has your health. You have something that never changes its location in memory that has a certain path to something that never changes. It can be a little bit of a maze. Things go from finding the address that never changes to finding the path to the address that never changes, and you always start at the end of that path and work your way back to the beginning to where it all starts and where the starting point never changes.


I'd strongly recommend the tutorial for the pc program called "Cheat Engine". That's where I first had a chance to learn about pointers and how to find them.

[FreddyRossy]

Dead Space 3 does not work. im on rebug 3.55

[kik4444]

Can someone make a cheat pkg for Metal Gear Rising? And and BTW, if I want to go back to 3.55, I just have to dehash, put on official 3.55 and then do I put on Rogero 3.55 or Rebug 3.55?