How to Build a Fair Alliance Train Schedule
A train schedule looks simple until the same reliable people are selected repeatedly, winners are unavailable, or officers use different rules. The answer is not more manual checking. It is a clear order of selection that everyone can understand and leadership can apply consistently.
Start with a written selection order
Decide what earns each seat before choosing names. A typical weekly plan may use event results on some days, alliance recognition awards on others and leadership choice for a flexible day. The exact rules matter less than publishing them and applying them consistently.
Keep conductor and VIP rules separate. A player may be eligible for one seat but not the other because of rank, availability, a recent turn or your alliance rules.
- Name the source for each day, such as event placement or alliance award.
- Set the eligible ranks for conductor and VIP.
- Define the tie-break rule before a tie happens.
- State whether substitutions keep the original reward category or move to the next category.
Use cooldowns to spread opportunities
A cooldown prevents a recent conductor being selected again too quickly. Three weeks is a useful example for a busy alliance, but the right period depends on member count and how many train days you allocate.
The key is to check the last actual driving date, not simply the last scheduled date. If a person was scheduled but replaced, the replacement should normally be the person whose cooldown starts.
Plan for availability without creating confusion
Publish a ready window alongside the schedule. When a driver is not available during that window, reallocate the train using the same selection order. This avoids waiting indefinitely and gives members a clear expectation.
Avoid changing the entire week because one person is absent. Replace only the affected seat and keep an audit note for leadership.
- Publish the start time and the latest time a driver must be online.
- Ask conductors to confirm early where possible.
- Use a named fallback order.
- Record the final driver after any reallocation.
What the planner can automate
Alliance Planning Platform can hold member eligibility, schedule assignments and previous turns in one place. Random selection can take configured rules into account, while manual selection can warn leadership when a chosen person is still on cooldown.
Automation should support the alliance rule, not invent it. Configure the rule first, then use the schedule to apply it consistently.
Leadership checklist
- Selection source is defined for every day.
- Conductor and VIP eligibility are configured.
- Cooldown period is agreed and enabled.
- Availability and reallocation window is published.
- Final substitutions are recorded.