Non-OP Command Blocker
by helloairbix
Non-OP Command Blocker lets server operators decide which commands regular players can still run, by keeping a block list that the server applies to non-operator players.
What it does
Operators manage the block list in-game, so a server owner can stop players from using selected commands without removing operator access. Commands on the list are refused for non-operator players, while operators keep full access to every command. The list is stored in a config file, so the blocked commands stay in effect after a server restart.
The mod ships with example entries for the cblock setting, which can grant a specific command to a chosen player when a server needs it. It suits owners who need to narrow the commands players can use while leaving staff unaffected. The mod requires Fabric API and Fabric Loader, and it runs on the server side only, so clients need nothing installed. Files are published for Fabric for 26.1, and the mod is released under the MIT License but is not open source.
Key features
In-game block list
Operators add or remove blocked commands while the server runs, without editing files by hand.
Operator bypass
Operators keep full access to every command, so the block list only affects non-operator players.
Persistent settings
The block list is kept in a config file, and the settings still apply once the server has restarted.
Per-player allowances
Entries such as cblock worldedit allow can grant a specific command to a chosen player despite the block.
Compatibility
Latest build for each game version and loader.
Only full game releases are shown. This mod publishes no snapshot builds.
Requirements
Dependencies declared by the latest file for each loader.
Required 1
Use cases
Restricting plugin-style commands
A server that runs add-on commands can keep them away from regular players while staff still use them.
Protecting shared worlds
Owners of community servers can prevent players from running commands that change the world or the game state.
Who it’s for: The mod suits server owners and operators who want to control which commands regular players can run, while keeping full command access for operators.
How it compares
Player Blocker is a client-side only Fabric mod for 26.1.2 – 26.2, and its license is All rights reserved, so it is not open source. Attack-Blocker is a client-side only Fabric mod for 1.20 – 1.21.11 under the MIT License, and it is open source. NeoForge Command Blocker is a server-side only NeoForge mod for 1.21.1 under All rights reserved, so it is not open source and it does not run on Fabric.
| Mod | Loaders | Game versions | Environment | Updated |
|---|---|---|---|---|
| Non-OP Command Blocker | Fabric | 26.1 | Server-side only | 2026-04-01 |
| Player Blocker | Fabric | 26.1.2 – 26.2 | Client-side only | 2026-06-18 |
| Attack-Blocker | Fabric | 1.20 – 1.21.11 | Client-side only | 2025-11-30 |
| NeoForge Command Blocker | NeoForge | 1.21.1 | Server-side only | 2026-05-31 |
Questions
Does Non-OP Command Blocker need Fabric API?
Do players need to install the mod?
Do blocked commands survive a server restart?
In the catalog
Non-OP Command Blocker is one of 8,016 Management mods on ModsFinder, and one of 5,930 Management mods for Fabric. 11,959 mods support Minecraft 26.1.
More from helloairbix
Similar mods
What the author says
Ex). /cblock worldedit allow Ex). /cblock spark allow Ex). /cblock vanish allow Blocked commands are saved to a config file, so your settings stay after server restarts.
Official listing
- Modrinth page
- modrinth.com/mod/cblocker-mod
- Owner
- helloairbix
- Published
- 2026-03-31
- Updated on Modrinth
- 2026-04-01
- Facts verified
- 2026-10-15