EngineHub / EngineHub/WorldGuard

Setting notify-enter to false blocks entry to region

Open
#2,231 0 comments 1 reaction 0 assignees View on GitHub
status:pending type:bug
Dominant language
Java
Stars
938
Forks
671
PR merge metrics
No merged PRs in 30d

Description

### WorldEdit Version

7.3.17-snapshot

### WorldGuard Version

7.0.15-snapshot

### Platform Version

Paper version 1.21.8-58-main@9aaaadf

### Confirmations

- [x] I am using the most recent Minecraft release.
- [x] I am using a version of WorldEdit compatible with my Minecraft version.
- [x] I am using a version of WorldGuard compatible with my Minecraft version.
- [x] I am using the latest or recommended version of my platform software.
- [x] I am NOT using a hybrid server, e.g. a server that combines Bukkit and Forge. Examples include Arclight, Mohist, and Cardboard.
- [x] I am NOT using a fork of WorldEdit, such as FastAsyncWorldEdit (FAWE) or AsyncWorldEdit (AWE)

### Bug Description

With commit #f8415ed regions on our server cannot be entered, when there's "notify-enter: false" in the region file. (We had one region where notify-enter was enabled years ago and disabled later, a pretty rare case). This also happens to op'ed players.
Setting "notify-enter: true" or removing the "notify-enter: false" entry from the region file completely makes it accessable again.

### Expected Behavior

the config entry "notify-enter: false" for a region does not affect entry to the region.

### Reproduction Steps

1. /rg flag freefarm notify-enter true
2. /rg flag freefarm notify-enter false
3. (trying to enter the region bounces the player back)
4. /rg flag freefarm notify-enter true
5. (region is can be entered again)

### Optional WorldGuard-Report

_No response_

### Anything Else?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.