Quote:
Originally Posted by Jakov_the_Jakovasaur
no such function exists
it would also be highly prone to abusive developers causing annoyance, plus changes would be applied globally to every server a player logs on to
|
There's tons of abusive **** developers might do! GraalControl is destroyable! The $pref for allowmasses can be forced on! Save-to-file functions allow staff to see all accounts on a single PC, as well as getFileModTime - used in its place to find out the last mod time of Graal6.exe.
And don't even get me started on PMs! They're obviously readable/loggable, but you could also make a system for "PM spoofing" -- where I could PM someone and make it look like YOU PMed them, using the default system entirely (basically just using your client as a proxy via new pmctrl/showpm()/plaintext retrieval/paste into pmeditctrl/sendpm() - all invisibly).
You can retrieve players histories with each other and upload it to the server (new pmhistoryctrl/plaintext retrieval/trigger the plaintext to server) so you can spy on people's conversations. You can do the same (but to a smaller degree) to retrieve player's email addresses, if they sign in with an email.
Not to mention that I know some
serious graal security holes that I won't even mention in this thread because nobody else should be aware of them.
I could see why mousex/mousey stopped being writeable -- outside of making a first-person-shooter on graal I can't even fathom a reason for why they should be writeable, and they were highly prone to abuse to any old novice coder otherwise (lol lol mousescreenx = int(random...).
But not being able to write or EVEN READ the default keybinds? That's just bad form!