Build a useful campaign snapshot
- 01
Write one current goal
Use an outcome that can change a decision, such as completing a ship module, supporting one faction until a reward unlocks, or rebuilding a lost loadout.
- 02
Describe the dependable kit
Record weapons, ammunition, armor channels, medical supplies, and the fallback you can actually replace. This note is for decision consistency, not inventory simulation.
- 03
Copy live upgrade requirements
Create one target per ship upgrade and enter the exact material names and quantities visible in the current game interface. Mark progress after each extraction.
- 04
Export before changing browsers
Browser-local state does not automatically follow you to another device or survive every privacy cleanup. Download a JSON backup after meaningful progress.
OFFICIAL GAMEPLAYWhat belongs in the campaign record
| Field | Useful example | Decision it supports |
|---|---|---|
| Current goal | Finish Clone Bay upgrade | What counts as progress today |
| Faction focus | Support AnCom, avoid strengthening rival | Which contracts are strategically acceptable |
| Common loadout | Piercing primary, cut fallback, cold protection | Whether a mission briefing reflects real equipment |
| Ship progress | Navigation complete, medical branch blocked | Which module should receive scarce materials |
| Upgrade target | Name plus required and owned quantities | Where the route planner should send the next run |
How local saving and backup work
Every edit is serialized under a versioned storage key. When the page opens, fields are validated individually; malformed values fall back conservatively instead of crashing the workspace. Unknown future item names remain in backups so a dataset gap does not erase the player's note.
Reset requires a second explicit click because it removes the local campaign record. Import accepts JSON text from a selected file and runs it through the same validator. No imported content is executed, and no state leaves the browser during save, import, or route calculation.
FAQ
Frequently asked questions
Where is My Campaign data stored?
It is stored in this browser's localStorage under a versioned Quasimorph key. Use Export backup before clearing browser data or moving to another device.
Why do I enter upgrade requirements manually?
The current game interface is the safest source for patch-sensitive requirements. Manual entry avoids inventing recipes and makes the route planner explain exactly which player-provided quantities it used.
Research trail
Sources and further reading
Current HIS Magnum departments, module effects, requirements, and progression paths.
02 · OfficialQuasimorph 1.0 and 1.0.1 NotesOfficial mission progression, difficulty, economy, UI, class, mercenary, implant, and balance changes.
03 · CommunityQuasimorph item-category community researchCommunity evidence connecting item categories with station types, used as probabilistic route guidance rather than a guaranteed drop table.