Hide region flags that users don't have access to
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java
- Domain
- authorization, cli
Research direction
Start at the /rg flags command and trace how its flag and option list is assembled. Resolve whether the hidden-permission approach or filtering by region-flag permissions is intended; done means users see only flags and values they can change, while permitted entries remain available.
Written by the indexing model from the issue text.
Description
The Problem
The region flags pages are quite extensive, and especially with custom flags or other plugins adding flags, users can get lost in the sauce trying to find a flag they can set in the sea of total flags.
A Solution
I have a few solutions to this problem; one would be to add a hide permission node such as worldguard.region.flag.hidden. to remove the flag from the /rg flags list if they have the hidden permission. Alternatively, and the more clean option, if a user has any of the following:
worldguard.region.flag.flags.<flag name>.<flag value>.own.<region name>
worldguard.region.flag.flags.<flag name>.<flag value>.member.<region name>
worldguard.region.flag.flags.<flag name>.<flag value>.<region name>
Then the user should see that flag and its options in /rg flags, else they can't see the flag in the list.
This would clean up the list significantly and help reduce clutter for the user, making it easier for players to access the flags that they actually have access to change.
Alternatives
No response
Anything Else?
No response
- Dominant language
- Java
- Stars
- 938
- Forks
- 674
- Avg merge
- 22h 57m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from EngineHub/WorldGuard
-
status:pending type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EngineHub/WorldGuard#2305 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
EngineHub/WorldGuard#2311 · 1 comment ·
-
status:pending type:bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
EngineHub/WorldGuard#2302 · 4 comments ·
-
status:pending type:feature-request
Difficulty 4/5 3-5 days Newbie friendliness 45/100
EngineHub/WorldGuard#2301 · 5 comments ·
-
status:pending type:feature-request
Difficulty 5/5 Over a week Newbie friendliness 25/100
EngineHub/WorldGuard#2288 · 1 comment ·
All issues in EngineHub/WorldGuard
Similar issues
-
type: possible bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
grimmory-tools/grimmory#2850 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aoqia194/leaf-loader#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/streampark#4521 ·