Colton1070
- Colton1070
- JIRAUSER720240
- Europe/Stockholm
- Yes
- No
REALMS-10315
BDS-17619Hosting a BDS on a Linux machine. After getting players on the server, an issue was reported where players will receive fall damage from heights
,they should not receive fall damage. This would happen especially frequently when sprinting and jumping, when the player is falling an additional block, or even on an even surface. I believe the server is using a flawed method to calculate fall damage where the distance travelled is being incorrectly "added" to the total distance fallen. This could explain why the bug is common when sprinting as you can travel further distances when jumping. This tends to happen more often with additional players on the server as well. It seems like client-auth movement is not working as intended either?For the game stuttering, I have no clue why tick rate/server related performance is dropping client FPS and making the game stutter for players when the worse that should happen with server performance issues is network related lag. Why does it seem like my client is completely dependent on receiving server updates for its own performance?
Hosting a BDS on a Linux machine. After getting players on the server, an issue was reported where players will receive
falldamage from heights they should not receive fall damage. This would happen especially frequently when sprinting and jumping, when the player is falling an additional block, or even on an even surface. I believe the server is using a flawed method to calculate fall damage where the distance travelled is being incorrectly "added" to the total distance fallen. This could explain why the bug is common when sprinting as you can travel further distances when jumping. This tends to happen more often with additional players on the server as well. It seems like client-auth movement is not working as intended either?For the game stuttering, I have no clue why tick rate/server related performance is dropping client FPS and making the game stutter for players when the worse that should happen with server performance issues is network related lag. Why does it seem like my client is completely dependent on receiving server updates for its own performance?
Hosting a BDS on a Linux machine. After getting players on the server, an issue was reported where players will receive damage falling from heights they should not receive fall damage from. This would happen especially frequently when sprinting and jumping, when the player is falling an additional block, or even on an even surface. I believe the server is using a flawed method to calculate fall damage where the distance travelled is being incorrectly "added" to the total distance fallen. This could explain why the bug is common when sprinting as you can travel further distances when jumping. This tends to happen more often with additional players on the server as well. It seems like client-auth movement is not working as intended either?
For the game stuttering, I have no clue why tick rate/server related performance is dropping client FPS and making the game stutter for players when the worse that should happen with server performance issues is network related lag. Why does it seem like my client is completely dependent on receiving server updates for its own performance?
I was able to find a workaround by quickly typing a single letter when the On-screen keyboard popped up, and quickly pressing B (On Xbox). This was after several attempts at creating signs where the text would disappear. After typing "Y", that sign and the future Signs/Name Tags ended up working. It may or may not be reproducible - I will comment further with findings.
Seems like really the only reliable work around is luck and brute force. Just keep spamming signs with a single letter until one of them sticks. You'll have a window of time to place more until you get the privilege taken away XD.
Seems to be resolved on my Realm, however - do not want to celebrate too early as it could just be a side effect of the Realm server being restarted for the in place upgrade to 1.19. It could also still affect other users, regardless it's good to hope that it is resolved after 8 months of waiting.