[stabker]

Cheaters can send invalid "surfing offsets", causing invisibility and "Loading..." bug for players in spectator mode.

Currently it can be fixed only by using memory-hacking plugins. Would be great if you add fix by default or function like GetPlayerSurfingOffsets.

Sorry for my bad English.

[povargek]

Up, this need fix

[Sew_Sumi]

https://sampwiki.blast.hk/wiki/GetPlayerSurfingObjectID

https://sampwiki.blast.hk/wiki/GetPlayerSurfingVehicleID

Is this not scriptable?

In accompanying the Object sizes, and the vehicles sizes, you'd be able to check how far they are actually from the object/vehicle, and then remove them from the game, so they don't cause it.

I'd guess this is much the same as the bullet issue where they were sending bullet vectors that were so far out, they were stupidly insane.

[povargek]

Quote:

Originally Posted by Sew_Sumi https://sampwiki.blast.hk/wiki/GetPlayerSurfingObjectID https://sampwiki.blast.hk/wiki/GetPlayerSurfingVehicleID Is this not scriptable? In accompanying the Object sizes, and the vehicles sizes, you'd be able to check how far they are actually from the object/vehicle, and then remove them from the game, so they don't cause it. I'd guess this is much the same as the bullet issue where they were sending bullet vectors that were so far out, they were stupidly insane.

No, hacker send a nearest vehicle id to "GetPlayerSurfingVehicleID", in surf offsets float "NaN", SA-MP not scriptable get a "surf offsets".
GetPlayerPos - return a NORMAL pos (example, on car roof)

[Spmn]

IIRC, YSF rejects invalid surf data, but I might be wrong.

[Romz]

Indeed, this problem needs to be corrected.