Server Implementation

Paper

Server Version

1.18.2

Describe the bug

Using world edit in a world that is not any of the three main worlds (overworld, nether, end) will cause the plugin to break upon leaving and rejoining.
For example, I teleport to a custom world on the server and set some blocks in any way using FAWE. I then leave the server and rejoin. If I then try to use any FAWE command, nothing will happen and the player will not be able to interact with blocks until rejoining again.
Players cannot use any FAWE command, however, the console can.

A temporary fix I found is deleting the history and clipboard folders and then restarting the server. You would have to repeat this process every time you use world edit and leave the server again.

To Reproduce

1. Teleport to a custom world.
2. //wand.
3. Select a region and //set stone.
4. Leave the server.
5. Join the server.
6. Use any FAWE command, like //wand.

Expected behaviour

World edit persists to work across leaving and joining the server despite having history and/or clipboard files saved from a custom world.

Screenshots / Videos

No response

Error log (if applicable)

No response

Fawe Debugpaste

https://athion.net/ISPaster/paste/view/83d37d9ebf5c4949af86eb3ec95898cd

Fawe Version

FastAsyncWorldEdit-Bukkit-2.1.3-SNAPSHOT-168

Checklist

• I have included a Fawe debugpaste.
• I am using the newest build from https://ci.athion.net/job/FastAsyncWorldEdit/ and the issue still persists.

Anything else?

What is a "custom" world. Is that one using a datapack, or simply any world not the default defined in server.properties?

Are there really no errors in chat or in the console?

Is this definitely replicable on the latest version? A fix for #1671 and #504 was implemented in the latest commit.

Your paper version is over a month old. Please also update paper.

Finally, the output of fawe threads would be useful when this occurs

Use /fawe threads from the console. Then please provide a full console log, including the commands used

What is a "custom" world. Is that one using a datapack, or simply any world not the default defined in server.properties?

Are there really no errors in chat or in the console?

Is this definitely replicable on the latest version? A fix for #1671 and #504 was implemented in the latest commit.

Your paper version is over a month old. Please also update paper.

Finally, the output of fawe threads would be useful when this occurs

A "custom" world in this case, is any world that is not the default. There are no errors or warning in chat or in the console.
I have updated paper and the issue still persists and I can confirm I am using the latest version of FAWE.
I'm not sure how to get the output of fawe threads.

Use /fawe threads

Edited to make it readable -dordsor21

https://mclo.gs/fwJITT9

Use /fawe threads from the console. Then please provide a full console log, including the commands used

I also used /fawe debugpaste from the console. I found out, only players cannot use FAWE commands when the bug occurs. I didn't think to try to use the console.
Here is the new link to it: https://athion.net/ISPaster/paste/view/83d37d9ebf5c4949af86eb3ec95898cd

There is no evidence of hanging threads. I am unable to replicate using exactly the same settings as you. The message "(world) has been unloaded from memory" does not seem to be sent by spigot or paper, and given it is completed before the player actually disconnects I am lead to believe this may be a functionality of "Core". What integration does the plugin have with FAWE, given its dependence upon it? And is it manually unloaded the world upon play disconnect/something similar?

There is no evidence of hanging threads. I am unable to replicate using exactly the same settings as you. The message "(world) has been unloaded from memory" does not seem to be sent by spigot or paper, and given it is completed before the player actually disconnects I am lead to believe this may be a functionality of "Core". What integration does the plugin have with FAWE, given its dependence upon it? And is it manually unloaded the world upon play disconnect/something similar?

Core uses FAWE to generate mines. When using /warp realm, it will load the player's world and when that player leaves that world, it gets unloaded. Upon quitting the server, the player will get teleported to the server spawn, therefor unloading their world (if they left while on their world). The "(world) has been loaded/unloaded" messages are there so I can debug.