EventPulse logoEventPulse

Commands

Every command, its arguments, what it does and the permission it needs, for players and for admins.

The command is /eventpulse, with /event, /events and /ep as aliases. If another plugin already registers one of those names, whichever loads first takes the plain name and this one is still reachable as /eventpulse:event. Every sub command tab completes.

All of these need eventpulse.use, which everyone has by default.

CommandWhat it does
/eventShows the running event and the time left, or the time until the next one
/event nextThe time until the next event, or a note that none is scheduled when the scheduler is off
/event topThe lifetime leaderboard across every event, top ten
/event top <id>The leaderboard for one event id
/event statsYour own wins, participations and FarmPoints
/event stats <player>The same for another player, online or not
/event toggleTurns the event scoreboard off or on for you. Saved, so it survives a rejoin
/event claimHands over any rewards waiting for you from an event you were offline for

A manual start is refused with an on-screen message when the scheduler's recent or exclusion check lands on the event you named, for example because one of its excludes ran within the cooldown between events or because it was picked too recently to be picked again. The message points you at force, and force skips that check and starts it anyway. The automatic scheduler still honours excludes on its own picks, it only skips them when you start an event by hand with force.

Zone wand

The objective events place things inside named areas, and those areas are written with the wand rather than by hand in zones.yml. The whole thing is /event admin zone.

  1. /event admin zone wand gives you a blaze rod named Zone Wand.
  2. Right click the first corner of the area, then right click the second corner. The two corners are the opposite corners of the area, not two adjacent ones, and the area is the cuboid between them.
  3. /event admin zone save <name> writes it to zones.yml under that name, lowercased. The name can use letters, numbers, underscore and hyphen, and the area may be no wider than 512 blocks on any side.
  4. To mark a named point inside a saved zone, /event admin zone point <name> <point> arms the wand for one click, and the next right click places that point. Points are where some event types set their objectives down, and they must sit inside the zone.
  5. /event admin zone list shows what is saved and /event admin zone delete <name> removes one.

A zone only has to exist for the events that name it. Save the zone first and then the events that use it, because an objective event that points at a zone that is not in zones.yml is dropped at load with a warning naming the missing zone. See Event types for which settings take a zone.

Notes

Starting while one is running. /event start refuses when an event is already running unless force is given, so a second event cannot be started by accident. Only one event runs at a time.

Reload during an event. The running event keeps the settings it started with, including its rewards, so a reload mid event is safe. The new settings apply from the next event.

Durations for the time command are written like every other duration: 30s, 5m, 1h30m.

Console. Every command works from the console except toggle, claim and stats with no name, which need a player.

On this page