Consider off-thread Chunkloading before Teleport

[BlayTheNinth]

A somewhat frequent report with Waystones is that servers are experiencing lagspikes or clients are falling through the ground on teleports.

Since nowadays chunk loading does support CompletableFuture to some extent, it might be time to look into whether the teleport's chunk load could be initiated off the main thread.

Some things to watch out for:

• what if player moves away
• what if the waystone is broken
• what if player drops the stone or scroll
• what if player uses the stone or scroll again
• what if player dies
• what if leashed entities or pets change

[MapleSugar365]

A somewhat frequent report with Waystones is that servers are experiencing lagspikes or clients are falling through the ground on teleports.

Since nowadays chunk loading does support CompletableFuture to some extent, it might be time to look into whether the teleport's chunk load could be initiated off the main thread.

Some things to watch out for:

• what if player moves away
• what if the waystone is broken
• what if player drops the stone or scroll
• what if player uses the stone or scroll again
• what if player dies
• what if leashed entities or pets change

This is a very important feature. I have some ideas that I hope can inspire you:
Is it possible to use a full-screen overlay animation immediately after the player performs a teleport? During this time, the player cannot perform any other actions. Wait for the asynchronous chunk loading to complete, then teleport the player to the destination, and finally remove the full-screen overlay animation.

The above idea should solve most problems. The only remaining issue is, "What if the player dies during the asynchronous chunk loading period?" I think we can add an additional condition check: after the asynchronous loading is complete and before teleporting the player, check if the player is still alive. If the player has died during this time, then cancel the final teleport step.