PaperMC / PaperMC/Paper

Add missing API code for operator permission levels and bypassesPlayerLimit

Open
#14,177 5 comments 1 reaction 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?

My feature request is related to a problem with the API. You can only set/unset/check operator status; you can't set/check the permission level (0 to 4) or the bypassesPlayerLimit flag.

Describe the solution you'd like.

The best solution would be to add the missing API code. This would allow plugins to set/unset/check an operator's permission level and the bypassesPlayerLimit flag.

Describe alternatives you've considered.

I've already looked into adding built-in commands for managing operators. However, it was determined that expanding the API would be a better approach.

Other

I've left the code for the built-in operator management commands I created on my GitHub to give people an idea of what the API would need to support. As much as I would like to participate, I am not familiar with expanding/making an API. I only know how to use it.

https://github.com/Mickey42302/Paper/tree/operator/paper-server/src/main/java/io/papermc/paper/command

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 reviewing the linked command code under paper-server/src/main/java/io/papermc/paper/command, then trace the existing API entry points for operator status. Identify how permission levels 0–4 and bypassesPlayerLimit are represented and exposed. Done means plugins can set, unset, and check both operator permission levels and the bypass flag through the API.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, authorization
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.