IntellectualSites / IntellectualSites/FastAsyncWorldEdit
FAWE ignores worldguard region restriction
Nobody has claimed this yet.
- 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
- Enable region-restriction in config
- Add fawe.worldguard.members to a non admin player
- create a region with worldguard
- let player use //tree in region he is not added.
- 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
- 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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