⟶ Balance is calculated cumulatively from starting warchest set in the Contract tab.
Repair & Rearm
⚙ Repair Costs
Unit / Description
Tons
Type
Cost (SP)
Total Repair Cost0 SP
🔧 Rearm Costs (10 SP/Ton)
Unit
Tons
Cost (SP)
Total Rearm Cost0 SP
▭ Reconfigure Omni Costs (Ton ÷ 4)
Unit
Tons
New Configuration
New BV
Cost (SP)
Total Reconfigure Cost0 SP
Total Repair, Rearm & Omni
0 SP
Unit Purchase & Sale
💰 Unit Purchase & Sale
Net SP0 SP
Total Unit Purchases & Sales
0 SP
Salvage Calculator
⚔ Salvage Value (BV ÷ 2)
Unit / Description
BV
Salvage SP
Claim
Total Salvage Value0 SP
Total Salvage0 SP
Contract Salvage %0%
Your Share0 SP
Personnel & Training
👥 Hire Personnel (100 SP each)
Description
Count
Cost (SP)
Total Hire Cost0 SP
❤ Heal Wounds (30 SP per wound)
Wounds
Cost (SP)
Total Heal Cost0 SP
⭐ Training
Description
Cost (SP)
Total Training Cost0 SP
Total Personnel & Training
0 SP
Force Record Sheet
Reputation+0Warchest0 SP
Pilot & Crew Roster
Type
Name
Rank
Callsign
Assigned Unit
G/P Skill
ADV
SPAs
Wounds
Status
Notes
No pilots on roster. Add a pilot to begin.
Deployment
No units deployed. Check the Deploy box on a formation row to stage a unit.
#
Unit / 'Mech
BV
Formation
Crew
Total Deployed BV0
BV Remaining—
Deployable BSP—
Cost Reference
Common Costs
Travel300 SP × Scale
Monthly Maintenance500 SP × Scale
Combat Bonus Pay
Broke Contract0
Unsuccessful50% Base Pay
Success100% Base Pay
All Objectives150% Base Pay
Mech Purchase & Sale
Purchase Unit (Classic)BV
Sell Repaired Unit (Classic)BV ÷ 2
Purchase Unit (Alpha Strike)PV × 40
Sell Repaired Unit (Alpha Strike)PV × 20
Repair Costs
Repair (Armor only)Ton ÷ 2
Repair (Structure/Crit)Ton × 2
Repair (Crippled)Ton × 3
Repair (Destroyed)Ton × 5
Rearm (Classic)10 SP/Ton
Rearm (Alpha Strike)20 SP/unit
Reconfigure OmniTon ÷ 4
Salvage
Salvage ValueBV ÷ 2
Rep (Reputation Points)
Noted in monthly ledger+/- Rep
Personnel & Training
Hire Personnel100 SP each
Heal Wounds30 SP / wound
TrainingSee Table Below
Training Activities
Unit Training Activities — Skill Improvements
Skill Improvement
Gunnery
Piloting
Skill (AS)
6 to 5 †
50
25
50
5 to 4
100
50
125
4 to 3
200
100
250
3 to 2
400
200
500
2 to 1
800
500
1,000
1 to 0
1,000
750
1,500
Special Pilot Ability = SPA Point Cost × 200
† Same cost applies to improving any higher Skill by one step (e.g. 7 to 6, etc.)
Force Training Activities
Create a New Formation10 SP × units in Formation
Change an Existing Formation5 SP × units in Formation
Command Training Activity
Learn First Special Command Ability250 SP
Learn Second Special Command Ability500 SP
Learn Third (or more) Special Command Ability750 SP
Replace a Special Command Ability250 SP
Settings
Game Mode
Sets the ruleset context for the sheet. BattleTech Classic — using BV (Battle Value).
Force Options
When checked, BSP is set to 0 and BV Available is increased by 500 per scale (500 / 1,000 / 1,500).
When checked, exposes a Number of Jumps field on the Contract tab. Travel cost becomes 50 + (50 × Jumps) instead of the flat 300 per scale.
× base repair cost
Applied to Repair Costs on the Support Costs tab when a unit's Tech Base is set to Clan or Mixed. Default is 1.5×. This is a house rule — not an official BattleTech rule.
Data is automatically saved to your browser's local storage. Use Save All Data to manually force a save. Clear All Data will permanently erase everything.
Export & Import
Export your contract data as a JSON file to back it up or transfer it. Import a previously exported file to restore your data.
GitHub Gist Sync
Sync your data to a private GitHub Gist so it's accessible across browsers and devices.
Requires a GitHub Personal Access Token with gist scope.
Generate one at github.com → Settings → Developer settings → Personal access tokens
(fine-grained: enable Gists read+write; or classic: enable gist scope).
Security Note
Your token is stored in localStorage on this device only and is never transmitted anywhere except directly to
api.github.com. Use a fine-grained token scoped only to Gists to minimise risk.
Revoke it from GitHub at any time.
Import Force from CSV
Upload a MekBay-style CSV file to populate formations on the Force Record tab. Each row becomes a unit entry.
Supported columns (case-insensitive): unit, tons, bv, status, omni, techbase, formation
The formation column is optional — if present, rows are grouped by its value into separate formations. If absent, all rows go into one formation.
No file chosen
Units & Campaigns
⚔
Multi-Unit & Campaign Management
Save your current unit as a named profile, then switch between different units and campaigns freely. Each profile stores everything independently — force record, pilots, formations, contracts, ledger, and all support data. Switching profiles will prompt you to save any unsaved changes first.
Active: — changes are not automatically saved to the profile. Use Update Active Profile to sync.
Campaign Journal
💾 Save Unit Profile
Give this profile a name — typically your unit name and campaign, e.g. "Iron Panthers — Hesperus Campaign".