Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
2 tasks done
PrOsToNiK13 opened this issue Jul 28, 2024 · 1 comment
Open
2 tasks done
Labels
Requires Testing This is a new issue which needs to be approved before labeled with "bug"

Comments

@PrOsToNiK13
Copy link

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

Anything else?

No response

@PrOsToNiK13 PrOsToNiK13 added the Requires Testing This is a new issue which needs to be approved before labeled with "bug" label Jul 28, 2024
@PrOsToNiK13
Copy link
Author

I think the problem is that Fawe completely refuses to acknowledge worldGuard's priorities. If you make 3 regions inside each other, set different priorities and play with the commands to add and remove yourself from the region, the behavior will always be different. You will be able to both change blocks in the region in which you are the owner, and at some other time you will not be able to change the region in which you are the owner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Requires Testing This is a new issue which needs to be approved before labeled with "bug"
Projects
None yet
Development

No branches or pull requests

1 participant