Skip to main content

Train scheduling

The Train is a weekly conductor and VIP rota. Officers can build it manually or enable Monday automation: saved rules are used when available, otherwise Last Command selects random active members. Manual assignments remain under officer control.

What the train is

Each day has a conductor slot and an optional VIP choice. Officers can assign both, or select only the conductor and let that player nominate a VIP. The platform coordinates your plan and reminders; players still carry out the train actions in game.

Try it

// LIVE DEMO · SAMPLE DATA

Oct 5 – Oct 11

The actual production schedule view, running against this week's dates with seven days populated by VS and donation ranking rules. Click any day to override the conductor or VIP — the source pill flips from 'auto' to 'manual' to make pinned slots obvious.

Configuring the rules

Open Train → Rules (R4+ only). For each of the seven days, configure one rule per slot. The platform supports six rule types:

  • VS ranking position — “the Nth-ranked player in last week's Alliance Duel.” The most common rule. Whoever sits at position 1 gets a slot, and so on down the leaderboard.
  • Donation ranking position — same pattern, but against the donation rankings. Useful for the day of the week you want to recognise donors.
  • Contribution ranking position — uses the combined participation ranking prepared before the Monday run.
  • Random — picks an active member who has not already been used that week where the roster allows.
  • Custom — free-text description (e.g. “dice game winner”, “newcomer of the week”) for slots officers want to fill manually.
  • Manual — deliberately leaves the slot for an officer to assign.

A no back-to-back toggle skips anyone who was conductor or VIP last week, so the same handful of top contributors don't hog every slot.

// NOTE

Automatic scheduling is a Pro switch under Train → Rules. When enabled, it runs every Monday at 06:00 UTC. Saved Normal, Push or Save rules take priority; if no rules are saved, Last Command falls back to random active members. When the switch is off, no automatic schedule is created.

Voting and conductor-nominated VIPs

Open Train → Voting & VIP choices. R4/R5 officers choose whether officers assign the VIP or the conductor nominates them, and whether voting is off, daily for the next game day, or weekly for the following week. Existing alliances keep officer-controlled assignments until this is changed.

Officers open the next available ballot. Members can vote within its displayed deadline; daily ballots choose one candidate and weekly ballots allow up to seven. Self-voting follows the alliance’s setting. Results inform the officers’ choice and do not automatically overwrite the rota.

An assigned conductor can choose a VIP from eligible current members while nominations are open. Recommendations explain recent recorded contributions and kudos, where available. Missing evidence is not a negative score. The final choice remains with the conductor, and an officer-assigned VIP is protected from being silently replaced.

// TIP

Example: the alliance votes this week for next week’s conductors. Officers review the results and ties, set the rota, and leave VIPs to conductor nomination. A conductor can recognise a teammate’s recent effort using the recommendation evidence rather than always selecting the strongest player.

Daily departure and replacements

The departure-time update adds Set departure time at the top of Train on web and iOS, and in Discord under /lc admin reminders → Train → Set departure time. Only linked R4/R5 officers can change the alliance setting. Check What’s new for rollout availability.

Enter the normal daily time and timezone—for example, 20:00 Europe/London. Reminders count back from that departure, not from server reset. Choose UTC for fixed game timing or a local timezone that follows daylight saving. Each train date still belongs to the game day between server resets.

// TIP

Example: the train normally leaves at 20:00 and shared reminders are set to 30 minutes. The Discord reminder is due at 19:30 in the chosen timezone. If the conductor is unavailable, an officer chooses Replace conductor, selects the person taking over and records a reason. When the train is actually sent, the conductor or an officer confirms Mark train sent.

The record keeps the original and replacement conductors, the reason, and when the change was recorded. Marking sent records the current time, completes today’s train and stops its remaining reminders. This does not launch the train in game, infer online status or automatically penalise attendance.

A conductor-nominated VIP is cleared when that conductor is replaced; an officer-assigned VIP stays. Future days are unchanged. With a configured departure time, nominations stay open until the train is recorded as sent or the game day ends, allowing a late replacement to choose a VIP.

Existing alliances keep reset-based reminders until an officer sets a time. A daylight-saving clock change that skips the chosen local time has no departure reminder that day; repeated times use the first occurrence. Avoid the clock-change hour or choose UTC if that would be inconvenient.

Manual overrides

Sometimes the rules pick someone who can't make their slot. Officers can override any day to pin a specific player, and the override sticks for that day only — the rest of the week continues to follow the rules. Overrides also surface clearly on the schedule page so it's obvious which slots are pinned.

Reminders

Members see when they're up on the schedule grid, and get a personal reminder at their chosen lead time via the channels they've enabled (push, in-app, email, Discord). The reminder includes their role (conductor or VIP) and the day so there's no ambiguity about what's expected.