RankSystem: organize a building team with clear roles

Define a builder role, inherit a shared base and keep individual permission exceptions understandable.

Content language

A building team needs recognizable roles and a manageable set of commands. RankSystem lets you define those roles once, inherit a shared base and assign ranks to individual users. A builder can have a useful identity without receiving every operator command.

Install the PHAR on your PocketMine server, not in Bedrock Resource Packs or Behavior Packs. The example below uses the SQLite provider.

Install and locate the settings

Enter stop in the server console and wait for shutdown. Back up its data, then place RankSystem.phar inside the server’s plugins directory. A hosted server may use a custom plugins path; use the one configured for that server. Keep only one RankSystem PHAR in that directory and move any older version to your backup.

Start the server normally. Look for Enabling RankSystem v1.2.2; the generated settings live in plugin_data/RankSystem. This example uses the plugin's SQLite provider, so it needs no separate database account. Stop the server again before editing YAML. Keep both the configuration files and the database when backing up: ranks describe the roles, while the database stores users' assignments.

Give the role a clear purpose

Open ranks.yml and add a new top-level entry alongside the existing ranks, before the final ... if present. Use spaces for indentation. The following example is for a server that also has MultiWorld installed:

Builder:
  nametag:
    prefix: '[Builder] '
    nameColor: ''
  chat:
    prefix: '[Builder] '
    nameColor: ''
    chatFormat: ': '
  permissions:
    - multiworld.command
    - multiworld.command.list
  inheritance:
    - Guest

The role inherits Guest and adds the two MultiWorld nodes used for its world list. It omits world creation and deletion permissions. Without MultiWorld, start with permissions: [], then add real nodes from the plugins your team uses. A permission name describes access to an existing feature; inventing a name does not create that feature.

In config.yml, keep Default_Rank: Guest. Add Builder between Admin and Guest in the existing Hierarchy list. This order controls rank priority for presentation; the inheritance list in ranks.yml controls which rank definitions are inherited. Leave unrelated settings alone, save the files and start the server cleanly.

Assign, inspect and remove a rank

Run these in the console without /, replacing Alex with the intended account name:

ranks list
ranks rankinfo Builder
ranks setrank Alex Builder
ranks userinfo Alex

Inspect the role first, then the user's assignments. setrank adds a rank: RankSystem allows multiple ranks, so it does not silently replace every existing one. To remove this particular assignment, use ranks removerank Alex Builder.

For in-game administration, add / and use an account with the corresponding management permission. For example, rank assignment requires ranksystem.command.setrank. The create, edit and manage commands use in-game forms in this release; they are not console substitutes for the YAML editing route above.

Check the role from the player’s side

Use the Builder account without operator status. In our example, /mw list succeeds and lists the lobby and workshop. The role grants multiworld.command and multiworld.command.list, while Guest supplies its shared base permissions.

The non-operator Builder successfully lists the lobby and workshop with MultiWorld.

The non-operator Builder can inspect the loaded worlds. The lobby behind the message is our own demonstration build.

Creating a world is a different permission. With this role, /mw create forbidden_test 123 flat is refused. The current plugin/server combination displays the untranslated red key %commands.generic.permission for that refusal; in this setup it means permission denied, not a successful world creation.

The Builder world-creation attempt is refused with the red key %commands.generic.permission.

The create command is refused, although this setup shows a translation key instead of a polished error message.

Keep maintenance permissions with the people who run the server. If an action unexpectedly succeeds, check operator status, inherited ranks and direct permissions before changing the role. Our sent chat messages also displayed the configured [Builder] prefix; the pictures above focus on the two command outcomes.

Keep exceptions separate from roles

A direct user permission is separate from a rank. Use ranks permissions pocketmine or ranks permissions MultiWorld to inspect registered nodes. For a one-off assignment, the syntax is ranks setpermission Alex permission.node; remove that direct assignment with ranks removepermission Alex permission.node. Replace permission.node with an actual node, not that literal example.

Removing a direct entry does not erase an inherited copy of the same permission. Check the user's other ranks and the global permission list before deciding where access comes from. Prefer shared role definitions for recurring responsibilities, and reserve individual entries for clear exceptions.

After an update, check startup and inspect the saved rank definitions before changing several settings at once. Keep a dated copy of ranks.yml, config.yml and the configured SQLite database while the server is stopped, so the team structure and its assignments can be restored together.

Keeping an older server

Match the connecting client to the server’s game protocol as well as choosing a compatible plugin API. The selected file’s requirements keep those two checks separate.

No ratings yet

Files

Filter files Files: 1All release types
Show all files

Version 1.2.2

Stable

RankSystem.phar

Server software: PocketMine-MP
2 downloads
Download · 197.7 KB
Requirements & details

PocketMine plugin · API 5.36.0

  • Server software: PocketMine-MP · Server API version: 5.36.0

Stop the server, place the intact RankSystem.phar in plugins, then start it normally. The plugin declares minimum API 5.36.0. Match the client to the server: PocketMine-MP 5.44.3 targets Bedrock 26.30; the additional Axolotl-PM 5.49.1 example uses PHP 8.3.29 ZTS and Bedrock 26.52 on Windows. This is a server plugin, not a local-world add-on, Microsoft Bedrock Dedicated Server plugin or Realms pack.

Requirements & notes
Server runtime requirements
Original server-side setup: PocketMine-MP 5.44.3 with PHP 8.2.30, targeting Bedrock 26.30. The additional example uses RankSystem 1.2.2 on Axolotl-PM 5.49.1 with PHP 8.3.29 ZTS and Bedrock 26.52 on Windows. It checks allowed and denied commands for the configured Builder role using the SQLite provider. The original declared minimum plugin API remains 5.36.0.

Release updates

Version 1.2.2

Stable

Original RankSystem author PHAR. The guide retains the PocketMine-MP 5.44.3 server-side setup and adds allowed and denied command checks for its configured Builder role on Axolotl-PM 5.49.1 with PHP 8.3.29 ZTS and Bedrock 26.52 on Windows. This documents the named setup and does not change the original declared minimum API 5.36.0.

View files

Comments 0

Share what worked, ask for help or reply to another player.

Join the conversation

1Your name & email

No account required. Confirm your email with a code before your first comment. Only a masked address appears with your name. Guest comments are reviewed before publication.

2Verify & post

No comments yet. Share what worked for you.

Search Modonix

Search in