🔐 Permissions Reference
TrialChamberPro uses a hierarchical permission system. Grant broad access with wildcards or fine-tune with specific permissions.
🎯 Quick Setup
Full Admin Access
permissions:
- tcp.admin.*Grants ALL admin permissions (add, scan, reset, manage keys, etc.)
Player Access (View Stats Only)
permissions:
- tcp.stats
- tcp.leaderboardPlayers can view their own stats and leaderboards. This is default!
Moderator Access (Manage Chambers, No Config)
Can reset chambers, manage keys/vaults, view player stats, but can't modify chamber structure or reload config.
📋 Complete Permission List
Admin Permissions
tcp.admin.*
Description: All admin permissions (wildcard) Default: Operators only Grants access to:
All commands listed below
Complete control over chambers
Configuration management
Use this for: Server owners, head admins
tcp.admin.generate
Description: Register and delete chambers Default: Operators only Allows:
/tcp generate <mode> <args>- Register chambers from WorldEdit selection, coordinates, or blocks/tcp delete <chamber>- Delete chambers/tcp setexit <chamber>- Set exit locations
Use this for: Staff who manage chamber infrastructure
tcp.admin.scan
Description: Scan chambers for vaults and spawners Default: Operators only Allows:
/tcp scan <chamber>- Detect vaults/spawners
Use this for: Staff who set up chambers (usually paired with tcp.admin.create)
tcp.admin.snapshot
Description: Manage chamber snapshots Default: Operators only Allows:
/tcp snapshot create <chamber>- Create snapshots/tcp snapshot restore <chamber>- Restore from snapshots
Use this for: Staff who maintain chambers and handle resets
tcp.admin.reset
Description: Force chamber resets Default: Operators only Allows:
/tcp reset <chamber>- Immediately reset a chamber
Use this for: Moderators who manage events and handle player issues
tcp.admin.key
Description: Manage trial keys Default: Operators only Allows:
/tcp key give <player> <amount> [type]- Give keys to players/tcp key check <player>- Check player's key count
Use this for: Staff who run events or compensate players
tcp.admin.vault
Description: Manage vault cooldowns Default: Operators only Allows:
/tcp vault reset <chamber> <player> [type]- Reset vault cooldowns
Use this for: Staff who handle player support and bug compensation
tcp.admin.reload
Description: Reload plugin configuration Default: Operators only Allows:
/tcp reload- Reload config files
Use this for: Admins who tune configuration
tcp.admin.stats
Description: View other players' statistics Default: Operators only Allows:
/tcp stats <player>- View any player's stats
Use this for: Staff who monitor player activity
tcp.admin
Description: View chamber information Default: Operators only Allows:
/tcp list- List all chambers/tcp info <chamber>- View chamber details
Use this for: Read-only access to chamber data
Player Permissions
tcp.stats
Description: View own statistics Default: All players (true) Allows:
/tcp stats- View your own stats
Typical usage: Default permission for all players
tcp.leaderboard
Description: View leaderboards Default: All players (true) Allows:
/tcp leaderboard <type>- View top players/tcp lb <type>- Alias/tcp top <type>- Alias
Typical usage: Default permission for all players
tcp.spectate
Description: Use spectator mode after death in chambers Default: All players (true) Allows:
Spectate a chamber after dying inside it
Type "spectate" in chat to accept spectator mode offer
Type "exit" to leave spectator mode
Effect:
Switched to GameMode.SPECTATOR on acceptance
Teleported to chamber center
Confined to chamber boundaries (with configurable buffer)
Restored to previous game mode on exit
Typical usage: Default permission for all players (enhances multiplayer experience)
Bypass Permissions
tcp.bypass.cooldown
Description: Bypass vault cooldowns Default: Operators only Effect:
Open vaults regardless of personal cooldown
No waiting period between loot
Use this for:
VIP ranks (be careful with balance!)
Staff testing chambers
Special event participants
Balance Warning: Giving this to regular players removes cooldown mechanics entirely. Consider carefully!
tcp.bypass.protection
Description: Bypass chamber protection Default: Operators only Effect:
Break blocks in protected chambers
Place blocks in protected chambers
Access protected containers
Use this for:
Staff building/modifying chambers
WorldEdit operations inside chambers
DO NOT give to regular players! This allows complete modification of protected chambers.
🎭 Permission Groups Examples
Example 1: Player Rank
Players can view stats and compete on leaderboards. This is the default!
Example 2: VIP Rank
VIPs get instant vault access (no cooldowns). Balance carefully!
Example 3: Helper/Moderator Rank
Helpers can:
View chamber info
View player stats
Give keys to players
Reset vault cooldowns (for bug compensation)
Force chamber resets
Cannot:
Create/delete chambers
Modify configuration
Create snapshots
Example 4: Builder Rank
Builders can:
Register and delete chambers
Scan for vaults/spawners
Create/restore snapshots
Build inside protected chambers
Cannot:
Manage keys or vaults
Reload configuration
Example 5: Admin Rank
Full access to everything. Simple!
🔧 LuckPerms Examples
Grant Full Admin Access
Grant Moderator Access
Create a VIP Group (No Cooldowns)
Create a Builder Group
Grant Temporary Admin Access (24 hours)
🌍 Per-World Permissions
Want staff to manage chambers only in certain worlds?
LuckPerms Example
Steve can only create/scan chambers in the nether.
🎯 Permission Hierarchy
💡 Common Setups
Survival Server
Philosophy: Keep VIPs balanced, give mods tools to help players, admins control everything.
Creative/Building Server
Philosophy: Let builders register chambers freely, admins handle config/keys.
Event/Minigame Server
Philosophy: Event participants get faster loot, hosts can reset chambers and give rewards.
❓ FAQ
"Do I need tcp.admin for tcp.admin.create?" No! Specific permissions (like tcp.admin.create) work independently. tcp.admin only grants access to /tcp list and /tcp info.
"What's the difference between tcp.admin and tcp.admin.*?"
tcp.admin= View chambers (/tcp list,/tcp info)tcp.admin.*= ALL admin permissions (wildcard)
"Can I use negative permissions to remove specific access?" Yes! With LuckPerms or similar plugins:
Steve gets all admin perms EXCEPT reload.
"Does tcp.bypass.cooldown work retroactively?" Yes! If a player has this permission, they can open vaults immediately regardless of existing cooldowns.
"Can I give permissions temporarily?" Yes, with LuckPerms:
"Do these permissions work with permission inheritance?" Yes! If a group has tcp.admin.*, all members inherit all child permissions automatically.
🔗 Related Pages
See which commands require which permissions.
Protection settings and their interaction with bypass permissions.
🛡️ Security Best Practices
Use the least privilege principle: Only grant permissions users actually need. Don't give tcp.admin.* to everyone.
Be careful with bypass permissions: tcp.bypass.cooldown removes progression. tcp.bypass.protection allows chamber destruction.
Never give regular players tcp.bypass.protection unless you want them modifying chambers freely!
🎉 Quick Permission Cheat Sheet
Player
tcp.stats, tcp.leaderboard, tcp.spectate
View stats, compete, spectate
VIP
Same + tcp.bypass.cooldown
Faster loot (optional)
Helper
tcp.admin.key, tcp.admin.vault, tcp.admin.reset
Help players, manage events
Mod
Helper + tcp.admin.stats
Monitor players
Builder
tcp.admin.create, tcp.admin.scan, tcp.admin.snapshot, tcp.bypass.protection
Register chambers
Admin
tcp.admin.*
Full control
Use this as a starting point and adjust to your server's needs!
Last updated