Making Swarmcore mutations easier to read

A visual effect should answer one question

Mutation visuals are useful only when they help a player understand what changed. If every possible effect appears at the same time, the preview becomes exciting but unclear. A player may see rings, trails, sparks and shields and still not know which mutation is active. The goal is not to make the screen louder; it is to make the decision more readable.

For Swarmcore, that means each mutation needs a visual language that can be recognised in motion. Movement upgrades should feel different from defensive upgrades. Shot upgrades should alter the attack in a way that can be seen during the actual shot, not only in a menu preview.

The deck is not the same as the active build

One common source of confusion is the difference between preparing a mutation deck and seeing active effects in a match. A deck is a set of possible choices. A live run contains only the upgrades selected during that run. If the preview shows everything, it can accidentally teach the wrong rule.

The better direction is to show a clean selected-state preview, name the equipped mutation clearly and keep the full catalogue available for comparison. That gives the player a sense of possibility without claiming that every effect is currently active.

Readable combat matters more than decoration

Swarmcore already has many moving objects: swarm particles, rival cores, red-zone pressure, returning shots, labels, projectiles and pickups. Mutation visuals have to live inside that space. If an effect hides a shot or makes the core position unclear, it hurts the game even when it looks impressive in isolation.

Future improvements should therefore be judged in gameplay first. The right test is simple: can a player tell what happened, why it mattered and what they should do next?