Patch Notes 0.9.3 — Ship Balance, Economy Fixes, and Combat Corrections

Update 0.9.3 is deploying today. This is a focused patch — no new content, nothing that requires a full download. It addresses a set of balance issues that emerged in the final weeks of closed beta, a significant combat calculation bug that was affecting large-fleet engagements, and a few economy adjustments driven by storage bottleneck data we collected post-0.9.2.

Patch notes are detailed below. For the short version: if you fly a Void Stalker, read the ship balance section. If you run large alliances, read the combat section.

---

Ship Balance

Void Stalker — Speed Reduction (–8%)

The Void Stalker has been the dominant Void Syndicate strike ship since the second week of closed beta. Its kill rate in solo PvP engagements was running 34% above the intended tier-for-tier parity against equivalent-investment ships from other factions. The root cause was not its weapons or armour — both are within expected parameters — but its movement speed, which made it effectively unkillable in the retreat scenario.

A Void Stalker at full speed could disengage from most combat encounters before the retreat threshold triggered, absorbing minimal losses on failed raids and making high-risk PvP nearly cost-free for skilled pilots. This is a problem not because aggressive playstyles shouldn't be rewarded, but because risk-free aggression removes the core economic pressure that makes combat decisions meaningful.

Change: Base movement speed reduced from 2.8 sectors/tick to 2.576 sectors/tick (–8%). Warp capability and engagement range are unchanged. The Stalker remains the fastest combat ship in the Syndicate roster — this adjustment narrows the gap between it and the next-fastest vessel rather than changing its role.

Expected outcome: Void Stalker pilots will see slightly higher average losses on failed raids. Successful raids are unaffected. PvP matchups against Dominion Cruisers and Frontier Interceptors should now be closer to the intended 50/50 at equal investment.

Frigate Mk.I — Hull Integrity Buff (+15%)

The Frigate Mk.I has been underperforming as a frontline ship in mid-game fleet compositions for most of beta. Its role — durable forward presence that absorbs fire while heavier ships engage — was not translating in practice because hull integrity degraded too quickly under concentrated fire to allow the tactical layer time to respond.

Change: Hull integrity increased from 1,400 base to 1,610 base (+15%). Repair costs scale with the new HP value, so this also increases repair cost slightly — approximately 120 additional Metal per full repair cycle. Armour rating and weapon loadout are unchanged.

Expected outcome: Frigate Mk.I becomes a viable frontline hull at fleet compositions of 10+ ships. The increased survivability gives commanders more decision window during engagements rather than losing frigates in the first two combat rounds before the battle develops.

Note: This change applies to newly constructed Frigate Mk.I hulls. Existing ships will receive the HP increase applied to their current integrity percentage — if your Frigate is at 60% HP, it will be at 60% of the new value after the patch, not a flat addition.

---

Economy

Metal Storage Cap — Tier 3-5 Building Increase

The most-reported economy frustration in beta was storage overflow blocking refinery throughput. The Refinery cap system — introduced to prevent Metal oversupply — works correctly. The storage cap system was unnecessarily aggressive at mid-game building tiers, causing players with well-developed Tier 3-5 storage infrastructure to still hit the raw ore overflow threshold.

The data from 11 weeks of beta shows that players who hit the storage cap before Tier 3 buildings are ready lose an average of 2.4 days of effective Metal income. This is not an intended friction — it's a quality-of-life problem that the original storage numbers created.

Changes:

Tier 1 and Tier 2 storage caps are unchanged. The throughput bottleneck at Refinery level (1,800 Metal/hour per Refinery) is also unchanged — we are adjusting storage headroom, not production speed.

The effect on Metal supply: marginal increase in available Metal for players with developed infrastructure. The refinery throughput remains the binding constraint for high-production operations, so this change does not reintroduce the Metal oversupply risk from alpha.

Market Tax Rate — No Change

We've seen discussion in the beta forums suggesting the 5% market transaction fee would be reduced. It will not be reduced in this patch. The 5% rate is performing as intended — it creates meaningful friction on high-frequency market trading without making occasional trades uneconomical. We'll revisit the rate at the 60-day post-launch mark with live economic data, but there is no current plan to change it.

---

Combat

Fleet Power Calculation — Stack Overflow Fix

This is the most significant fix in the patch.

During beta, fleet engagements involving 500 or more ships on a single side were producing incorrect power calculation results. Specifically: the fleet power calculation function used a recursive algorithm to sum module contributions across all ships in the fleet. At fleet sizes above approximately 480 ships, the recursion depth exceeded the stack limit, triggering a stack overflow that caused the calculation to return a corrupted value — sometimes absurdly high, sometimes zero.

The result was engagements where a 600-ship fleet was calculated as having effectively no power, losing to a 50-ship fleet. This affected a small number of large-alliance engagements in the final two weeks of beta and produced several outcomes that were reported (correctly) as exploits. They were not exploits — they were a calculation error that happened to be triggerable by fleet size.

Fix: The fleet power calculation has been rewritten as an iterative algorithm. There is no longer a stack-depth limitation on fleet size. We have tested the fix at simulated fleet sizes up to 2,000 ships with correct results across all test cases.

We reviewed the beta engagement logs to identify battles that were materially affected by this bug. Twelve engagements had outcomes inconsistent with a correct calculation. We cannot retroactively alter beta outcomes, but commanders involved have been notified and the incident has been noted in their beta records.

Going forward: Fleet power calculation at any fleet size should now produce correct results. If you observe combat outcomes that appear inconsistent with your fleet composition, please report them through the Bug Reports channel with your engagement ID — we want to verify the fix is holding in live conditions.

---

Territory

Siege Timer Extension — Tier 4-5 Sectors

Tier 4 and Tier 5 sectors are the highest-value territorial assets in the game. They contain the densest resource deposits, the best strategic positions, and in many cases the most developed infrastructure of their owners. The siege mechanic for these sectors was not appropriately reflecting their value.

The previous 2-hour Breach timer for Tier 4-5 sectors allowed a coordinated assault team to complete a capture before the defending alliance could organise a meaningful response across time zones. Beta data: 67% of Tier 4-5 sector captures completed without the defending alliance successfully fielding a counter-force. Only 23% of those captures were attempted in the sector owner's active playing hours. The implication: most high-tier sector captures were timezone raids — attacks timed specifically to occur when defenders were asleep, with the siege completing before anyone woke up.

We don't want to make timezone raiding impossible — it's a legitimate strategic tool. But a 2-hour window for the defender to respond is too short for a tier of content where the resource stakes justify mobilising an alliance.

Change: Siege Breach timer for Tier 4 sectors extended from 2 hours to 3 hours. Tier 5 sectors extended from 2 hours to 3 hours. Tier 1-3 timers are unchanged.

The additional hour gives defenders in adjacent or overlapping timezones a realistic window to redirect fleets, recall offline commanders, and organise a counter-assault. Attackers will need to sustain their commitment for longer, which increases the resource cost of a high-tier siege and makes the risk/reward calculation more symmetric.

---

Additional Fixes

- Scout cloaking persistence: Scouts were occasionally losing cloak status after a failed sensor sweep. Fixed. Cloak now persists through failed sweeps as intended.

- Alliance treasury display: Treasury balance was displaying incorrectly in the Alliance Panel when the balance exceeded 10 million credits. Display now correctly formats large credit amounts. No credits were lost — this was a display formatting bug only.

- Nebula sector fog-of-war: Nebula sectors were not correctly blocking long-range sensor scans in some edge-case fleet positions. Fixed. Nebula sectors now correctly block all non-short-range sensor capability as intended.

- Trade route fuel calculation: Fuel cost per sector was calculating correctly for direct routes but producing slightly incorrect values on routes with 3+ waypoints. Fixed. If you have active trade routes with waypoints, recheck the profitability estimate — it may have changed marginally.

---

What's Coming in 0.9.4

We're not announcing 0.9.4 content today, but we can confirm: the next patch will include the first iteration of Faction War mechanics, which have been in design review since beta close. More detail when the design is finalised.

As always, feedback goes to the patch feedback thread in the official Discord. If you find something that looks wrong, tell us — the fleet power bug persisted for two weeks in beta because the affected commanders assumed it was intentional. It was not. Report strange things.

— Starforge Dev Team