[1.16.5] Server hard lock when clicking on a Dungeon Checkpoint
ProsperCraft opened this issue · 4 comments
Describe the bug
When you click on a Dungeon Checkpoint, the server locks up hard for 15 seconds to 10 minutes.
To Reproduce
Steps to reproduce the behavior:
Click on a Dungeon Checkpoint, the third and fourth time.
Screenshots
Warmroast-
Warmroast 2
Additional context
Add any other context about the problem here.
Logs
Debug log-
https://gist.github.com/ProsperCraft/e21da9da4d2c836b3dbe47d447205f4d
this was fixed by https://www.curseforge.com/minecraft/mc-mods/futurepack/files/3420273
sorry for the long wait.
This was in the console when it hard locked but then recovered.-
`·
[11:44:28] [Server thread/DEBUG] [futurepack/]: Create EScanner massage with {"extra":[{"extra":[{"bold":true,"color":"dark_gray","text":"Floor:1 Mantes shi│···············································································
vering Cave L:0"}],"text":"You are at: "},{"text":"Teleport to: "},{"underlined":true,"color":"dark_blue","clickEvent":{"action":"change_page","value":"dung│···············································································
eon_teleport=ffffa73ffe67a080"},"text":"Floor:0 Wugis polar Virtuality L:0"},{"underlined":true,"color":"dark_blue","clickEvent":{"action":"change_page","va│···············································································
lue":"dungeon_teleport=ffffb3bffe667094"},"text":"Floor:1 Wugis polar Virtuality L:0"}],"text":""} │···············································································
[11:44:28] [Server thread/DEBUG] [futurepack/]: Resived Research request from TextComponent{text='Dreminon', siblings=[], style=Style{ color=null, bold=null│···············································································
, italic=null, underlined=null, strikethrough=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null, font=minecraft:default}} │···············································································
[11:44:28] [Server thread/DEBUG] [futurepack/]: Resived Research request from TextComponent{text='Dreminon', siblings=[], style=Style{ color=null, bold=null│···············································································
, italic=null, underlined=null, strikethrough=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null, font=minecraft:default}} │···············································································[11:44:28] [Server thread/DEBUG] [futurepack/]: Resived Research request from TextComponent{text='Dreminon', siblings=[], style=Style{ color=null, bold=null│···············································································
, italic=null, underlined=null, strikethrough=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null, font=minecraft:default}} │···············································································[11:44:28] [Server thread/DEBUG] [futurepack/]: Resived Research request from TextComponent{text='Dreminon', siblings=[], style=Style{ color=null, bold=null│···············································································
, italic=null, underlined=null, strikethrough=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null, font=minecraft:default}} `
There is something realy weird going on becuase, I never experienced that issue and also that method is called async and only chcks 1 chunk before sleeping again, so there literaly is no way for me to further scale it down. I wonder why the "chunkExist" check takes so long, it absolutly should not, its a simple yes no.