⚜ SteamCozy

Home / News / Cepheus Protocol

2026.8.21.1 Experimental Patch Notes & August Development Update

Cepheus Protocol · Community Announcements · August 21, 2026

Read the original on Steam ↗
[carousel autoadvance="true"]

THE BAY AREA IS COLLAPSING. The virus is loose across the peninsula. Flashpoints are erupting across the region as entire districts fall into chaos and infected swarms push deeper into civilian zones. CERC forces are already in the field.

Embedded military reporters and frontline operators are transmitting battlefield coverage directly from active operations. The images you are about to see were captured during recent combat deployments across the region.

These transmissions come directly from the front. The battle for the Bay Area continues.

Experimental Update Highlights

Minimap Overhaul

More control and more information directly from the Minimap. The Minimap has received one of its largest usability passes yet, with mouse scroll wheel zoom support, rotation + Q& E support, bookmarks, improved panning, Its size was improved by 20%, improved damage alerts, and additional multiplayer improvements for planning on the map.

Bookmarks now preserve the Minimap's current perspective, including zoom, rotation, and panning, allowing you to quickly jump between different areas of an operation.

Selection, Abilities & Active Weapon Feedback

Better feedback for exactly who and what you're commanding. When multiple units are selected, units corresponding to the currently selected ability group are now highlighted in the Details Panel. Weapon displays also highlight the weapon currently equipped by a unit, making weapon swaps immediately visible without having to infer the unit's current state and go looking for them. Ability cycling has also been moved to TAB, making it faster to work through larger selections.

Fog of War, Vision & Late-Game Performance

A significant amount of this week's engineering has gone toward making vision more reliable under heavy simulation load. We've continued profiling and optimizing the VisionGrid, reducing memory operations, improving deferred processing, prioritizing relevant sight results, and preventing older results from becoming stale. This work also addresses cases where low framerates or extremely heavy late-game waves could cause units to detect enemies late, ignore them, or seemingly have infected disappear from vision. This remains an active area of development, but the changes in this build are another meaningful step forward.

Combat & AI Reliability

A wide range of combat and AI behaviors have been tightened up this week. Fire-mode changes now immediately cause units and independent weapons to reevaluate valid targets, patrol behavior has received additional reliability fixes, combat facing has been improved, garrison movement has been cleaned up, and the Stun and Enrage systems have been reworked to interact more predictably.

Patch Notes for 2026.8.21.1 (Experimental)

Minimap

Unit Selection, Commands, and Interface

Fog of War, Vision, and Performance

Combat, Targeting, and Infected

Movement, Patrols, and Garrison Behavior

Helicopters

Structures, Construction, and Blueprints

Recruitment and CERC

Civilians

Audio and Battlefield Feedback

Vehicles and Visuals

Steam Workshop and Mod Uploader

Save / Load and Stability

Development Update — Finishing the Foundation

Today's Experimental patch is only part of what we've been working on over the last week. A lot of our time has also gone into watching people play, reading feedback and reviews, looking through reports, and profiling what happens as matches become larger and more complicated. That process has been useful because the things that affect how the game feels aren't always the big headline features. Sometimes it's a performance spike late in a match, a pathfinding edge case, or a system that is technically working but isn't giving you enough feedback to understand what it's doing. Those smaller points of friction add up, and this phase of development has increasingly become about finding and cleaning them up. Through the rest of August, that's where much of our attention is going. We want to finish the work already in motion, get the existing systems into a good place, and make sure we're starting Escalation from a game that feels stable and dependable rather than carrying a list of known problems forward with us.

Where Things Stand

Several of the larger systems we've talked about recently are now complete.

We've also been spending more time on the smaller usability improvements that are easy to overlook on a feature list but make a noticeable difference during a match. Cycling through units and abilities, clearly showing the active weapon, improving selection feedback, and making the Minimap easier to work with are all examples of that. A lot of these changes come directly from seeing where players hesitate or have to work harder than they should to understand what the game is telling them. That's useful feedback for us, because sometimes the solution isn't another major system. Sometimes the game simply needs to communicate the systems it already has better.

GPU Fog of War — Delayed

The remaining GPU Fog of War work is taking longer than we originally expected, so we want to be clear about where that stands. There are two sides to the work. The visual portion of Fog of War is being moved over to the GPU so we can reduce the amount of CPU time spent presenting it. Underneath that, however, the actual trace and line-of-sight work is still heavily CPU dependent. That distinction has become increasingly important while profiling the mid-to-late game. As infected populations, unit counts, and the rest of the simulation grow, we're still seeing situations where CPU load can spike and vision processing begins to fall behind. This week's VisionGrid work is aimed directly at that problem. We've reduced memory operations, improved how deferred sight results are handled, prioritized nearby results, and added better controls for situations where more vision work is being generated than the system can process immediately. Those changes have also helped with cases where infected could appear late, disappear from sight, or be ignored during particularly heavy waves. The GPU visual migration is still happening, but finishing that portion alone wouldn't address the larger performance problem. We're continuing to profile both sides together so that when we call this work complete, it has actually improved the situations we're trying to fix.

Learning From Legacy

One lesson we took from Legacy is that it's very easy to get caught up in shipping the next feature before the previous one has had enough time to settle. We'd get something working, move onto the next system, discover an edge case in the previous one, jump back to fix it, and gradually end up with several interconnected systems all needing another pass at the same time. That made development harder to manage and made it easier for smaller issues to stay around longer than they should have. We're trying to handle this phase differently. Rather than immediately stacking the next large feature on top, we're giving the systems already in the game the time they need for profiling, polish, usability work, and bug fixing. Escalation is going to introduce plenty of new variables on its own, so this is the right time to get the current baseline into the best shape we can.

CERC OPS — Planning & Synchronization

CERC OPS is also moving into its next stage of development. This week's build contains an early implementation of streaming Minimap information between CERC OPS and the game, and we're starting to build on that work with synchronization between connected clients. The immediate use case is SP/Coop planning. We want information created during planning to be shared between players instead of living only on one client's machine. Once that works cleanly at the game level, the same foundation can extend outward to CERC OPS. The long-term direction is a two-way flow between the game clients, server, and CERC OPS, so plans can be created, updated, and reflected across the different parts of the system.

Dr. Kira & An Official In-Game Tutorial

We're also showing off Dr. Kira's new model. Kira is second-in-command of CERC, and she'll also be the character guiding players through the mission-based tutorial we're beginning to build.

Recent reviews, feedback, and simply watching people play have made it clear that Cepheus Protocol needs a better way to teach its mechanics inside the game itself. The community has done a lot to fill that gap through Steam guides, videos, and other player-made resources, and those have been genuinely helpful. At the same time, we want the game itself to do a better job of giving new players the information they need to get started. Many of Cepheus Protocol's mechanics become fairly intuitive once you've seen them in action, but getting to that point shouldn't depend on leaving the game and searching for an explanation. There's also a practical side to this: not everybody wants to stop playing, open a guide, or watch a video before continuing. Some players would rather learn by doing, so that's an experience we want to support more directly. The first version will be a basic mission-based tutorial with Kira providing guidance as the player moves through objectives and encounters different systems. It isn't intended to replace the deeper guides, tutorials, and strategies the community has built. The goal is to give players a solid introduction to the fundamentals inside the game, then let them explore the deeper systems naturally from there.

Main Menu & UI Cleanup

The Main Menu and the remaining UI are also getting another pass. Some of the new Server Browser assets are already being prepared internally, although they're not active in the current interface yet. This work is partly visual, but it's also about readability and consistency. The same questions we're asking elsewhere in the game apply here too: is the important information obvious, does the interface respond the way the player expects, and can somebody understand what they need without having to hunt for it? The Minimap changes were a good example of how much difference that kind of cleanup can make, and we want to carry the same thinking through the rest of the UI.

Helping Report Issues & Bugs

While we're working through this cleanup phase, detailed reports from players are especially useful. If you're still seeing performance drops, pathfinding problems, strange unit behavior, UI issues, multiplayer problems, or anything else that consistently feels wrong, please send it our way through Discord or the Steam Community. Videos, screenshots, GIFs, save files, and reproduction steps are all extremely helpful because they let us see the exact conditions around an issue instead of trying to recreate it from a description alone. Even something that looks minor on the surface can sometimes expose a larger underlying problem once we can reproduce it reliably. The more of those issues we can identify and resolve now, the cleaner the game will be as we move into the next phase of development.

The Road to Escalation

The standard we're aiming for before we move into Escalation isn't that Cepheus Protocol somehow becomes completely bug-free. What we want is for the existing game to feel stable and predictable enough that we can trust what we're working from. That matters because Escalation itself is going to involve a lot of R&D. We'll be updating parts of the engine, evaluating newer engine features, testing navigation improvements, and prototyping systems that may behave very differently once they're dealing with the number of actors Cepheus Protocol can put on screen. Building climbing is one example. Before that can become a production feature, we need to find out how well the available navigation systems handle it, how predictable the behavior is, and whether it remains practical when scaled up. Some of what we need may already be available through newer engine systems, some of it may require extension, and some of it may ultimately need to be engineered specifically for the game. That's the part of Escalation we're looking forward to getting into. Getting the current game into a dependable state beforehand means we'll have a much clearer picture of how those experiments are affecting the simulation and where the next round of engineering needs to focus.

Through the End of August

That's the general plan for the remainder of August. We'll continue shipping fixes and improvements while we finish the Fog of War profiling, expand CERC OPS synchronization, start the in-game tutorial work, reskin the Main Menu, and clean up the remaining UI. Today's Experimental patch is part of that process rather than something separate from it. A lot of the work in this update comes directly from the same testing, profiling, and player feedback that's guiding what we're working on next. Once those remaining pieces are where we want them, we can turn our attention toward Escalation and the R&D that comes with it. For now, we're going to keep working through what is already in front of us and give these systems the time they need.

Community Workshop Spotlight

The Steam Workshop continues to grow alongside the Blueprint, Squad Preset, and modding tools. This week's update also makes it easier for creators to bring an existing Workshop project back into the Cepheus Protocol Mod Uploader, update it, and publish subsequent versions. Here are a few creations from the community worth checking out:

[dynamiclink href="https://steamcommunity.com/sharedfiles/filedetails/?id=3783404703"][dynamiclink href="https://steamcommunity.com/sharedfiles/filedetails/?id=3786782849"][dynamiclink href="https://steamcommunity.com/sharedfiles/filedetails/?id=3784826542"]Keep sharing what you're building. We'll continue looking through the Workshop for creations to feature in future updates and CERC HQ discussions.

Last CERC HQ Episode Summary

[dynamiclink href="https://youtu.be/n07JsESAfpA"]Last week's CERC HQ focused heavily on the systems that have been coming together over the last few updates, including reusable base blueprints, battlefield control, Fog of War work, patrol improvements, and the ongoing performance push.

Base Blueprints were one of the larger topics, covering the ability to capture layouts, save them locally, share them with friends, and distribute them through the Steam Workshop. We also looked at improvements to construction behavior and the broader work surrounding reusable squad and operational presets.

Fog of War and vision were another major part of the discussion, including the ongoing effort to move more of the visual workload onto the GPU while continuing to profile the CPU-side line-of-sight and trace work. We also covered vehicle patrols, formation controls, weapon switching, vehicle destruction, ammunition resupply behavior, radio fixes, and optimizations for units outside the player's immediate view.

We also spent time looking ahead at Escalation and some of the R&D that will come with it, including stronger infected progression, new variants, specialized lieutenants, and larger navigation and traversal experiments.

Weekly CERC HQ's

When: LIVE SATURDAYS at 7:00 PM Eastern

Another week. Another deployment. Another look behind the curtain at the continuing development of Cepheus Protocol.

CERC HQ is our weekly development podcast covering the latest development progress, current technical challenges, upcoming roadmap work, community feedback, and the systems currently moving through production.

Where to Watch

Watch CERC HQ on YouTube Join the Discord Server Visit the Steam Page

Missed a Stream? No Worries!

Watch the CERC HQ Archive Thank you to everyone continuing to test Experimental, report issues, send save files, record videos, capture screenshots and GIFs, participate in performance testing, create Workshop content, and provide detailed feedback. It gives us a much better picture of where the rough edges still are and where our attention is most useful next.

Cepheus Protocol MORE ON STEAMCOZYCepheus Protocol 79.0% positive · 3,032 reviews Price tracking · player charts · similar games →

This announcement was written and published by the developers/publisher of Cepheus Protocol on Steam; it is mirrored here unedited for readability, with full credit and a link to the original above. © the respective rights holders. Rights holder and want it removed? Email us — we take it down promptly.