PaperMC / PaperMC/Paper

Bypass permission nodes for vanilla features.

Open
#12,656 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: needs triage
Dominant language
Java
Stars
12.7k
Forks
3.5k
Avg merge
3d 13h
Merged PRs (30d)
11

Description

Is your feature request related to a problem?

There are a number of vanilla features which do not have a bypass permission node. This includes, but is not limited to: spawn protection, the "force-gamemode" setting, and the "allow-flight" setting.

The lack of permission nodes for these features makes it more difficult to control who is and isn't affected by them. This can be especially problematic for certain configurations. For example, if a server uses "force-gamemode", there is no way to prevent certain users from being affected by it.

Describe the solution you'd like.

Adding permission nodes for these features would be very helpful.

A permission node for bypassing spawn protection would allow server owners to give staff members the ability to be exempt from it. The lack of a permission node for spawn protection has been an issue since Bukkit; I even found a forum post about it from back in 2014: https://bukkit.org/threads/permission-to-ignore-spawn-protection.312432/

A permission node for bypassing "force-gamemode" would allow for more control when running a server with the "force-gamemode" setting. Sponge already has this feature, as well as bypass permission nodes for the player limit and whitelist: https://docs.spongepowered.org/stable/en/server/spongineer/commands.html

A permission node for bypassing the "allow-flight" setting would be nice too. This way, servers can control who is exempt from this anti-cheating measure. Paper already has a permission node for bypassing its anti-xray functionality, which is an anti-cheating measure as well: https://docs.papermc.io/paper/reference/permissions/

Describe alternatives you've considered.

I have asked forks of Paper about this issue, but never received a response.

Other

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

The issue names no files, tests, or entry points. Start by locating the implementations for spawn protection, force-gamemode, and allow-flight, then inspect how permissions are checked for related features. Done means the requested bypass permissions are defined and consistently applied for each listed vanilla feature, with coverage for their intended behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.