Release notes
Short summaries of changes in this installation, newest first.
v403 · Use the current commander?s token instructions
Movement-only commander cards such as MechWarrior A no longer open or block on Move First/Last assignment. Existing waiting turns also use the corrected applicability rule. Token assignment shows the current card?s instructions, applicable token type and comparison references, including card B?s M damage and Armor criteria. Show applicable commander movement instructions with opposing movement activations; preserve saved review evidence and accounting.
v402 · Readable commander icon legend
Stack the commander icon legend vertically to the right of the card faces on wide screens. Double the symbol size and enlarge the explanatory labels; move the legend below the cards on narrower screens. Use the same readable legend in Aces, Hot Spots and published starting-card previews.
v401 · Commander cards and end-of-combat decisions
Display larger paired commander cards in the assistant, with a legend for their icons, using the existing card renderer and authorized project artwork. At the end of combat, choose the first true printed strategy condition using readable buttons, or None of the above. The next commander card appears immediately, before starting the next turn. Respect each retained deck?s own conditions and maintain-strategy cards; preserve hidden commander access, published versions and one-time decisions. Published starting-card previews now show both card faces and update in place before saving.
v400 · Confirm opposition decks in one table
Mission opposition decks now lists the opposition roster with a deck dropdown and copy number for each unit, plus one confirmation for all editable assignments. A failed row saves no assignments and retains all selections. Readiness corrections return to mission readiness after the whole table is confirmed. The shared Aces and Hot Spots assistant preserves helper access, hidden opposition and locked in-play assignments; newly revealed arrivals remain assignable.
v399 · Require staged deployment acceptance
Upload packages now require staged browser/workflow acceptance and independent fresh artifact verification before promotion. Failed, missing or unavailable required checks block packaging and preserve the existing deploy; repair and rebuild are required. SQL-impacting changes require matching disposable MySQL execution; SQLite browser evidence is labelled separately. Fix the forbidden-Aces error screen found by acceptance: retain the denial, shared menu and account-only breadcrumb.
v398 · Restore the signed-in Home dashboard
Fix the missing Aces task-helper dependency that stopped Home rendering after the header when building campaign summaries. Preserve the existing dashboard, campaign cards and direct task destinations. Add a cold-entry dependency regression and exercise GM/player Home rendering across Aces phases.
v397 · Open the task named by the Aces navigation link
Make Prepare mission force open unit and pilot selection directly from the overview, Campaign menu and dashboard. Briefing links open briefing or route choices directly. Replace the Aces preparation task menu with a single next required step. Correction links return to readiness after saving and revalidate persisted records. Use the same preparation checks for readiness and the authorized Begin action, preserving source values, permissions, accounting and replay protections.
v396 · Follow the Aces player mission cycle
Connect briefing and route choices, group decisions, mission force preparation, results and played-mission history in the Campaign menu and overview. Show pending group decisions with readable subjects and vote counts. Move completed setup edits and decisions to a separate history. Make Mission history the default log, with individual saved mission results, objectives, damage and expenses. Keep accounting logs separate. Give players a read-only result-review path and preserve existing GM confirmation, voting, accounting and source disclosure protections.
v395 · Connect Aces inventory, record sheets and shopping
Make Unit inventory and Merchant permanent Campaign and overview destinations, with clear paths back from purchases and previews. Show all owned units in a compact inventory with saved pilots, condition, record sheets and individual details. Add sheet links to deployment and retain selections in the original tab. Allow viewing nondeployed unit trackers without enabling battle mutations. Preserve exact-source preview authorization and explicitly label undamaged/base-crew previews. Use one equipment-stage policy across UI and actions; retain after-sortie shopping and permit printed setup-time Omni configuration. Keep price, affordability, voting and repeat-save protections.
v394 · Narrative and meaningful Aces route choices
Add the source-reviewed Planetary Approach narrative and three descriptive landing choices before selecting the opening Scouring Sands sortie. Show the current completed sortie’s published outcome and applicable continuation context for later route decisions, including successful paper history. Preserve GM direct choices, player suggestions/votes and existing branch/accounting rules. Future briefings and unrevealed source pages remain private.
v393 · Shared-force totals and reciprocal GM approvals
Show PV and BV2 totals above the shared-force unit list for organizers and players, including committed forces. Allow explicit GM approval when Alpha Strike exceeds PV but fits BV2, alongside the existing Classic/Override BV2-over/PV-within exception. Both-limits-over remains rejected. Update live sortie totals, approval wording and starting funds for both directions. Preserve current source authority, exact-force approval, paper Warchests and repeat-credit protection.
v392 · GM approval for Aces BV2/PV differences
Show both force totals and let the GM explicitly accept an over-BV2 Aces starting force or sortie roster that fits its PV limit. Bind approval to the exact selected units, current sources, combat system and allowance; recheck it at commitment, application and starting play. Record the decision in campaign history. Approved starting forces use unused PV at 40 SP per PV for opening funds. Preserve recorded paper Warchests, ordinary accounting, authorization and repeat-credit protections.
v391 · Remove invented model gates and use supplied scenario sources
Remove the remaining Aces model-ownership checkbox and its proposal/application/starting-commitment gates. No replacement inventory restriction is added. Retain historical model notes and flags, while omitting synthetic ownership answers from new units and suggestions. Keep real source, budget, pilot and permission checks. Correct a scenario-emplacement catalog relationship so fixed OpFor uses its supplied published profile. Preserve saved identities, existing bindings/damage and explicit preparation adoption.
v390 · Remove unnecessary box-name paperwork
Remove the mandatory box set/ForcePack textbox from Basic Aces starting-unit entry. The printed rules do not require a product name for every unit. Retain one confirmation that these are owned player models separate from the Aces opposing force. Apply the same policy when adding units and committing the force. Preserve saved box notes, exact sources, budgets, pilot/unit counts, Advanced availability and existing accounting.
v389 · Reach every matching unit suggestion
Replace the unreachable 20-result cutoff with shared first/previous/page-number/next/last controls. A 43-result search offers all three result pages. Page Aces, company equipment and OpFor catalog suggestions in place, retaining unrelated entries. Preserve Aces query/type/page drafts and reset the page when the search changes. Show accurate ranges and totals, keep current-source checks on each requested page and provide explicit read retry without adding or buying a unit.