You must be inside the region to change blocks for the first time.

Server Implementation

Spigot

Server Version

1.21

Describe the bug

I'm using worldguard to create regions. After creating a region, in order to change the blocks inside, you need to go inside the region for the first time and make a change (for example //set 1), then you can exit the region, subsequent changes will be made regardless of your location. Players get confused and write bug reports, thinking that something is wrong, because they have already created the region. However, even if you close your eyes to this, there is a second point.

Second point: information that there is no region allowed is displayed to players only if their selection is located in the same chunk. If it goes beyond the chunk boundary, then the error message is written to the console, not to the player.

To Reproduce

1. Selecting a region
2. Create a region using /rg claim
3. After the command //set 1, if the player is not inside the region, he will receive an error that the required region does not exist. And if the selection also contains several chunks, even this error will not be displayed to it.

The player simply has nothing going on and he doesn’t know why

Expected behaviour

Either you need to be able to change blocks without being inside the region, or have a separate message for a more convenient user experience - so that the player understands that he needs to enter the region

Screenshots / Videos

https://youtu.be/7r6mhS_0ung

Error log (if applicable)

No response

Fawe Debugpaste

https://athion.net/ISPaster/paste/view/def7702b7c3f4955a332c6e129ed9a39

Fawe Version

FastAsyncWorldEdit version 2.11.1-SNAPSHOT-861;6fb0102

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?

No response

Reproduce the behavior on Spigot 1.21 with FAWE 2.11.1-SNAPSHOT using /rg claim followed by //set 1, both inside and outside the region and across chunk boundaries. Trace the region-check and player error-reporting paths; done means changes are handled as intended outside the region and affected players receive a clear message instead of only console output.