SupplyBudget

SupplyBudget - Design Notes

Purpose

The vanilla game gives each mission its own independent supply cap. This means you can max-spend on every single mission with no consequences. SupplyBudget replaces this with a shared pool for the entire operation, forcing the player to budget across missions. Overspend early = less later.

Core Formula

Pool = baseMissionSupply numberOfPlayableMissions

• []baseMissionSupply: the vanilla per-mission supply cap (e.g., 1070)

  []numberOfPlayableMissions: unique m_LayerIdx values across op.m_Missions. Parallel/branching missions share the same layer index, so this gives the actual number of missions the player plays. Example: 5 total missions, missions 2/3/4 are parallel (same layer) → 3 unique layers → pool = 1070 3 = 3210.

The full pool is available from mission 1. The player decides how to distribute it.

Within an Operation

• []Pool is set once at the start of the operation (all upfront)

  []Each mission launch deducts the deployed cost from the pool

  []Remaining pool carries forward to the next mission within the same operation

  []Minimum per-mission budget (setting, default 100) ensures the player always has something to deploy and doesn't get soft-locked.

Between Operations

• []NO carryover. Each operation gets a fresh pool.

  Installation

  • []Install MelonLoader to your game folder (instructions)

  • Extract the zip contents into the Mods folder inside your game folder