# Player Roles for Fabric
\nThis is a simple implementation allowing for custom permissions to be assigned to players via Discord-like “roles”.
\nRoles and their permissions are defined within a JSON file, which can be easily modified and reloaded at runtime for rapid iteration.<\/p>\n
The roles.json file is located in the config directory (` But what’s going on here? This JSON file is declaring three roles: `admin`, `spectator` and `everyone`.<\/p>\n `everyone` is the default role: every player will have this role, and it cannot be removed. ### Overrides It is important to consider how overrides are applied when multiple roles target the same things. Conflicts like this are resolved by always choosing the role with the highest level. #### Commands For example, the pattern `.*` matches every possible command, while `gamemode (spectator|adventure)` would match the gamemode command only with spectator and adventure mode. For example: The commands override can additionally make use of the `hidden` rule result, which will allow the command to be used, #### Name Decoration Name decoration might be declared like: Three fields can be optionally declared: #### Chat Types The `chat_type` override declares simply the `chat_type` that should be used: This example will replace all messages for players with a given role to apply the `say_command` style.<\/p>\n It is important to note that Vanilla chat type registry is loaded from the datapack on server start, and cannot be hot-reloaded like the player roles config.<\/p>\n ##### Declaring custom chat types For example, we might declare a `data\/mydatapack\/chat_type\/admin.json`: Role & permission management for Fabric servers<\/p>\n","protected":false},"featured_media":122552,"template":"","meta":{"_minecraft_slug":"player-roles","_minecraft_project_id":"Rt1mrUHm","_minecraft_author":"Patbox","_minecraft_license":"MIT","_minecraft_downloads":35985,"_minecraft_follows":126,"_minecraft_client_side":"unsupported","_minecraft_server_side":"required","_minecraft_storage_type":"zip","_minecraft_archive_name":"player-roles.zip","_minecraft_size_bytes":5066932,"_minecraft_version_count":51,"_minecraft_updated_at":"2026-05-16T14:02:08.884018Z","_minecraft_date_created":"2020-12-17T08:24:57.800588Z","_minecraft_date_modified":"2026-03-31T20:25:40.130154Z","_minecraft_project_url":"https:\/\/modrinth.com\/mod\/player-roles","_minecraft_icon_attachment_id":122552,"_minecraft_imported_at":"2026-06-07T04:55:39+00:00","_minecraft_import_hash":"46bde16a15a3076e0ea9b996f2d1daa2","_minecraft_versions":"","_minecraft_links":"","_minecraft_gallery":"","_minecraft_api_metadata":""},"mod_category":[97,126,92],"mod_loader":[99],"minecraft_version":[47,48,49,50,51,52,54,55,57,677,58,59,36,60,94,102,62,37,40,41,73,74,38,78,79,80,81,82,83,167,163],"class_list":["post-122551","mod","type-mod","status-publish","has-post-thumbnail","hentry","mod_category-fabric","mod_category-management","mod_category-utility","mod_loader-fabric","minecraft_version-1-16-4","minecraft_version-1-16-5","minecraft_version-1-17","minecraft_version-1-17-1","minecraft_version-1-18","minecraft_version-1-18-1","minecraft_version-1-19","minecraft_version-1-19-1","minecraft_version-1-19-3","minecraft_version-1-19-3-rc1","minecraft_version-1-19-4","minecraft_version-1-20","minecraft_version-1-20-1","minecraft_version-1-20-2","minecraft_version-1-20-4","minecraft_version-1-20-6","minecraft_version-1-21","minecraft_version-1-21-1","minecraft_version-1-21-10","minecraft_version-1-21-11","minecraft_version-1-21-2","minecraft_version-1-21-3","minecraft_version-1-21-4","minecraft_version-1-21-5","minecraft_version-1-21-6","minecraft_version-1-21-7","minecraft_version-1-21-8","minecraft_version-1-21-9","minecraft_version-26-1","minecraft_version-26-1-1","minecraft_version-26-1-2"],"yoast_head":"\n
\n“`json
\n{
\n “admin”: {
\n “level”: 100,
\n “overrides”: {
\n “name_decoration”: {
\n “style”: [“red”, “bold”],
\n “suffix”: {“text”: “*”}
\n },
\n “permission_level”: 4,
\n “command_feedback”: true,
\n “commands”: {
\n “.*”: “allow”
\n }
\n }
\n },
\n “spectator”: {
\n “level”: 10,
\n “overrides”: {
\n “commands”: {
\n “gamemode (spectator|adventure)”: “allow”
\n }
\n }
\n },
\n “mute”: {
\n “level”: 1,
\n “overrides”: {
\n “mute”: true
\n }
\n },
\n “everyone”: {
\n “overrides”: {
\n “commands”: {
\n “help”: “allow”,
\n “.*”: “deny”
\n }
\n }
\n }
\n}
\n“`<\/p>\n
\nThe other roles that are specified function as overrides on top of the `everyone` role.<\/p>\n
\nWithin each role declaration, we list a set of overrides. Overrides are the generic system that this mod uses to change game behavior based on roles.
\nCurrently, the supported override types are `commands`, `name_decoration`, `chat_type`, `mute`, `command_feedback`, `permission_level` and `entity_selectors`.<\/p>\n
\nSo, in the case of the example: although `everyone` declares every command except `help` to be disallowed, because `admin` and `spectator` have higher levels, they will override this behaviour.<\/p>\n
\nThe `commands` override is used to manipulate the commands that a player is able to use.
\nEach override entry specifies a regular expression pattern to match, and then a strategy for how to respond when the mod encounters that pattern.<\/p>\n
\nThe strategies that can then be used alongside these patterns are `allow` and `deny`:
\n`allow` will make sure that the player is allowed to use this command, while `deny` will prevent the player from using this command.<\/p>\n
\n“`json
\n“commands”: {
\n “gamemode (spectator|adventure)”: “allow”
\n}
\n“`<\/p>\n
\nwhile hiding it from command suggestions.<\/p>\n
\nThe `name_decoration` override modifies how the names of players with a role are displayed. This can be used to override name colors as well as prepend or append text.
\nThis has lower priority than scoreboard team colors.<\/p>\n
\n“`json
\n“name_decoration”: {
\n “prefix”: {“text”: “[Prefix] “, “color”: “green”},
\n “suffix”: {“text”: “-Suffix”},
\n “style”: [“#ff0000”, “bold”, “underline”],
\n “contexts”: [“chat”, “tab_list”]
\n}
\n“`<\/p>\n
\n – `style`: accepts a list of text formatting types or hex colors
\n – `prefix`: accepts a text component that is prepended before the name
\n – `suffix`: accepts a text component that is appended after the name
\n – `contexts`: accepts a set of possible contexts defining where this decoration should be applied
\n – Accepts: `chat` and `tab_list`
\n – Default: applies to all possible contexts<\/p>\n
\nThe `chat_type` override allows the chat message decorations to be replaced for all players with a role.
\nThis integrates with the Vanilla `minecraft:chat_type` registry, which can be altered with a datapack.<\/p>\n
\n“`json
\n“chat_type”: “minecraft:say_command”
\n“`<\/p>\n
\nCustom chat types can be declared with a custom datapack in `data\/
\n“`json
\n{
\n “chat”: {
\n “decoration”: {
\n “parameters”: [“sender”, “content”],
\n “style”: {},
\n “translation_key”: “%s: %s <- an admin said this!\"\n }\n },\n \"narration\": {\n \"decoration\": {\n \"parameters\": [\"sender\", \"content\"],\n \"style\": {},\n \"translation_key\": \"chat.type.text.narrate\"\n },\n \"priority\": \"chat\"\n }\n}\n```\n\nWhich can be then referenced in an override like:\n```json\n\"chat_type\": \"mydatapack:admin\"\n```\n\n#### Permission Level\nThe `permission_level` override sets the vanilla permission level for assigned players. \nThis is useful for interacting with other mods, as well as with vanilla features that aren't supported by this mod.\n\nPermission level is declared like:\n```json\n\"permission_level\": 4\n```\n\n#### Mute\nThe `mute` override functions very simply by preventing assigned players from typing in chat.\n\nMute is declared like:\n```json\n\"mute\": true\n```\n\n#### Command Feedback\nBy default, all operators receive global feedback when another player runs a command. \nThe `command_feedback` override allows specific roles to receive this same kind of feedback.\n\nCommand feedback is declared like:\n```json\n\"command_feedback\": true\n```\n\n#### Entity Selectors\nNormally, only command sources with a permission level of two or higher can use entity selectors.\nThe `entity_selectors` override allows specific roles to use entity selectors.\n\nEntity selectors can be allowed like:\n```json\n\"entity_selectors\": true\n```\n\n### Other configuration\nRoles can additionally be applied to command blocks or function executors through the configuration file.\nFor example:\n```json\n{\n \"commands\": {\n \"apply\": {\n \"command_block\": true,\n \"function\": true\n },\n \"overrides\": {\n }\n }\n}\n```\n\nIt may also be useful for a role to inherit the overrides from another role.\nThis can be done with the `includes` declaration by referencing other roles with a lower level.\nFor example:\n```json\n{\n \"foo\": {\n \"includes\": [\"bar\"],\n \"overrides\": {\n \"commands\": {\n \".*\": \"allow\"\n }\n }\n },\n \"bar\": {\n \"overrides\": {\n \"name_decoration\": {\n \"style\": \"red\"\n }\n }\n }\n}\n```\n\nWith this configuration, the `foo` role will inherit the red `name_decoration`.\n\n### Applying roles in-game\nOnce you've made modifications to the `roles.json` file, you can reload it by using the `\/role reload`.\n\nAll role management goes through this `role` command via various subcommands. For example:\n\n- `role assign Gegy admin`: assigns the `admin` role to `Gegy`\n- `role remove Gegy admin`: removes the `admin` role from `Gegy`\n- `role list Gegy`: lists all the roles that have been applied to `Gegy`\n- `role reload`: reloads the `roles.json` configuration file\n\n<\/p>\n","protected":false},"excerpt":{"rendered":"