Testing Spectrium Boss Phases in Botwars Ascendance

One of the most important parts of building Botwars Ascendance is making sure our boss encounters feel dangerous, dynamic, and genuinely memorable. In a recent testing session, I focused on one of the systems that will have a major impact on that experience: enemy boss configuration, and more specifically, how boss phases and combat waves are programmed and triggered during an encounter.

At the center of this work is the World Builder, our bespoke internal tool for configuring play zones, NPC behavior, and mission logic across the game. It gives us a high level of control over how encounters are created and tuned. When it comes to Spectrium bosses, I can use the World Builder to define exactly where a boss is found, the area it patrols, what kind of player activity generates aggro, which boss variant is active, and how powerful that boss should be in the context of the mission or zone.

That’s already a powerful foundation, but the most exciting part of this test was the phase system.

We’ve now implemented the ability to add unlimited boss waves or phases, with each phase triggered by player behavior or by the boss reaching specific shield or health thresholds. That means a boss encounter is no longer just a static fight. It can evolve in response to what the player is doing and how the battle is progressing.

For example, I can set up logic such as:

When the boss shield reaches 90%, trigger wave one.
When the shield drops to zero, trigger wave two.
When the boss health reaches 50%, trigger wave three.

That kind of sequencing gives us much more control over pacing, escalation, and surprise. Instead of a boss simply absorbing damage until it is destroyed, the encounter can shift in tone and intensity at key moments. A fight can begin as a patrol engagement, then transition into a reinforcement-heavy battle, and then become a more aggressive final-phase showdown once the boss is under real pressure.

What makes this system especially flexible is that each wave can completely redefine how the boss behaves. A phase can change the boss’s movement or patrol behavior, alter its attack profile, deploy smaller enemy fighters, or send in salvage vessels. In other words, each stage of the battle can feel like a distinct tactical problem for the player to solve.

For this test, I configured four separate phases, each with its own parameters, and then recorded the encounter so I could review the full battle from start to finish. The goal was simple: verify that the boss responded correctly to the conditions set in the World Builder, and confirm that the phase transitions happened exactly when intended.

The result was a 99% successful test, which is an excellent outcome for a system with this much layered logic.

During the encounter, I was able to confirm that the boss behavior changed as configured and that the encounter flow respected the thresholds I had defined. Most importantly, the boss successfully deployed the specified smaller fighters, known in the game as Centurians, at the correct moments in the battle. Those Centurians also appeared with the exact levels and power settings that had been assigned to them, which was a key part of the validation process.

That may sound like a technical detail, but it is a big deal from both a gameplay and production standpoint. It means the system is not only triggering waves at the right points, but also correctly passing through the supporting combat data that determines how dangerous those reinforcements actually are. In practical terms, it means we can build encounters that are much more deliberate, much more dramatic, and much more scalable.

It also opens the door to a wide range of encounter design possibilities across the wider game. Different Spectrium bosses can now be tuned not just by raw power, but by structure. One boss might rely on attrition and reinforcement pressure. Another might become more aggressive as its defenses fail. Another could use salvage vessel deployment to create additional battlefield complications. Because the system is modular, we can create a broad variety of boss experiences without having to reinvent the underlying logic every time.

From a player perspective, that should translate into encounters that feel more alive and less predictable. A boss battle in Botwars Ascendance is not meant to be a damage sponge with a bigger health bar. It should feel like a staged conflict with rising stakes, shifting threats, and moments that force players to adapt.

This test was an important step toward that goal.

Even better, recording the battle gave me a clean way to verify not just whether the system worked, but how it felt in motion. Timing matters in boss design. It’s one thing for a trigger to fire correctly in a technical sense; it’s another for the transition to happen at the right emotional and gameplay moment. Watching the encounter back helps confirm whether a phase change feels earned, whether reinforcements arrive with enough impact, and whether the pacing maintains tension throughout the fight.

At this stage, I’m very encouraged by the result. A 99% success rate tells me that the core framework is doing what it needs to do, and that the World Builder is giving us the level of encounter control we need to create more compelling battles. It also gives us a strong base for more advanced testing, including additional phase combinations, more complex trigger logic, and even more varied boss support behavior.

Boss encounters are a major part of how players will experience danger, progression, and payoff in Botwars Ascendance. This test showed that we are moving in the right direction. The underlying systems are becoming more robust, the fights are becoming more expressive, and the tools we are building are making it easier to turn design ideas into playable combat scenarios.

There is still more to refine, as there always is in development, but this was a strong result and a meaningful milestone. The Spectrium bosses are becoming smarter, more reactive, and far more capable of delivering the kind of escalating encounters we want players to remember.

‍