⟶ Sortie entries are populated from the Sortie Log tab.
Sortie Log
—
Pilot Cards
Force Profiles
⚔
Multi-Force Management
Save your current force data as a named profile, then switch between different forces freely. Each profile stores everything independently — roster, pilots, sorties, campaign log, warchest, and archives. Switching forces will prompt you to save any unsaved changes first.
Active: — changes are not automatically saved to the profile. Use Update Active Profile to sync.
Settings
Data Management
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.
Import Unit Roster from CSV
Import a Mekbay-format CSV to populate the Unit Roster. Columns used: chassis, model, TP, SZ, PV. All other columns are ignored.
Type mapping: BM → BattleMech CV → Vehicle CI → Infantry Platoon BA → Battle Armor Squad
Export / Import Data
Export your data as a JSON file to back it up or transfer it to another device. 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).
—Ready
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.
Campaign Journal
⚔ Save Force Profile
This will save a complete snapshot of your current force — all units, pilots, sorties, campaign log, and warchest — as a named profile you can return to at any time.