Quote:
Originally Posted by Mark Sir Link
doing something like if(clientr.class == null) {clientr.class = class;} would be sufficient to make sure they couldn't force that trigger to allow for class changing.
with how things are currently going, anything that is sensitive needs to be stored into a clientr or other sort of server side storage, with additional verifications used to insure the triggerserver is coming from where you expect or not interfering with existing data
|
See where you are coming from. I don't know why the Graal Online team can't add a better anti-hack mechanism to Graal. The current one is ridiculous and isn't worth being called a defense mechanism. We have to script it ourselves.