-ffs-PLASMA

> @xPREDATORx or @ffsPLASMA, can you confirm whether or not [0e2b203](https://github.com/multitheftauto/mtasa-blue/commit/0e2b203aa1d12f15931eb7d9522a5edf987f45ff) fixed this issue? It was a test fix after all. -ffs-Drake — heute um 11:29 Uhr we tested it...

I confirm crashing for me as well with same offset when starting to use timed-objects on new IDs.

You would have to blacklist certain commands like login/register as you could simply build a keylogger for them.

Yeah... In a more secure world, client should not be able to use functions like setElementHealth, setElementPositon, blowVehicle on elements if he aint the explicit syncer of said element. But...

> > Yeah... In a more secure world, client should not be able to use functions like setElementHealth, setElementPositon, blowVehicle on elements if he aint the explicit syncer of said...

Since this discussion came up again recently in discord, the situation remained same if not got worse for server. The fundamental issue here is server trusts the client too much...