-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Inefficient dragon respawn #10323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
AfonsoMendoncaJacinto
added a commit
to AfonsoMendoncaJacinto/Paper
that referenced
this issue
Mar 27, 2025
This issue likely arose from the method findExitPortal(), which has been optimized. This optimization will ensure better server performance during the respawn sequence and smoother gameplay. Signed-off-by: Afonso Jacinto <[email protected]>
Good afternoon (at least where I live). I believe this patch fixes this issue smoothly, without affecting gameplay negatively, on the contrary. Me and my colleague have tested this thoroughly and found no game-breaking behaviour. Please let me know, in case there is anything out of the ordinary. |
AfonsoMendoncaJacinto
added a commit
to AfonsoMendoncaJacinto/Paper
that referenced
this issue
Mar 28, 2025
This issue likely arose from the method findExitPortal(), which has been optimized. This optimization will ensure better server performance during the respawn sequence and smoother gameplay. Signed-off-by: Afonso Jacinto <[email protected]>
AfonsoMendoncaJacinto
added a commit
to AfonsoMendoncaJacinto/Paper
that referenced
this issue
Mar 28, 2025
This issue likely arose from the method findExitPortal(), which has been optimized. This optimization will ensure better server performance during the respawn sequence and smoother gameplay. Signed-off-by: Afonso Jacinto <[email protected]>
AfonsoMendoncaJacinto
added a commit
to AfonsoMendoncaJacinto/Paper
that referenced
this issue
Mar 28, 2025
This issue likely arose from the method findExitPortal(), which has been optimized. This optimization will ensure better server performance during the respawn sequence and smoother gameplay. Signed-off-by: Afonso Jacinto <[email protected]>
AfonsoMendoncaJacinto
added a commit
to AfonsoMendoncaJacinto/Paper
that referenced
this issue
Mar 28, 2025
This issue likely arose from the method findExitPortal(), which has been optimized. This optimization will ensure better server performance during the respawn sequence and smoother gameplay. Signed-off-by: Afonso Jacinto <[email protected]>
AfonsoMendoncaJacinto
added a commit
to AfonsoMendoncaJacinto/Paper
that referenced
this issue
May 1, 2025
This issue likely arose from the method findExitPortal(), which has been optimized. This optimization will ensure better server performance during the respawn sequence and smoother gameplay. Signed-off-by: Afonso Jacinto <[email protected]>
AfonsoMendoncaJacinto
added a commit
to AfonsoMendoncaJacinto/Paper
that referenced
this issue
May 2, 2025
This issue likely arose from the method findExitPortal(), which has been optimized. This optimization will ensure better server performance during the respawn sequence and smoother gameplay. Signed-off-by: Afonso Jacinto <[email protected]>
AfonsoMendoncaJacinto
added a commit
to AfonsoMendoncaJacinto/Paper
that referenced
this issue
May 2, 2025
This issue likely arose from the method findExitPortal(), which has been optimized. This optimization will ensure better server performance during the respawn sequence and smoother gameplay. Signed-off-by: Afonso Jacinto <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Timings or Profile link
https://spark.lucko.me/yEwDSXG6Yk
Description of issue
After placing the fourth end crystal when respawning the ender dragon on the latest version of paper with only spark installed, a lag spike happens from the method
net.minecraft.world.level.dimension.end.EnderDragonBattle.findExitPortal()
. The timing link has a threshold of 100ms per tick, so it only captured the tick where the spike occurred.Plugin and Datapack List
Server config files
Paper version
Other
After testing, the lag spike is caused by the server checking for the end portal formation from the highest placed block at 0,0 to the bottom of the world in a single tick, which takes longer than 100ms (usually anywhere from 800-2500). I think major refactoring might have to be done to fix this, although just making the search algorithm more efficient could also be an easier fix.
The text was updated successfully, but these errors were encountered: