Commands
Everything lives under /ecstacy, aliased to /ac. Running /ecstacy with no arguments prints
the interactive help. Rows are clickable and hover for detail.
Every subcommand has its own permission node; see Permissions.
Everyday use
| Command | Does |
|---|---|
/ecstacy menu |
Opens the main GUI panel |
/ecstacy checks |
Opens the checks GUI: view and toggle checks, edit values |
/ecstacy player <name> |
Player detail: reputation, violations, client |
/ecstacy violations [player] |
Recent violation history |
/ecstacy alerts [simulation] |
Toggles alerts for yourself. simulation toggles simulation alerts separately |
/ecstacy logs <player|uuid> [limit] |
Audit log for a player. Limit is 1–200, default 20 |
/ecstacy reputation [player] |
Opens the reputation panel. Aliases: rep, trust |
/ecstacy theme |
Picks a visual theme for the GUIs |
Moderation
| Command | Does |
|---|---|
/ecstacy spectate <player> |
Spectate a flagged player. Alerts link straight to this |
/ecstacy suspicious |
The near-threshold review queue. Players scoring just below the flag bar |
/ecstacy feedback |
Marks a flag TRUE / FALSE / DUNNO. Usually reached from the [Report] suffix on an alert |
/ecstacy replay list [player] |
Lists recorded flag replays |
/ecstacy replay play <id> |
Plays a replay back. Usually reached from the [Replay] button on an alert |
/ecstacy replay stop |
Stops the replay you are watching |
/ecstacy exempt <player> [check|*] |
With no check, shows what the player is exempt from; with one, toggles it |
/ecstacy reputation reset <player> |
Resets a player's reputation |
/ecstacy reputation mode <LOCAL|GLOBAL> |
Switches reputation scope for the licence |
Tip
/ecstacy suspicious is the useful one to check after a tuning change. If a family stops
flagging, the players it nearly flagged still show up here. That tells you whether the check
went quiet or the cheaters did.
Diagnostics
| Command | Does |
|---|---|
/ecstacy cloud |
Connection state, lobby host, ping, last heartbeat |
/ecstacy doctor |
Full connectivity diagnosis. Start here when something is wrong |
/ecstacy update |
Checks for, and downloads, a new build |
/ecstacy reload |
Reloads the configuration files |
/ecstacy debug <info|reload|gc|netdiag> |
Debug utilities |
/ecstacy doctor output is what support asks for first. Paste it verbatim rather than
summarising it. See Troubleshooting.
Note
/ecstacy reload re-reads settings.yml, checks.yml and the message files. Check toggles
changed through the GUI are written to disk and synced to the cloud immediately, so a reload is
not needed after using /ecstacy checks.
Which one to reach for
| Situation | Command |
|---|---|
| An alert just fired and you want to see it | /ecstacy replay play <id> from the alert's [Replay] button |
| You think a flag is wrong | /ecstacy feedback from the [Report] suffix, then /ecstacy violations <player> |
| A player insists they are clean | /ecstacy player <name> for reputation, client and violations in one view |
| Nothing is flagging at all | /ecstacy cloud, then /ecstacy suspicious, then /ecstacy doctor |
| You changed a setting and want to see the effect | /ecstacy suspicious: near-misses move before flags do |
| A new player arrives with a bad history | /ecstacy reputation <player> |
| Staff chat is drowning in alerts | /ecstacy alerts for yourself; fail.alert.every in checks.yml for everyone |
| Someone should not be scored at all | /ecstacy exempt <player> [check]: per check, not the blanket permission |
Reading the flag alert
Most moderation starts from an alert rather than from a command. Each one carries two clickable suffixes:
[Replay]: runs/ecstacy replay play <id>for the clip recorded around that flag. Present when the family is inreplay.trigger-checks; Crystal Aura is there by default.[Report]: opens/ecstacy feedbackto mark the flagTRUE,FALSEorDUNNO.
Note
The replay id and the feedback id are different numbers. Only the AI-scored checks carry a
feedback id, so the recorder mints its own for everything else. Use the id shown next to
[Replay], or find the clip with /ecstacy replay list <player>.
Alerts go to holders of ecstacy.notify. If you would rather have none of this in chat and
review everything on the dashboard, alerts.mode: "WEB_ONLY" in settings.yml switches the
whole server over without touching detection.
Console
Everything except the GUI commands (menu, checks, violations, player, reputation,
theme, spectate) works from the console. GUI commands need a player to open the inventory for.
That makes the diagnostic and moderation halves scriptable from a console wrapper or a remote
management panel: cloud, doctor, logs, exempt, reload, update, debug and
reputation reset all run without a player attached. /ecstacy logs <player> [limit] is the
useful one to pipe somewhere. The limit accepts 1 to 200 and defaults to 20.
Permissions at a glance
Every subcommand has its own node, all defaulting to op, and ecstacy.admin grants the set.
Three are enforced by their commands without being declared in plugin.yml: ecstacy.doctor,
ecstacy.profiler and ecstacy.exempt.manage: so grant those explicitly if you use a
permission manager rather than relying on operator status.
ecstacy.exempt.* is not part of ecstacy.admin and defaults to false for everyone. Full
table on the permissions page.