FAWE unable to select WorldGuard regions above Y:320 or below Y:-64.
Cookie-Kurokami opened this issue ยท 0 comments
Server Implementation
Paper
Server Version
1.19.2
Describe the bug
When using a datapack that allows for increased build height, FAWE is perfectly capable of interacting with blocks and even allows the creation of WorldGuard regions that exist beyond the vanilla borders, but cannot properly select them when prompted. When attempting to select a WorldGuard region above Y:320 for example, the plugin will instead select the vanilla height limit at the same X and Z coordinates. This would not come as much of a surprise to me if not for the fact that WorldEdit is able to do this just fine.
To Reproduce
- Install WorldGuard, FAWE, and a region visualizer of your choice to help with the test.
- Use a plugin or datapack that allows for increased build height.
- Select a region above the vanilla height limit and save it as a WorldGuard region.
- Unselect the region and then attempt to select it again through WorldGuard.
- You cannot.
- Switch out FAWE for WorldEdit.
- Repeat steps 3 and 4 to see the difference.
Expected behaviour
I expected the WorldGuard region I'd created above the vanilla height limit to be selectable while using FAWE, but it is not. It is selectable, however, when using WorldEdit.
Screenshots / Videos
This is me attempting to select my WorldGuard region at Y:1024 with FAWE: https://streamable.com/xpffmg
This is me doing it again, but with WorldEdit: https://streamable.com/0iqv4b
Error log (if applicable)
No response
Fawe Debugpaste
https://athion.net/ISPaster/paste/view/4bde1412bb774c4cb075375099c4b780
Fawe Version
FastAsyncWorldEdit-293
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?
While I do not know for certain, I should mention that I believe this difference between FAWE and WorldEdit may be caused by a single setting that exists within WorldEdit's configuration file, but not FAWE's.
Simply pasting the option into FAWE's worldedit-config.yml understandably does nothing whatsoever.