Permissions
The four permission nodes, what each one grants or blocks, and the wildcard trap that makes staff score nothing.
EventPulse registers four nodes. Two gate the commands, one stops a player from ever being counted, and one decides who hears the announcements.
| Node | What it does | Default |
|---|---|---|
eventpulse.use | The player side: /event, next, top, stats, toggle and claim | everyone |
eventpulse.admin | start, stop, skip, time, list and reload | op |
eventpulse.bypass | Nothing this player does is ever counted, in any event | nobody |
eventpulse.notify | Receives the start, warning and end broadcasts and their sounds | everyone |
The bypass trap
eventpulse.bypass is meant for staff who are building in creative or testing something and should not turn up on the board. It is off by default, but a permissions plugin that grants * or eventpulse.* grants it along with everything else. An admin with a wildcard therefore counts nothing at all, and that is the single most common reason behind "nothing is being counted".
While an event runs, the console says so once for that player:
[EventPulse] Nothing Steve does is being counted because they have the eventpulse.bypass permission. A permission plugin that gives them * or eventpulse.* gives them this one as well, so take it away if they are meant to compete.The fix is a negative node for that player or group in your permissions plugin, for example -eventpulse.bypass in LuckPerms, or eventpulse.bypass set to false.
Notify
Taking eventpulse.notify away from a player or group silences the three broadcasts and their sounds for them. It does not stop them scoring or seeing the board. Use it for a staff group that does not want event chat, or for a lobby rank.
Tab completion
Tab completion follows the same nodes. A player without eventpulse.admin is not offered the admin sub commands.