WOS101 — Event Command

Field plannerStage / Before the event

Arrange the hive, traps, banners, city positions, and player seating before the Bear Hunt timer starts.

People and roles: One coordinator with the player list and intended seating plan.
You will need: Player names, field arrangement, city positions, and optional march calibration.
The board produces: A device-saved layout, seating state, estimated travel, and exportable plan or player list.
Important boundary: Travel is an estimate. The board does not replace live march time or the frozen Bear Ratio Calculator.

Board state: local planning surface; exported files carry the plan between devices.

Timing toolStage / Before launch and takeover

Synchronise separate counter rallies to the selected enemy impact that removes the primary leader from the castle.

People and roles: One caller, the primary leader, and every counter-rally leader.
You will need: Primary timer and march, counter timer and marches, enemy ETAs, selected removal rally, and takeover offset.
The tool produces: Counter create order, common impact, live countdown states, and a call that can be copied or shared.
Important boundary: The launch result depends on the enemy ETA and timing inputs. Missing or late states must be resolved before the call.

Tool state: timing planner; verify every live timer against the game before calling launch.

3D planning boardStage / Before the event

Assign teams to buildings and rehearse an ordered capture route before the Foundry battle begins.

People and roles: One caller plus team leads who know their team label and callsign.
You will need: Team assignments, building order, route name, and the lead responsible for each call.
The board produces: Device-saved team tags, callsigns, and ordered paths that can be replayed on the 3D board.
Important boundary: This is a local planning board, not a live game feed. Confirm event rules and current conditions separately.

Board state: route rehearsal and local assignment surface; tactical claims still require event evidence.

3D planning boardStage / Before the event

Choose one sector and rehearse the order in which its forts should appear in the alliance route.

People and roles: One caller and the lead responsible for the selected sector.
You will need: West, East, or South sector; fort order; named route; and any intended hold points.
The board produces: A saved sector route that can be played on the 3D map to review the order before the event.
Important boundary: The route is a rehearsal plan. Confirm the event state and unresolved assignments before issuing a live call.

Board state: sector-route rehearsal; event-specific recommendations remain evidence-dependent.

3D command boardStage / Before and during calls

Make the selected castle or turret, assigned lead, timer state, and next alliance call visible in one command view.

People and roles: One overall caller, a castle lead, and named leads for every active turret.
You will need: Selected focus point, assigned leads, current timer state, and the call being prepared.
The board produces: Local assignments, focused target information, a battle clock, and an opening, hold, or break-call view.
Important boundary: Check the current event panel for exact rules and conditions. The 3D board does not read the live game.

Board state: local command surface; live ownership and event rules must be verified in game.

Which event are you preparing?