OK, but something like that seems incredibly unlikely. The basic memory architecture and operating system design of a PC explicitly prohibits messing with the RAM belonging to another process unless you have either kernel level memory access. (which is mainly just the OS kernel itself, and system drivers), or manage to find a security hole or patch the trainer into the game's executable so it operates from the same process as the game it is modifying.LordLundar said:You're confusing a save editor with a trainer. A save editor does what you are describing. A trainer does modify memory values but those values are stored in RAM and at the worst case scenario causes the game to crash which will force the game to be shut down and be purged from the RAM. In fact, a poorly made save editor is FAR more hazardous to a game than a poorly made trainer because of the temporary nature of what the trainer affects while a save editor can corrupt the save completely which would require the player to start over.CrystalShadow said:Anyway, most trainers I know of don't do anything to the memory of a running process. They alter the data in the save files.
At worst that will crash a game, depending on how robust the code that loads save files is...
More likely if it messes something up the file will just get treated as being unreadable and ignored...
Hardly the same level of risk as memory hacks...
But as I said, how would even do that with any code that doesn't set off a dozen security warnings?
It seems highly unlikely to be something that is commonplace.
Do you know what a General Protection Fault is? - This causes the system to halt, and on windows is one of several ways to 'bluescreen' a PC.
But do you actually know what it means? - It means a piece of code tried to write to a memory location that isn't part of it's own process...
What you're describing sounds highly dubious and improbable... You don't just arbitrarily rewrite the memory of a program to do cheap tricks in a game.
That violates so many basic process security features it's very hard to believe stuff like that is around.
(There are exceptions of course, the fact that emulators can modify the RAM content of an emulated game is no surprise because the RAM in question is part of an emulated system which was created by the same process as the emulation software. In that case, all of the RAM, cpu registers and so on are part of the address space of the emulator itself, so it can do whatever it likes to them.)
Anyway, I'm having a very hard time believing the existence of stuff that does what you're claiming. Sure it isn't completely impossible, but it's an absurdly convoluted thing to be doing just to mess around with a game a little bit.
Save file editing is absolutely trivial by comparison. Anyone that can program to a modest standard should be able to create a reasonably functional save game editor - (if they can figure out the file format).
Only a handful of people with obscure technical knowledge could create anything that actively modifies the RAM of a game as it's running, and actually get it to work (rather than just crashing computers, triggering severe system security warnings, or other random things...)