Permissions
DupeTrace keeps things simple with just two permissions. No complicated hierarchies, no nested nodes – just straightforward access control.
Permission Nodes
dupetrace.admin
Access to all /dupetest commands
op
dupetrace.alerts
Receive duplicate detection alerts
op
dupetrace.admin
dupetrace.adminDefault: Server operators (op)
Grants access to all DupeTrace commands:
/dupetest give/dupetest uuid/dupetest history/dupetest stats/dupetest search/dupetest discord(test, status, reload)
Who Should Have This?
Give this to:
✅ Server owners
✅ Head admins
✅ Staff members who handle dupe investigations
✅ Moderators you trust with database access
Do NOT give this to:
❌ Regular players (obviously)
❌ Trial staff or junior mods (unless you really trust them)
❌ Build team members who don't need investigation tools
Example Usage (LuckPerms)
Example Usage (PermissionsEx)
dupetrace.alerts
dupetrace.alertsDefault: Server operators (op)
Allows players to receive duplicate detection alerts in chat when a dupe is found.
Alert Example
Who Should Have This?
Give this to:
✅ Server admins
✅ Active moderators
✅ Staff who monitor for exploits
Consider withholding from:
❌ AFK staff members (alert fatigue is real)
❌ Players who panic and make a scene every time there's an alert
❌ Staff who don't need to respond immediately to dupes
Why Separate This Permission?
Not everyone who can investigate dupes (with dupetrace.admin) needs to be notified in real-time. You might want a few trusted admins to receive live alerts while junior staff only use commands when needed.
Example Usage (LuckPerms)
Example Usage (PermissionsEx)
Permission Combinations
Setup #1: Full Admin Access
Use Case: Head admins, server owners, senior moderators
Setup #2: Investigation Only
Use Case: Junior mods, staff who only investigate when asked, build team leads
Setup #3: Alert Watcher
Use Case: This is pretty rare, but could be useful for a "watcher" role who escalates issues to other admins.
Configuration Interaction
The alert-admins setting in your config.yml controls whether alerts are sent to players with the dupetrace.alerts permission:
Even if someone has dupetrace.alerts, they won't get alerts if alert-admins is set to false.
Learn more: Configuration →
Wildcard Permissions
If you're using a wildcard permission plugin, DupeTrace respects common wildcard patterns:
dupetrace.*– Grants both permissions*– Grants everything (standard Minecraft behavior)
Example (LuckPerms)
Frequently Asked Questions
Can regular players see duplicate alerts?
Only if you give them the dupetrace.alerts permission AND broadcast-duplicates is set to true in the config.
By default:
dupetrace.alertsis op-onlybroadcast-duplicatesis enabled
So yes, if you op a player, they'll see alerts. If you want to prevent this, either:
Don't op them (use a permission plugin instead)
Set
broadcast-duplicates: falsein your config
What happens if someone doesn't have permissions?
They'll get the standard "You do not have permission" message when trying to run commands. No alerts will be shown to them either.
Do offline players keep their permissions?
That depends on your permission plugin (LuckPerms, PermissionsEx, etc.). DupeTrace doesn't store or manage permissions – it just checks what your permission plugin says.
Can I create custom permission groups?
Absolutely! Use your permission plugin to create custom groups and assign DupeTrace permissions as needed.
Example (LuckPerms):
Best Practices
🎯 Principle of Least Privilege
Only give permissions to staff who actively need them. Just because someone is a "moderator" doesn't mean they need dupe investigation tools.
🔔 Alert Fatigue is Real
If your staff complain about too many alerts, remove dupetrace.alerts from their group. They can still use commands when needed.
🧪 Test with Trial Staff
When promoting new staff, start them without dupetrace.alerts and grant it after they've proven themselves.
🔒 Audit Regularly
Periodically review who has dupetrace.admin access. People leave staff teams, and permissions should be revoked accordingly.
What's Next?
You've mastered the basics! Ready to dive deeper? Check out the developer docs:
Plugin Architecture →
Core Functions →
Database Schema →
Last updated