FastAsyncWorldEdit

FastAsyncWorldEdit

Bukkit Plugins
152k Downloads

Operations not updating blocks on chunk Worldguard region border

LM-Wolfert opened this issue ยท 2 comments

commented

Server Implementation

Paper

Server Version

1.18.2

Describe the bug

A continuation from #2258 when doing a FAWE operation in a WorldGuard region of which you are the owner/member it will not update blocks when they are in the same chunk as the border of the region. See the attached video if this is not clear.

To Reproduce

  1. Create a polygonal Worldguard region. It must have at least 1 whole chunk in the region.
  2. Add yourself as a member of that region with sufficient permissions to use FAWE commands in it.
  3. Create a cuboid selection that includes at least part of the whole chunk and another part in a chunk that includes a region border.
  4. Run //set stone, it will now only set the stone in the chunk where no border exists. In the chunk with the region border nothing happens. The number of effected blocks in the command output do indicate the correct number of blocks. This happens with any command that would modify the world.

Expected behaviour

The blocks within your WorldGuard region be set to stone.

Screenshots / Videos

https://i.gyazo.com/66aaf94c155cb596c80e59012c259ad1.mp4

Error log (if applicable)

No response

Fawe Debugpaste

https://athion.net/ISPaster/paste/view/35168cc0fe9c4f07959283afe448ed32

Fawe Version

FastAsyncWorldEdit-Bukkit-2.6.2-SNAPSHOT-453.jar

Checklist

Anything else?

No response

commented

FYI this is not an issue in the latest release build (2.6.1).

commented

Unfortunately this has not fixed the issue, in chunks with the border of a Polygonal Worldguard region the blocks still don't get replaced.
@dordsor21

It appears like everything should be working but it's just that the blocks don't get altered. If you do this in a chunk that doesn't include a region border then it's fine. The number of blocks effected by the operation in the command feedback is the correct number, even when doing it over the border of the region. After reverting the server back to 2.6.1 this was fixed.