Post-Launch Hotfixes
Angels Fall First version 1.0 launched on July 11, 2026 with a surge of returning Early Access veterans and new players. Strangely Interactive was candid before release that hotfixes would follow — and the first wave arrived within days. The July 4, 2026 Steam post titled “More stability” documented dedicated-server crash fixes, several client-side crash resolutions, and silent background updates as the team scaled infrastructure for launch-week traffic. This guide summarizes confirmed post-launch patches, how to stay on the correct build version, and where to report new issues without confusing engine quirks with fresh regressions.
July 4 stability post (pre-launch final stretch)
Published four days before 1.0, the “More stability” announcement thanked the community for crash reports that helped isolate dedicated-server failures and a handful of client-side crashes. Developers noted servers were under heavy load from rising player counts and warned that silent game and server updates would roll frequently through launch week.
Marketing shorts highlighting AFF pillars over ten years of development were linked alongside the post — useful context for new players who want a two-minute overview before reading wiki guides.
Known fix categories
Dedicated-server crashes received priority — public lobbies depend on stable hosts, and early 1.0 traffic stressed backend systems. Client-side crash fixes targeted edge cases reported during beta tutorial testing and final QA.
Map collision and visual glitches from Update 29 hotfixes continued receiving touch-ups. Prestige, achievement, and player-stat read errors from June 2026 patches were already addressed pre-1.0 but remain relevant if you skipped months of updates.
Silent updates and version sync
Launch week often shipped unlisted client patches. If you disconnect with “versions out of sync,” restart Steam to grab the latest build. The server browser sorts mismatched versions to the bottom after Update 30 — join top-listed servers first.
Dedicated servers may reboot during hotfixes. Wait thirty seconds and requeue rather than assuming a ban or hardware fault.
What developers said to expect
Strangely Interactive promised a fuller named changelog and roadmap discussion on Discord and Steam after the launch dust settled. Treat this wiki page as a summary layer — pair it with the Version 1.0 Update guide for Update 30 content and Steam news for future named hotfix posts.
No gameplay expansion was announced alongside stability work. Balance tweaks may still land in hotfixes; re-check Weapons Tier List dates after any patch note mentioning gunplay.
Launch week status (July 11–20, 2026)
Version 1.0 shipped July 11 with a 10% Steam discount through Tuesday July 21, 2026 — the final day of the launch sale is tomorrow. Community coverage reported concurrent players passing 1,000 on July 12 with an all-time peak above 1,500 — modest versus AAA titles but a significant bump for this niche combined-arms indie.
As of July 20, no new named hotfix post appeared on Steam beyond the July 4 pre-launch stability note. Silent client and server updates during launch week remain possible — restart Steam if you see version mismatch errors.
Developers still owe a fuller public changelog and roadmap discussion per the 1.0 announcement. Monitor this page and Steam news for the first post-launch named patch.
Reporting new issues
Confirm you are on the latest build and test in a bot Territories lobby before posting. Performance stutter on modern CPUs is often settings-related — read Performance Fix before filing engine bug reports.
Discord remains the fastest channel for reproducible crashes with steps. Include map name, mode, player count, and whether dedicated or listen server hosted the match.
Official launch-week videos
Strangely Interactive released YouTube shorts covering infantry, vehicles, space combat, and capital boarding pillars ahead of 1.0. Embed below is the main pillar trailer; pair with the Tutorials guide for in-game onboarding after watching.