PaperMC / PaperMC/Paper

Permission nodes for more utility blocks/items.

Open
#12,658 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?

Paper already has permission nodes for Command Blocks and Debug Sticks (https://docs.papermc.io/paper/reference/permissions/). However, a number of utility blocks/items still do not have a permission node, such as Structure Blocks, Jigsaw Blocks, and Test Blocks/Test Instance Blocks. This makes it impossible to give users access to them without giving them operator access.

Describe the solution you'd like.

Adding permission nodes for these blocks/items would be helpful.

Structure Blocks/Jigsaw Blocks are typically used as tools for content creation. Permission nodes for these would allow server owners to grant access to people that need them.

Test Instance Blocks/Test Blocks are a somewhat new feature that is used with the "/test" command. Permission nodes for these would allow server owners to give staff members the ability to use them with the "/test" command.

Describe alternatives you've considered.

I have asked forks of Paper about this feature, 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

Start with Paper's permission reference, especially the existing Command Block and Debug Stick entries, and trace their corresponding permission handling. Identify how Structure Blocks, Jigsaw Blocks, Test Blocks, and Test Instance Blocks are exposed to the /test command or item use. Done means each named utility has a documented permission node that grants access without operator status.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.