You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BetterRTP won't stop finding location in some circumstances, including superflat (Y of blocks always under -60 but default minY=0 in config.yml#L83) or void (no blocks in new chunks) world.
How To Reproduce:
Start a new Paper server instance with only latest BetterRTP plugin. Set world type to minecraft:flat. Change MaxRadius to 3000000 and leave other configuration default. Wait until no more disk space available.
Expected Behavior:
If BetterRTP fails to pick teleport location from a world for a number of times, it may automatically disable RTP in that world.
Screenshots/Error Log:
Umm... There might not be any useful logs, but here are the chunk files list.
And here is a screenshot of MCA Selector, which shows that the coordinate of generated chunks are random.
Additional Context:
The behaviour is already reported in #127 but it's closed without any explanation. It seems that more than one user have the same behaviour.
The text was updated successfully, but these errors were encountered:
Plugin Version:
3.6.12
Describe The Bug:
BetterRTP won't stop finding location in some circumstances, including superflat (Y of blocks always under -60 but default minY=0 in config.yml#L83) or void (no blocks in new chunks) world.
How To Reproduce:
Start a new Paper server instance with only latest BetterRTP plugin. Set world type to minecraft:flat. Change MaxRadius to 3000000 and leave other configuration default. Wait until no more disk space available.
Expected Behavior:
If BetterRTP fails to pick teleport location from a world for a number of times, it may automatically disable RTP in that world.
Screenshots/Error Log:
Umm... There might not be any useful logs, but here are the chunk files list.
And here is a screenshot of MCA Selector, which shows that the coordinate of generated chunks are random.
Additional Context:
The behaviour is already reported in #127 but it's closed without any explanation. It seems that more than one user have the same behaviour.
The text was updated successfully, but these errors were encountered: