HSHOT SPOTSSTEEL DOMINIONHOT SPOTS / CAMPAIGN CONTROL

Aces reconnaissance, waypoints and reinforcements

Aces organizers and players · Reviewed for v433

Prepare the current sortie, reveal its information as play proceeds, and retain branch, dice and expense evidence.

Prepare and reveal

  1. Record session attendance, choose an unlocked sortie as GM or vote on a player suggestion, then read Current briefing. Agree reconnaissance before revealing its results; even skipping reconnaissance is an explicit plan. The app retains paid options and one-time physical or app dice.

  2. Select units from the shared force, assign eligible named pilots and choose the deployed force commander. The adjusted allowance includes difficulty and earned-pilot-SP restrictions. Sortie 16 also needs a separate plant-defense force within the combined allowance.

  3. Sortie 08 begins at 150 PV. Its optional 200 SP reinforcement purchase adds 60 PV, making 210 PV or 6,300 BV. The reinforcement adds 60 to the original 150, rather than using the inconsistent printed total.

  4. Reveal tabletop-triggered waypoints from Revealed waypoints. Paid reconnaissance, branch outcomes and commander salvage have server-side prerequisites. Revealing a position only does not award its ignored SP or other effects. The tabletop still determines distances, facing, nearest units and positional damage.

Resolve arrivals

  1. Battlefield presence and arrivals lists newly revealed units. Confirm each role/subtype deck for the mission, including role overrides and extra deck copies. Confirm an arrival before completing its phase. Physical card entry uses the printed ordinal, not the priority number.

  2. The printed 06-B repeats reserve unit 5 while unit 6 is also a reserve. The app asks which actual reserve arrives and retains that choice instead of silently changing the publication.

  3. The supplied Aces emplacement cards provide the three standard templates automatically: 3× AC/2 light, 2× AC/5 medium and AC/20 heavy. Scenario source templates shows the card source and adaptation. The cards have no Size rating; the assistant does not invent one. Existing bound records retain their saved source until the organizer uses Use supplied card and adaptation during preparation. Recorded damage or a deployed template prevents replacement.

  4. Use saved presence to record reserves, retreats, immobility and transport links. Apply tabletop transport capacity and entry rules. Scenario allies are distinct from purchased units; only explicitly exempt allies avoid the deployment allowance.

Optional tutorials and campaign ending

  1. Tabletop > Optional Aces tutorials offers the BattleROM guided tutorial and Training Simulator as tabletop reference sessions. They are optional and separate from the live campaign sortie tracker. Follow their printed instructions with tabletop pieces and cards; skip them whenever the group is ready to prepare the starting force.

  2. Training Simulator waypoint entries reveal independently when triggered at the table. Confirm that the tutorial ended before revealing its outcome and recording a score from 0 to 10 VP. Tutorial reveals and scores never change the Warchest, pilot SP, injuries or campaign keywords.

  3. Campaign reference provides the introductory Scouring Sands campaign pages. The campaign epilogue stays unavailable until the final route choice approves it. Future mission and unrevealed waypoint images remain unavailable to every player, including the organizer.

Saved placement and force allowance

  1. Prepare mission force shows selected base PV/BV, the adjusted allowance, the remaining allowance and unselected owned units. Plant defenders share the combined allowance; a unit may belong to only one force. Pilot selectors offer compatible living, unwounded pilots, with generic crew as an option.

  2. Placement dice may be entered from physical dice or rolled in the assistant. The saved arrival shows its die and printed corner result. Arrival confirmation cannot be repeated. Sortie 16 similarly saves one plant-defense die and compares the actual defender value with the PV threshold, multiplied by 30 for Classic or Override.

Preparation pages and attendance

  1. Campaign > Prepare mission force opens unit and pilot selection directly. Save the deployed roster and choose Continue to mission readiness. Readiness shows only the next missing requirement: attendance, reconnaissance, the saved force, required opposition preparation or earned pilot SP. Follow its exact correction link, save and return; when a choice is awaiting approval, readiness links to its vote. After all required preparation is saved, enter tabletop player count and Begin prepared sortie. Deck-enabled play opens Shared initiative; bookkeeping-only Aces play opens the current briefing.

  2. Session attendance lets the organizer choose attending campaign accounts; each player may also mark their own attendance. Changing attendance cancels open session-decision votes so the group can submit new suggestions for the current attendees. Campaign-wide purchase votes keep their electorate. The tabletop player count entered before beginning may include offline players.

  3. After settlement, invest the awarded pilot SP, then confirm progression complete. The app returns to the next-mission narrative and legal route choices, also available through Campaign > Briefing and route choices. A GM route save unlocks the next briefing immediately. A player route suggestion requires a completed vote or explicit Apply as GM; suggesting it alone does not reveal the briefing.

  4. If readiness asks for opposition decks, its correction link opens the whole Mission opposition decks table. Review the mission deck and copy number on every row, then use Confirm all deck assignments. This confirms the editable roster together and returns to readiness, instead of opening a separate editor for each unit.

Browse all help topics · Release notes