Quote:
Originally Posted by scriptless
That is what I ment. Foogles showed me this a few years back. It seems to work for a very long time, so long that I was unaware it was even patched. And I assume the .code files are the .code files I see on my computer? Wonder how long it takes for someone to break the encryption :o Graal v2-5 have already had there packet encryption broken (several times). 
Thanks for informing me on the client vars. so player.attr[] vars would be the best way? I was just wondering cuz if a noob opened a memory editing tool and changed there attr, would this effect show for all other players? seems unfair if 1 player changes his size to 20+ and just stomps you to peices. |
I doubt the encryption is the only form of security backing them up. It probably checks modification time as well.
As for player.attr[]'s, even if a hacker were to change the attr of another player it'd all be clientside. That means the only person who would see the change is the player doing the hacking. Also, there's a reason my system is not dependent on zoom. I use a separate, more secure(ideally, though I mainly leave that up to whomever uses it to implement) variables and zoom is only a visual representation. In fact, the zoom was the last thing I added.