Commands
Every ExyliaCapture command for players and admins, with the permission each one needs.
Every ExyliaCapture command, with the permission it needs. Event ids complete as you type: start suggests the configured events, stop suggests the ones running.
| Command | What it does | Permission |
|---|---|---|
/capture | Open the list of events: what is running now and what is scheduled. | exyliacapture.use |
/capture top | Open the player leaderboard. Repeating it within 2 seconds is ignored. | exyliacapture.leaderboard |
/capture clantop | Open the clan leaderboard. Repeating it within 2 seconds is ignored. | exyliacapture.leaderboard.clan |
/captureadmin | Open the admin panel: configurations, running events, reload and plugin settings. | exyliacapture.admin |
/captureadmin start <configId> | Start a configured event now. If it cannot start, the chat says why. | exyliacapture.admin |
/captureadmin stop <eventId> | Stop a running event. | exyliacapture.admin |
/captureadmin list | Open the running events menu. From the console it lists them in text. | exyliacapture.admin |
/captureadmin reload | Reload the configuration files, events and menus. A changed database.yml still needs a restart. | exyliacapture.admin |
Start and stop an event#
/captureadmin start <configId> starts an event now, even when it also has a schedule. When it cannot start, the chat gives one line per reason: it is switched off, where it runs is not set, its type is unknown, or another plugin cancelled the start. Fix it in /captureadmin, Configurations, your event. See Your first event.
/captureadmin list opens the running events menu. Click an event to see it, right-click to stop it; stopping always asks you to confirm. From the console, the command prints the running events as text.
What reload does#
/captureadmin reload re-reads config.yml, messages.yml and scoreboards.yml, the event configurations and the menus. It also registers the placeholders of a new event and restarts the scheduler with the current schedules. If a step fails, the console names it and you are told how many worked.
It does not reopen the database. After changing database.yml, restart the server.
The admin command is only /captureadmin. Update any menu, hologram or rank-up command that still uses /cadmin.
Something missing on this page? Tell us on Discord