Tours

A tour is an ordered list of stops the host steps through, rallying the crowd to each one in turn. Instead of registering every stop as a waypoint by hand and remembering the order, you load a route once and move through it with a single repeated command.

Tours are built from another plugin's data rather than typed in. The one source RallyPoint ships with is MineMail: /rally tour load minemail turns every mailbox on the server into a stop.

MineMail is optional

MineMail is an optional soft dependency. /rally tour load minemail is the only thing that needs it; if MineMail is not installed, that command says so and every other RallyPoint feature works as normal. See Installation.

Commands

Loading or clearing a tour requires rally.admin. Stepping through one requires rally.use. See Permissions.

Command	Description	Permission
/rally tour load minemail	Build a tour of every MineMail mailbox.	rally.admin
/rally tour next [force]	Rally the crowd to the next stop.	rally.use
/rally tour prev [force]	Rally back to the previous stop.	rally.use
/rally tour go <n> [force]	Rally to stop number n (as shown by list).	rally.use
/rally tour list [page]	List the stops, marking where the tour is.	rally.use
/rally tour status	Show the current stop.	rally.use
/rally tour clear	Unload the tour.	rally.admin

Stop numbers shown by list and used by go start at 1. /rally tour on its own is the same as /rally tour status.

Running a tour

1. Load the route (once, before the event):

   /rally tour load minemail

   RallyPoint reports how many stops it built. The tour starts "not started" - no one has been moved yet.

2. Check it if you like:

   /rally tour list
   /rally tour status

3. Step through it, one stop at a time, as the event runs:

   /rally tour next

   Each next rallies the crowd to the following stop with the usual countdown, scatter, and arrival title. prev goes back a stop, and go <n> jumps to a specific one - handy for revisiting a build or skipping ahead.

4. Finish, and optionally unload:

   /rally tour clear

   Clearing only unloads the route; it does not move anyone. Run /rally return to send the crowd home as usual.

How stops are ordered

When you load a tour, the stops are sorted so stepping straight through them is a sensible walk:

• World by world, in the server's own world order.
• Within each world, by nearest neighbour starting from that world's spawn - each stop is followed by the closest one not yet visited.

This keeps the route from zig-zagging across the map. The order is fixed when the tour is loaded and saved with it, so list always shows the same numbering.

Where the crowd lands

At each stop the crowd gathers in a ring around the mailbox, facing it, on safe ground - not stacked on top of it. RallyPoint picks a safe spot beside the stop and spreads arrivals around it, falling back sensibly if the immediate surroundings are tight. The destination safety checks still apply, and force skips them for a single step just as it does for a normal rally.

Retrying a refused stop

A tour only advances when a rally actually fires. If a step is refused - the cooldown has not elapsed, nobody is opted in, or the spot failed the safety check - the tour stays on the current stop so you can simply try again:

/rally tour next        # refused: still on the same stop
# ...wait out the cooldown, or:
/rally tour next force   # retry, skipping the safety check

You never lose your place to a failed rally.

Surviving a restart

The loaded tour and your position in it are saved to session.yml. If the server restarts or crashes mid-tour, RallyPoint resumes at the same stop - it logs the tour and position it picked up on enable. You do not need to reload the route or step back to where you were. See Data Files.

/rally reload re-reads config.yml and waypoints.yml only; it leaves a loaded tour untouched.

Tours and waypoints are separate

A tour never touches waypoints.yml. Loading, stepping through, or clearing a tour does not create, change, or remove any named waypoint, and /rally go <name> is unaffected by whether a tour is loaded. You can use both in the same event: a hand-registered waypoint route for the main stops, and a tour for a run of mailboxes, without one disturbing the other.