![]() |
Better security
Is there anyway to improve Graal's security? This is mainly to stop the hacking. Player's have found yet another way to edit there strings/flags.
|
Sorry :{
|
Quote:
I've also noticed this on N-Pulse, mainly in the Spar Center. Players have been enabling their weapons somehow, and when his/her attributes are viewed, their weapons are displayed as disabled. Quote:
|
Quote:
At least that's what we've noticed on Era. |
Quote:
|
Quote:
I sure wish they would fix this 'glitch' then. Personally i reported it numerous times, but nothing is being down, not yet atleast. It's quite annoying waiting to spar, and you have a bunch of fools trying to act funny by hitting you in a nopkzone/weaponsdisabled area. Except for you of course, since you live in NYC, and i love NYC. ^^ |
There's always the Original Classic method. Have everyone else in the level watch if anyone else in the level is doing something...
|
Quote:
|
That applies for UN only i guess then.
|
I guess you goto bed early.
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Weird enough, it's not the client.flags that they're editing.
Into more details, it's CLIENTR. |
Quote:
I know on Unholy Nation, with their Event Points, they have a database that matches the current amount of Event Points then it changes when events are won and if it's changed, it detects it with RemoteControl. Then again, I guess with the new scripting engine, it would be less of a hassle to have each account have its own folder to compare stuff within? |
Snandy, try hack Graal yourself. It sounds pretty weird, but that way you find the flaws and can prevent it yourself or get someone to do this for you.
|
We shouldn't need to worry about this though, the graal client should some-what prevent it.
|
Quote:
|
Quote:
Quote:
|
Quote:
|
Quote:
I mean, Damix helped me with Kingdoms and the graphics replacement. |
If someone knows hacking working methods then report them via forum pm.
The script variables are usually quite secure on clientside, but you should never rely on them. It can never be prevented that something is sent/received incorrectly or some bugged script is setting a variable to a wrong value, so do only things on the server which cannot go wrong even if there is bad input from the clientside. (Bad input means: client. vars being edited, invalid triggers being sent) |
| All times are GMT +2. The time now is 03:46 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
Copyright (C) 1998-2019 Toonslab All Rights Reserved.