Danger ability to remove all owners

Open
#2,320 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
54/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
backend

Research direction

Start by locating the clickable /rg info menu and the permission checks for its [Rem] and [Clr] actions. Decide whether clearing all owners should require confirmation or have a separate permission, then inspect the related tests and add coverage for the chosen behavior. Done means players cannot accidentally leave a region without owners, while permitted removal still works.

Written by the indexing model from the issue text.

Description

status:pending type:feature-request
The Problem

any player can remove all owners in clickable menu (/rg info) without any confirmation, after region exists without any owner... player lost control of his rg and contact to admins for return control

Any player can lost control rg by missclick - buttons [Rem] [Clr] are to close together for missclicking

As admin I cant block [Clr] button, because [Rem] и [Clr] button have shared permission nodes

A Solution

Add confirmation for dangerous action [Clr]
OR
Separate permission nodes and admin can disable [Clr] action when [Rem] stay active

Alternatives

No response

Anything Else?

No response

Dominant language
Java
Stars
944
Forks
686
Avg merge
4d 7h
Merged PRs (30d)
6

Getting set up

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.

More from EngineHub/WorldGuard

All issues in EngineHub/WorldGuard

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.