Outpost Zero development updates

Expanded public Field Manual and lighter page media

The public game pages now document mission Power, survivor progression, Base effects, crafting requirements, transport maintenance and Base Defense in substantially more detail. Large public hero images are served in WebP to reduce transfer size while original source files remain available as compatibility backups.

• Detailed system references added to every public Game section.
• Beginner guide expanded into a full progression route.
• FAQ expanded with tactical combat, vehicles, rarity and virtual-resource answers.
• AdSense ownership meta tag and existing ads.txt publisher declaration kept available without loading ads before approval.

Account flow, privacy controls and measurement cleanup

Registration and privacy handling were tightened before paid traffic testing. Optional analytics and advertising measurement remain separate from essential gameplay storage, and tracking tags are not loaded until the relevant choice is made.

• Privacy, Terms and Cookie documentation updated.
• Registration measurement moved to the successful account-creation event.
• First-mission measurement moved to the actual resolved mission result instead of the start button.
• AdSense delivery remains disabled until the publisher account and required consent configuration are ready.

Mission progression rebalanced for up to six deployed survivors

The Required Power curve was rebuilt around a progression from small early teams to full late-game squads. Recommended team size now rises from two survivors in the opening mission to six in the hardest current operations.

• Perimeter Sweep begins at 110 Required Power with a two-survivor recommendation.
• Mid-game missions transition through four- and five-person teams.
• Warden K-9, The Hollow, Signal Vault and The Choir are balanced around six-person deployments.
• Session storage was isolated and extended to reduce unexpected logouts on shared hosting.

See the complete current Required Power table →

Scout combat states tied to real battle events

Scout presentation was synchronized with saved combat events so movement, attacks and damage states match what actually happens in both manual combat and Auto Battle.

• Walk state is used on real movement events.
• Normal attacks and Aimed Shot use distinct action states.
• Hit and knockdown/death states respond to server damage results.
• The same event stream is used in manual and automatic battle resolution.

World Event cards made more compact and missing event art restored

The World Map event list was tightened so more active signals fit into the visible area without removing reward, specialist or risk information. Missing Mutant Nest event art was also restored.