Permissions Guide
LilChunks uses a simple but effective permission system to control access to commands and features.Permission Overview
LilChunks has two main permission nodes that control access to different functionality levels:Basic Access
lilchunks.use
View-only permissions for checking status and getting helpAdministrative
lilchunks.admin
Full access to all commands including start, stop, and reloadPermission Nodes
lilchunks.use
Default:true
(all players)Description: Basic permission for read-only commands Allowed Commands:
/lilchunks status
- Check generation status/lilchunks help
- View help information
lilchunks.admin
Default:op
(operators only)Description: Administrative permission for all commands Allowed Commands:
/lilchunks start
- Start chunk pregeneration/lilchunks stop
- Stop chunk pregeneration/lilchunks reload
- Reload configuration- All commands from
lilchunks.use
The
lilchunks.admin
permission automatically includes all lilchunks.use
permissions.Permission Setup
LuckPerms
LuckPerms is the most popular permission plugin. Here’s how to set up LilChunks permissions:PermissionsEx (PEX)
For servers using PermissionsEx:GroupManager
For servers using GroupManager:Default Permission Behavior
Fresh Installation
When LilChunks is first installed, the default permissions are:- All players can use status and help commands
- Only operators can start, stop, and reload
No Permission Plugin
If you don’t have a permission plugin installed:- Operators have full access (all commands)
- Regular players have basic access (status, help only)
Permission Scenarios
Scenario 1: Public Server
Allow all players to check status but restrict generation to staff:Scenario 2: Private Server
Allow trusted players to use generation commands:Scenario 3: Staff Only
Restrict all LilChunks access to staff members:Scenario 4: World-Specific Permissions
Grant permissions only in specific worlds:Permission Testing
Check User Permissions
Verify what permissions a user has:Debug Permission Issues
If permissions aren’t working correctly:-
Check Permission Plugin Status:
-
Verify Permission Nodes:
-
Test with OP:
- Check Plugin Logs: Look for permission-related errors in the server console
Advanced Permission Configuration
Inheritance
Set up permission inheritance for cleaner management:Temporary Permissions
Grant temporary access for specific tasks:Context-Based Permissions
Use contexts for more granular control:Permission Best Practices
🛡️ Principle of Least Privilege
🛡️ Principle of Least Privilege
Grant users only the minimum permissions they need for their role.
👥 Use Groups
👥 Use Groups
Manage permissions through groups rather than individual users.
🔄 Regular Audits
🔄 Regular Audits
Regularly review and audit permissions to ensure they’re still appropriate.
📝 Document Changes
📝 Document Changes
Keep track of permission changes for accountability and troubleshooting.
Troubleshooting Permissions
Commands Not Working
Commands Not Working
Problem: User can’t execute LilChunks commandsSolutions:
- Check if user has required permissions
- Verify permission plugin is working
- Test with OP status
- Check for permission conflicts
- Review server logs for errors
Permission Denied Messages
Permission Denied Messages
Problem: “You don’t have permission” errorSolutions:
- Grant appropriate permission node
- Check permission inheritance
- Verify world/context restrictions
- Clear permission cache if needed
Inconsistent Behavior
Inconsistent Behavior
Problem: Permissions work sometimes but not othersSolutions:
- Check for world-specific permissions
- Review temporary permissions
- Verify group inheritance
- Check for conflicting plugins