I had it running on the server. I had assumed it was the server because you are looping through all the players and updating the score for each which I didn’t figure you’d have every client doing.
its at 1.24 billion when it stops updating. Did you go to that position? (1, -2.478e9,1)
My server stopped updating when it hit 2147483648. It does have an impact if you try to move your character first also. If you move your character to start at -100000000 it seemed to actually set the Y position to -1000000 and started dropping from there but had already set the score to 100M.
You could probably also run something on the client that would update the characters position on the server every so often but be aware that this could easily be utilized to send fake positions.
I figured that out already. I wanna find a way to do it without a compromise in security (e.g exploiting)
I’ll mark this as a solution even though it has a vulnerability. Anyone else that can reply and suggest how else to fix the vulnerability will be given it
You could save the velocity of the player each heartbeat and once the position stops updating, use it to calculate the new position.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.