IntellectualSites / IntellectualSites/FastAsyncWorldEdit

FAWE ignores worldguard region restriction

Open
#3,267 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Requires Testing
Dominant language
Java
Stars
806
Forks
394
Avg merge
22h 19m
Merged PRs (30d)
14

Description

Server Implementation

Paper

Server Version

1.21.5

Describe the bug

Hi! I'm running a Paper 1.21 server with FAWE, WorldGuard, and LuckPerms. I want players to only be able to use FAWE (e.g. //set, //tree, etc.) inside regions they are a member or owner of.
region-restrictions: true
My players have the permissions fawe.worldguard.member and worledit.tool.tree. They can still use //tree in every region without being member oder owner.

Am I missing something?

I would ask on discord but all invite links does not work anymore :(

To Reproduce
  1. Enable region-restriction in config
  2. Add fawe.worldguard.members to a non admin player
  3. create a region with worldguard
  4. let player use //tree in region he is not added.
  5. tree appears
Expected behaviour

User get a message that he can't use this command in regions he is not a member of.

Screenshots / Videos

No response

Error log (if applicable)

No response

Fawe Debugpaste

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

Fawe Version

FastAsyncWorldEdit-1107

Checklist
Anything else?

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with Paper 1.21.5, FAWE, WorldGuard, and LuckPerms: enable region-restrictions, grant the listed permissions, and run //tree outside the player's region. Compare the observed behavior with the expected denial message; use the linked FAWE debugpaste for additional context.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
authorization
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.