🔐 Advanced Permissions & LuckPerms Setup Guide

Last Updated: 2026-05-21 | CMDMaker Version: 2.4.0+

📑 Table of Contents

Overview
Installation
Configuration
Permission System
LuckPerms Integration
Commands
Examples
Troubleshooting

📋 Overview

CMDMaker now features an advanced permission system that gives server administrators fine-grained control over who can use aliases and commands. The system supports:

Per-Alias Permissions: Control which players can use specific aliases
Per-Command Permissions: Allow/deny /cmd and /addcommand access separately
Operator Bypass: Operators (permission level 2+) always have full access
LuckPerms Integration: Full integration with the popular LuckPerms permission plugin
Configuration-Based Fallback: If LuckPerms isn't installed, use built-in JSON configuration
Per-Player Permissions: Grant specific permissions directly to player UUIDs

Permission Hierarchy

Operators (Level 2+): Always have full access - no checks needed
LuckPerms Users: If LuckPerms is installed, permissions are checked via LuckPerms
Config-Based Users: Fallback to permissions.json configuration
Default: No access unless explicitly granted

⚙️ Installation

Step 1: Install the Mod

Install CMDMaker mod to your Minecraft server:

Fabric: Copy JAR to mods/ folder

Quilt: Copy JAR to mods/ folder

Step 2: (Optional) Install LuckPerms

For advanced permission management with groups and inheritance, install LuckPerms:

Download LuckPerms from LuckPerms Downloads
Place the JAR in your mods/ folder
Restart the server
CMDMaker will automatically detect and integrate with LuckPerms

ℹ️ Note: LuckPerms is optional. CMDMaker works perfectly without it using built-in configuration.

Step 3: Server Startup

When the server starts:

CMDMaker will automatically create config/CommandMaker/permissions.json
Default configuration allows all players to use all commands (no restrictions)
LuckPerms integration will be enabled if the plugin is detected

🔧 Configuration

Configuration Locations

Version	Location
Fabric Server/Client	config/CommandMaker/permissions.json
Quilt Server/Client	config/CommandMaker/permissions.json

Default Configuration Structure

The first time the server runs, CMDMaker creates a default permissions.json file with this structure:

{
  "version": "1.0",
  "description": "CMDMaker Advanced Permissions Configuration",
  "useLuckPerms": true,
  "enablePerAliasPermissions": true,
  "aliases": {
    "home": {
      "permission": "cmdmaker.alias.home",
      "description": "Allow players to use the home alias",
      "enabled": true
    }
  },
  "globalPermissions": {
    "cmdmaker.cmd": "Allow use of /cmd command",
    "cmdmaker.addcommand": "Allow use of /addcommand",
    "cmdmaker.manage.alias": "Allow managing aliases",
    "cmdmaker.*": "Allow all cmdmaker features"
  },
  "players": {
    "permissions": {}
  },
  "luckperms": {
    "syncInterval": 300,
    "enabled": true,
    "groupPrefix": "cmdmaker"
  }
}
            

Key Settings

Setting	Type	Default	Description
version	String	"1.0"	Config version for future compatibility
useLuckPerms	Boolean	true	Enable LuckPerms integration if available
enablePerAliasPermissions	Boolean	true	Enable per-alias permission checks

🛡️ Permission System

Permission Nodes

CMDMaker uses hierarchical permission nodes following Minecraft conventions:

Global Permissions

Permission	Description
cmdmaker.*	Admin wildcard, grants all permissions
cmdmaker.cmd	Allow use of /cmd command
cmdmaker.addcommand	Allow use of /addcommand command
cmdmaker.manage.alias	Allow adding/deleting/reloading aliases
cmdmaker.manage.permissions	Allow managing permissions (admin command)

Per-Alias Permissions

cmdmaker.alias.{aliasname} - Allow use of specific alias

Examples:

cmdmaker.alias.home - Use the /home alias
cmdmaker.alias.tp - Use the /tp alias
cmdmaker.alias.ban - Use the /ban alias

How Permissions Are Checked

Console Commands: Always pass - console has full access
Operator Players: Pass if permission level ≥ 2 (default OP level)
LuckPerms Enabled: Check LuckPerms permission if installed
Configuration Fallback: Check permissions.json
Default Deny: If no permission found, access is denied

🎯 LuckPerms Integration

Why LuckPerms?

LuckPerms is the most powerful permission plugin for Minecraft. It provides:

Group Management: Create permission groups for easy bulk assignment
Inheritance: Extend permissions from parent groups
Tracks: Create hierarchical advancement tracks
Prefix/Suffix System: Custom tags for players
Web Editor: Beautiful online configuration interface
Per-World Permissions: Different permissions on different worlds

Setting Up LuckPerms

1. Install LuckPerms

# Download from https://luckperms.net/download

# Place in mods/ folder

# Restart server

2. Create Permission Groups

/lp creategroup member

/lp creategroup moderator

/lp creategroup admin

3. Add CMDMaker Permissions

For Regular Members (limited alias access):

/lp group member permission set cmdmaker.alias.home

/lp group member permission set cmdmaker.alias.spawn

/lp group member permission set cmdmaker.alias.tp

For Moderators (command access):

/lp group moderator permission set cmdmaker.cmd

/lp group moderator permission set cmdmaker.addcommand

/lp group moderator permission set cmdmaker.manage.alias

For Admins (full access):

/lp group admin permission set cmdmaker.*

4. Set Up Track Hierarchy

/lp createtrack promotion member moderator admin

/lp user {player} track set promotion member   # Assign to track at member level

/lp user {player} track set promotion admin    # Promote to admin

5. Assign Players to Groups

/lp user {player} parent set member

/lp user {player} parent set moderator

/lp user {player} parent set admin

⌨️ Commands

/cmd - Manage Aliases (Server-Side)

Requires: cmdmaker.cmd permission

/cmd list                           # List all aliases

/cmd reload                         # Reload aliases (requires cmdmaker.manage.alias)

/cmd add <alias> <target>      # Add an alias (requires cmdmaker.manage.alias)

/cmd del <alias>                 # Delete an alias (requires cmdmaker.manage.alias)

/cmd function <function>         # Execute a function

/addcommand - Alternative Alias Management

Requires: cmdmaker.addcommand permission

/addcommand add <alias> <command>  # Add an alias

/addcommand del <alias>            # Delete an alias

/addcommand reload                 # Reload aliases

/cmmakerperm - Permission Management (Admin Only)

Requires: OP level 4

/cmmakerperm grant <player> <permission>    # Grant permission

/cmmakerperm revoke <player> <permission>   # Revoke permission

/cmmakerperm check <player> <permission>    # Check if player has permission

/cmmakerperm reload                         # Reload permission configuration

💡 Examples

Example 1: Basic Permission Setup (No LuckPerms)

Edit config/CommandMaker/permissions.json:

{
  "players": {
    "permissions": {
      "a1b2c3d4-e5f6-7890-abcd-ef1234567890": [
        "cmdmaker.cmd",
        "cmdmaker.alias.home",
        "cmdmaker.alias.spawn"
      ]
    }
  }
}
            

Example 2: LuckPerms Setup with Groups

# Create groups

/lp creategroup member

/lp creategroup moderator

# Add permissions

/lp group member permission set cmdmaker.alias.home

/lp group moderator permission set cmdmaker.*

# Assign player

/lp user Steve parent set member

/lp user Alex parent set moderator

🔍 Troubleshooting

Issue: Players can't execute aliases

Solution Steps:

Check if player is operator: /op {player}
Check LuckPerms status: /lp info
Check permissions configuration: View permissions.json
Test with console: Execute the alias from console

Issue: LuckPerms not integrating

Solution Steps:

Verify LuckPerms is installed in mods/ folder
Check server log for integration message
Verify LuckPerms is working: /lp info
Check CMDMaker permissions: /lp search cmdmaker

✅ Success! If you see "LuckPerms detected - enabling LuckPerms integration" in the server log, everything is set up correctly.

📚 Resources

CMDMaker v3.0.0+ | Last Updated: 2026-05-21