Set the force and support allowances
Open Operations > Build OpFor, choose a scheduled mission, then Budget allocations. The mission saved player scales determine the combined scale; player selected BV is shown separately. Generation supports combined scales up to 200.
The force starts at 3,000 BV per scale, with a separate 500 BV support allowance per scale. Choose Scales using No Support to transfer 500 BV each from support to force. This is a GM enemy-budget choice and does not change player selections. Supported and No Support scales generate separate sets of up to three.
The mission track system chooses Revised Dobless when enabled; otherwise the campaign profile chooses Hinterlands or Draconis Reach. Budgets always scale verified category/weight proportions to the chosen allowance. Generating budgets never adds fixed book units. Alpha Strike converts the combined base allowance at BV / 30, rounded once; individual units spend published PV.
Mission force totals explicitly identifies No Battlefield Support chosen as Yes or No for each participating company, with Sitting out for scale zero. The total counts scales, not companies. New budget allocations default Scales using No Support to that saved player total; existing GM allocation choices remain unchanged and can be edited.
A roster checkbox changes the local BV preview immediately. OpFor continues to show the saved choice until Save track roster succeeds. Company and scheduled roster forms display a red Unsaved roster changes warning after edits, and warn before leaving. Save each company separately. A saved-status message identifies the persisted support choice; a failed save keeps the warning.
Expanded book-derived combinations
Budget variety selects book-derived combinations, or original Dobless rows when that system is enabled. Choose Book table family to restrict book draws to a faction group, or Any verified table family. Supported and No Support packets use only their exact scale. Book draws are uniform among fully valued combinations and do not reproduce printed dice probabilities; the modifier affects Dobless only.
Budget template sources lists book rows and expanded combinations from printed recursive rolls. Source pages are Hinterlands 138–149 and Draconis Reach 187–201. Printed smaller-scale combinations stay within their original faction and support choice. Verified vehicle shorthand relationships expand to exact cached variants. Budgets use base BV without crew skill adjustments. Missing values and unspecified veteran crews still require reviewed evidence; no unknown unit is omitted. Abstract air and artillery support use the separate support allowance.
Open a template to inspect its source page, constituent rolls, base BV and quantity. For unresolved lines, enter verified total base BV for the whole line, type and weight, and record the source/calculation. Reviews are saved for this mission and audited. Only fully valued combinations can generate pools. For upgrades from releases before 147, run Admin > Database updates. This corrects reviews with known base values, archives ambiguous old reviews for rechecking, and flags old allocations for regeneration. Regenerate flagged allocations before filling the force; existing units remain and need budget review. Completed mission history is preserved. If none fit the exact scale, family and support choice, review source values or choose another table family.
Allocation evidence preserves the selected book page and row, original unit values and original total, or the Dobless dice and modifier. Rescaling preserves the relative type/weight proportions while matching the force allowance. Regenerating archives the old allocation, preserves units and complications, and requires explicit reassignment of units formerly charged to base pools.
Spend allocations and add complications
When adding or editing an opposing unit, choose Charge this allocation. If it exceeds that pool, choose a base allocation to supply the excess. Transfer between pools moves a specified unspent amount from one base pool to another, preserving the total. Support and complications cannot donate allowance. Saved costs recalculate on every OpFor task; removing a unit releases spending.
Contract complications records extra BV/PV or a count of additional units, with the applicable contract source or ruling. Charge bonus units to that complication allowance, not a base pool. Complications are entered explicitly; contract prose is not automatically interpreted.
Support assets records a named asset, verified BV/PV cost and source against the separate support pool. Unit purchases cannot use this pool. Unassigned units, missing costs, overspent complications/support or stale scale block marking the force ready; locked player rosters remain required.
Base force spending is shown on every builder screen. Above the total scale allowance by more than 250 BV is yellow; more than 500 BV is red. Exactly +250 is normal and exactly +500 is yellow. These are advisory GM warnings, not purchase blocks. Alpha Strike compares PV overage at 30 BV/PV. Valid complication spending and support assets are excluded; unassigned unit costs count provisionally against the base total. Pool-balancing warnings remain visible separately.
Old generated allocations and historical forces are preserved. Regenerate allocations to apply the new exact-scale proportional budgets, then reassign existing base units. Scheduled tracks links to this builder; the old fixed-unit book generator no longer accepts submissions.
Generate units from faction RATs
Choose Mission opposition once (or use the linked contract opposition), then Fill budgets randomly. The generator automatically chooses the faction/year RATs and type/weight columns from the remaining pools. All faction / paint styles allocated to player companies are excluded in full. Only spare models from the remaining campaign-linked GM painted stock are eligible after individual model assignments and pending chassis reservations. Every draw counts existing and newly added units against the same chassis total across all variants and budget pools; repeated generation cannot exceed it. Unpainted and unprinted models are excluded; disabled inventory limits do not bypass this rule.
The generator makes weighted MegaMek draws among affordable, verified, available models. It stops when no matching stock fits, at 100 unsuccessful table selections per pool, or at 200 saved units. Unspent budget is reported; it never silently borrows between pools. VTOL/APC-specific pools still need manual review when movement/transport metadata is not verified.
Completed missions and missions whose unit reporting has begun are read-only. Budget and force changes are audited and use the existing protected GM save workflow.
Lock, change or reroll generated units
Open the selected Track menu > Generated units after Fill budgets randomly. Manually selected or entered units are kept separate and are never included in bulk rerolls.
With JavaScript enabled, generated-unit locks, individual and bulk rerolls and Change variant update in place, preserving scroll and other unsaved visible fields. Progress blocks overlapping changes; errors remain beside the submitted form. Reload after a connection or refresh failure before retrying. Without JavaScript, normal submissions remain available. Lock unit protects that generated entry. Reroll unit or Reroll all unlocked generated units draws a different eligible variant using the mission opposition and year, retaining type, weight, budget assignments, unit identity and purchased crew upgrades. The old slot is released during availability checks; all other saved units still consume painted capacity.
Rerolls use only spare eligible non-player painted models and fit the current allocation plus its selected spillover allowance. No fitting replacement leaves the original unit unchanged with an explanation. Assign a current budget first after regenerating allocations.
Change variant offers cached same-chassis, same-weight designs introduced by the mission year. These choices need not be listed in the faction RAT. Save rechecks painted stock and uses the new base cost. Review budget warnings and Assign unit budgets if the new variant needs spillover. Locked entries must be unlocked first.
Completed missions and missions in reporting remain read-only. Locks and replacements are audited.