[1.12.2] [BUG] Failed /top over void causes server timeout crash
TheodoreHua opened this issue ยท 3 comments
WARNING: Do not delete any of the sections below. Improperly filled out issues will be closed if not rectified in a timely manner!
Initial Steps
- I have updated to the latest build from Jenkins before reporting a bug
- I have checked, if the bug was not already reported by using the search.
- Attached is my ForgeEssentials/modlist.txt, my latest.log, and my debug.log (attached is modlist, although latest.log and debug.log are useless as it just shows the server crashing from a timeout, no relavent information).
- Also, attached are the client logs (if applicable) N/A
Describe the bug
Failing (meaning there's nothing above the player to teleport to) a /top with nothing underneath (the void) causes the server to time out and crash.
Normally a failed on /top happens, FE teleports the player to the ground, it's likely that the timeout is happening because FE continuously searches for the ground when there's nothing to find (just the void).
To Reproduce
Steps to reproduce the behavior:
- Go to the end or make a hole to the void
- Make sure there is nothing above you
- Make sure the only thing below you is the void
- Jump off into the void and then attempt to use
/top
with nothing but the void below you and nothing above you - The server will time out
Expected behavior
/top to not work or something else happens rather than the server crashing
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: Windows 10
- Browser Firefox
- Initially Found On: 12.3.82 then double checked on (latest at time of writing): 12.3.110
Additional context
N/A
Fixed in 738d25d
This is being caused by the code counting down until it finds a solid block.
A fix will be added in a future build.