PaperMC / PaperMC/Paper

Expose CraftServer#ignoreVanillaPermissions to the API

Open
#14,108 0 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?

Using paper-26.1.2-74.jar (currently marked as supported on download page).

Currently to ignoreVanillaPermissions you have to set it manually in commands.yml or via

((CraftServer) Bukkit.getServer()).ignoreVanillaPermissions = true;

I'm managing a mini games network, where on each backend server a single plugin exists, that should take control of this backend server and therefore the minigame. I find it a better solution to configure the server to my liking via plugins than via configuration files. As commands.yml was made optional, i'd favor to set this via plugin.

Describe the solution you'd like.

Expose a setter (and maybe a getter) for CraftServer#ignoreVanillaPermissions.

Something like org.bukkit.Server#setIgnoreVanillaPermissions(boolean) and org.bukkit.Server#getIgnoreVanillaPermissions().

I would say, that changing this via plugin is temporary for the current runtime of the server and is not written back to the config file.

Describe alternatives you've considered.

Currently it can only be change like described above, which needs paperweight to compile and not just the paper-api.

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

Start by reading CraftServer#ignoreVanillaPermissions and the org.bukkit.Server API entry point, then compare how commands.yml currently configures the setting. Add the requested public setter and getter while keeping plugin changes limited to the current runtime, and verify that plugins can use the API without depending on CraftServer internals.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.