Map Rotation Config

Each server runs its own independent weekly poll (checked Monday 07:00 UTC by /root/single-map-vote.py). Quorum is just one vote — the top-voted candidate wins the cycle, even with a single ballot cast. If a server's poll gets zero votes in a week, its configured fallback decides what happens: Simulate result generates a plausible-looking random tally and picks a site as if the community had voted, while Keep current site leaves the map unchanged and restarts the poll fresh next week. Either way every cycle ends with the tally cleared and a fresh cycle number, so last week's votes never carry over. The winner is applied directly to AMP — the instance's CustomMission is swapped to the new site's mission file (adding its mod to the server if it isn't already installed), and the instance is stopped/started to apply it.

Before this per-server single-site vote, horselab.ca ran a shared 3-slot terrain pool: both servers voted on the same candidate list, visitors could pick up to 3 sites, and a cycle only resolved once at least 3 distinct sites had votes — sometimes sitting unresolved for weeks. The winning set was applied in-game via the Vote-For-Escapist mod's map-voting list rather than as a single fixed site. That system (map-vote-tally.py + its systemd timer) has been stopped and archived to /root/archive/map-vote-v1/ for reference — it is no longer running.