Commands and permissions
Every command with its permission, and the bypass nodes.
Player
| Command | Aliases | Permission |
|---|---|---|
/events | /event, /ev | exyliaevents.commands.events |
/events join <eventId> | exyliaevents.commands.join | |
/events leave | exyliaevents.commands.leave | |
/events start <configId> | exyliaevents.start or exyliaevents.start.<configId> | |
/events stats | exyliaevents.commands.stats | |
/events stats <player> | exyliaevents.commands.stats.others | |
/events music | exyliaevents.commands.music |
/events start is the player-facing start: it is what makes an event something a rank can open,
subject to the limits and cooldowns in Game flow.
Run in game and from the console, /events start <configId> opens the same configuration, but not
the same way. A player who starts it joins it at once, is subject to the start cooldown and the
per-player limit, and, when the configuration has two or more kits, picks the kit from a menu before
the event opens. The console skips all of that and, with two or more kits, starts with no kit. See
Teams, kits and loot · Kits.
Administration
Everything under /eventsadmin needs exyliaevents.admin.
| Command | What it does |
|---|---|
/eventsadmin | Opens the admin panel. |
/eventsadmin reload | Reloads the configuration files. |
/eventsadmin forcestart <eventId> | Starts an event, ignoring the usual gate. |
/eventsadmin forcejoin <player> <eventId> | Puts a player into an event. |
/eventsadmin forcejoinall <eventId> | Puts every online player into an event, reporting how many joined and how many were skipped. |
/eventsadmin forcestop <eventId> | Stops and removes a running event. |
/eventsadmin revive <eventId> <player> | Brings an eliminated player back into a running event. |
/eventsadmin gauntlet start <series> | Starts a saved series with every free player online. |
/eventsadmin gauntlet stop | Cuts the running series short, along with the stage it is playing. |
/eventsadmin export | Dumps every table into dumps/. |
/eventsadmin import <filename> | Reads a dump back. |
Series of events are put together in the menus and covered in Gauntlets.
Sign-up commands live under /eventsadmin inscriptions and need their own node — see
Sign-ups.
Permissions
| Permission | Description |
|---|---|
exyliaevents.admin | The whole /eventsadmin command and the setup menus. |
exyliaevents.admin.inscriptions | The sign-up subcommands. |
exyliaevents.start | /events start, the gauntlet builder in the menus, and the start actions, for every configuration. |
exyliaevents.start.<configId> | The same, for that one configuration only. |
exyliaevents.commands.events | /events |
exyliaevents.commands.join | /events join |
exyliaevents.commands.leave | /events leave |
exyliaevents.commands.stats | /events stats |
exyliaevents.commands.stats.others | /events stats <player> |
exyliaevents.commands.music | /events music |
exyliaevents.cooldown.bypass | Ignore the start cooldown. |
exyliaevents.cooldown.<name> | Whatever nodes you define in start-cooldown-permissions. |
exyliaevents.world.bypass | Join events from a world the world rules would refuse. |
exyliaevents.bypass.blocked-commands | Run commands the whitelist would block inside an event. |
start lets a player open an event from the menu, which is usually a rank perk. admin lets them
create, edit and delete configurations. Do not merge them.
A rank that should only host some events gets exyliaevents.start.<configId> for each of them instead
of exyliaevents.start. The start menu and tab completion then offer that player only those
configurations, /events start refuses the rest, and the gauntlet builder only starts a series whose
every stage they may host.
Grant exyliaevents.commands.events, join, leave, stats and music to everyone. They are
harmless and their absence only produces tickets.
What reload covers
/eventsadmin reload runs four steps and reports on each: the configuration files and menus, the
event configurations, both schedulers, and the sidebars of every running event. A step that fails is
named rather than swallowed.
An edited prefix applies without a restart, and a running event picks up an edited sidebar in place.
It does not reopen the database connection: changing database.yml needs a restart.
Something missing on this page? Tell us on Discord