op permission level glitch
Open
Nobody has claimed this yet.
priority: low
status: accepted
status: unlikely
type: bug
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Expected behavior
when I set op permission level in server.properties to 0~3, ops can't use /stop command
Observed/Actual behavior
when I set op permission level in server.properties to 0~3, ops can use /stop and other commands freely even 0.
Steps/models to reproduce
set op-permission-level in server.properties to 0~3
deop yourself and op again through console
test /stop
Plugin and Datapack List
none
Paper version
1.18.1 -160
Other
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior with op-permission-level set to 0 through 3 in server.properties, then deop and re-op through the console and test /stop. Compare the command's permission handling with the configured level; done means operators at those levels cannot use /stop or other commands that require higher permission.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100