Data Files

Everything RallyPoint stores lives in plugins/RallyPoint/ as YAML. There is no database option.

File	Contents	Created
config.yml	All settings and messages.	On first run.
players.yml	Opt-in state per player UUID, plus the rally serial each player last saw.	When the first player opts in or out.
waypoints.yml	Named waypoints: world and coordinates.	When the first waypoint is saved.
returns.yml	Return points for players who have been rallied and not yet sent home.	When the first rally fires.
session.yml	The live event: current rally point, loaded tour and position, and rally history.	When a rally fires or a tour is loaded.
stage.yml	The game mode each held player had before stage mode.	Only while stage mode is active.

players.yml

Written the moment a player opts in or out, not only on shutdown, so a crash never loses an opt-in. save-interval-seconds is a periodic backstop on top of that.

The loader is deliberately forgiving. A missing, empty, or partially malformed file loads with warnings in the console rather than failing plugin startup, and entries written by pre-1.0 builds as plain booleans are still understood.

waypoints.yml

Saved to disk immediately when a waypoint is set or removed, so a route registered the day before an event survives a restart. /rally waypoint set <name> overwrites an existing waypoint of the same name, which is the intended way to nudge a stop to a better spot.

/rally reload re-reads this file, so editing it by hand is workable if you would rather adjust coordinates in a text editor than fly back to the spot.

A waypoint in a world that is not loaded yet when RallyPoint starts - a Multiverse world brought up after the plugin, for example - is kept and starts working once that world loads, rather than being dropped and erased on the next save.

returns.yml

Holds where each rallied player was standing before the rally that moved them. Entries are cleared as players are sent home. Anyone offline during /rally return keeps their entry and is teleported home on their next login.

An entry with no matching player is harmless: it is simply never used. Return points in a world that has not loaded yet are preserved too, the same way waypoints are.

session.yml

The live state of the event, written whenever it changes so a restart or crash mid-event carries on where it left off. It holds:

• The current rally point - where /rally catchup sends latecomers, and the serial number that drives missed-rally notices.
• The loaded tour and position - the ordered list of stops and which one the host is on, so a tour resumes at the same stop after a restart. See Tours.
• Rally history - the recent rallies shown by /rally history.

/rally reload does not touch this file; it is the running event, not configuration. There is normally no reason to edit it by hand. Deleting it between events simply starts the next event with a clean slate.

stage.yml

Exists only while stage mode is holding somebody. It records whether stage mode is active, which mode is in use, and the previous game mode of every held player. It is deleted once nobody is held.

If you find this file on a server where stage mode is not running, the plugin stopped mid-mode. Leave it in place: RallyPoint reads it on the next start and restores everyone.

Backups

Copy the whole plugins/RallyPoint/ directory. The one worth keeping is waypoints.yml, since a registered route represents real setup work. Opt-in state is cheap to rebuild, and return points and session.yml are only meaningful during an event.

Take the copy while no event is running, since the plugin writes these files as state changes rather than only on shutdown.