Staff Performance
The Performance page ranks every staff member by a single combined score that weighs tickets handled, moderation actions taken, in-game activity, applications reviewed and outstanding strikes. It is the fastest way to see who is carrying your team and who has gone quiet.
Accessing Performance
- Open your server in the dashboard
- In the sidebar under Staff, click Performance
Performance scoring must be enabled in the configuration before scores are calculated. If the page is empty, open the settings panel and toggle the system on.
How the Score Works
Each staff member's score for the selected period is calculated from five inputs:
| Input | Default weight | Notes |
|---|---|---|
| Tickets resolved | per ticket | Counts tickets the staff member closed |
| Moderation actions | per action | Bans, mutes, warns, kicks across Discord and Roblox |
| Activity hours | per hour | In-game session minutes from the Adonis plugin, converted to hours |
| Applications reviewed | per submission | Counts approvals + rejections |
| Strike penalty | subtracted | A flat penalty per active strike on the staff member |
The score is the sum of those points minus the strike penalty. The ranking on the leaderboard is straightforward: higher score = higher rank.
Period Selector
A dropdown at the top of the page lets you scope the leaderboard:
- Last 7 days
- Last 14 days
- Last 30 days (default)
- Last 90 days
- All time
Switching the period re-calculates every score on the fly using only the activity inside that window.
Adjusting the Weights
Click the Settings button next to the period selector to open the configuration panel. From there you can:
- Toggle the Enabled switch — when off, no scoring runs and the page is hidden from non-admins.
- Edit each weight individually. The weights are integers — tune them so one type of work isn't dominating the rest.
- Edit the Penalty per strike to make active strikes count for more (or less) against the score.
- Click Save to persist changes. The leaderboard refreshes immediately.
Tuning Tips
- Start with the defaults for a few weeks, see who lands where, then tune.
- If your team is mostly handling tickets, raise the activity weight slightly so in-game presence still matters.
- Don't make the strike penalty too aggressive — one strike from months ago shouldn't drop a top performer to the bottom.
Per-Staff Breakdown
Click a staff member in the leaderboard to open their detailed breakdown. Each card shows:
- Total score for the selected period
- Per-input contribution — exactly how many points came from tickets, mod actions, activity hours and applications, plus the strike penalty deducted
- Raw counts — the underlying numbers (tickets resolved, mod actions taken, activity minutes, applications reviewed, active strikes)
This is the right place to go when a staff member asks "why am I ranked so low" — you can show them which inputs are dragging the score and which are carrying it.
Required Permissions
| Action | Required permission |
|---|---|
| View the leaderboard | Discord Administrator or staff with staff_performance section read access |
| Edit the score weights | Discord Administrator only |
Best Practices
- Use Performance as one signal, not the only one. A high score with bad attitude is still a problem; a low score from a new hire is usually just inexperience.
- Share the weights with your team so the rules are transparent.
- Review the leaderboard at the same cadence you review staff overall (weekly or monthly). It loses meaning if you only check it during disputes.
Related Sections
- Staff Activity — raw in-game activity tracking
- Staff Quota — enforce minimum activity goals
- Strikes — issue / clear strikes that affect performance scores