Prevent mem hacking before dumping character from memory

[Link88]

Hi,

I know that it's possible to force the client to simulate to have an item (or any other stuff I guess, like reputations or mounts maybe...) by changing the entry in memory of an item that you really own with another that you would like to export.

Doing so, if the user exports the whole character data from memory (with a specific handmade program and following the Info Dump Thread List that you posted) for importing into another server, the data would be hacked since there will be items that the character doesn't really own.

How can we check and prevent this type of hack?
edit: Is it possible to programmatically "reset" the memory to remove any hacked value and restore all the real values?

I also know that it's possible to turn off the hacking program by killing the process from task manager (I have read it into some forum) without making the client crash (so the hacked memory keeps the data). At this point the solution that should come out would be very soffisticated imho.

Thanks in advance, any idea is appreciated.

[namreeb]

If you accept data from a user, there is always the chance that the user modified that data. The only way to be sure would be to take the user out of it by connecting to the realm where that player is located yourself to produce the dump.

[Link88]

If you accept data from a user, there is always the chance that the user modified that data. The only way to be sure would be to take the user out of it by connecting to the realm where that player is located yourself to produce the dump.

Yes that would be the perfect way to prevent hacked data but unfortunately when you have a lot of porting request from different users it is very hard and wasteful to handle.

Any programmatic way like some kind of flag to check that the user changes upon a memory hack? If you think that there is no way just tell me please.

Thank you

[Jadd]

Yes that would be the perfect way to prevent hacked data but unfortunately when you have a lot of porting request from different users it is very hard and wasteful to handle.

Any programmatic way like some kind of flag to check that the user changes upon a memory hack? If you think that there is no way just tell me please.

Thank you

There's no way.

[Link88]

Sad to read but thank you for the quick answer.