Team Builder

Two competitor sites advertise an optimizer for this game. Open either one and it is a prose article with a screenshot. Nothing runs. That is worth naming, because it sets a low bar and this tool only needs to clear one thing: it has to actually compute something, and what it computes has to be true.

So it checks exactly three things, and it is honest about the limits of each. It checks whether your six units contain a confirmed Synchro pair, and it lights up both units when they do. It counts how many of the seven elements your team covers, using only elements a source has actually stated. And it looks at your roles, warning you when your team has grown to four or more units without a single support in it.

What it deliberately does not do is give you a damage number. Every instinct in tool design says to put a big confident figure at the top, because a big number feels like an answer and a warning feels like a nag. But we have no verified stat table for this roster. Producing a DPS score would mean inventing base damage values for 115 units and multiplying them together into something that looks authoritative and means nothing. A twelve-year-old would then spend real shards on the basis of it. The absence of that number is the most considered decision in this tool.

Synchro arrived with Update 4.0 and it is the single most misunderstood thing in the game right now, because people pattern match it to synergy systems from other tower defense games. In most of those, synergy is emergent: three fire units, get a fire bonus. Two units from the same franchise, get a franchise bonus. The system generalises, so you can reason your way to it.

Synchro does not work that way. It is a hard-coded list of specific two-unit pairs. If your two units are on the list, the pair activates. If they are not, nothing happens, no matter how much sense the combination makes thematically. Two Marvel parodies do not trigger anything for being Marvel parodies. Two S+ DPS units do not trigger anything for being strong.

There are also two kinds of Synchro pair, and the difference is not cosmetic. A Fuse pair merges the two units into a single new unit. A Clash pair leaves both units standing on the board and gives them a combo attack together. That changes the slot maths in a way people miss: a Fuse pair spends two of your six slots and gives you back one body, so you are trading board presence for whatever the merged unit turns out to be. A Clash pair keeps both bodies and stacks a combo on top. Neither is strictly better, but committing to a Fuse without noticing you just dropped to five effective units is a real way to lose a run.

This has a real consequence for how you build, and it is the reason the builder exists. You cannot deduce your Synchro pairs. You have to look them up, and until recently there was nowhere to look them up, because the game does not surface the pair list and the community board that would traditionally hold it is discontinued. So the honest answer for a lot of teams is that they trigger nothing, and the builder telling you None active is not a failure state. It is information.

Read the table for the thing it tells you beyond the pairs themselves. Some units turn up in more than one pair, and those are the ones worth building around, because owning them unlocks several routes at once instead of one. Human Spider (Responsible), Nutaru (Beast) are hinge units. If you own one of them, your team has options. If you own none of the units in this table at all, no confirmed Synchro pair is available to you, and the correct move is to build as though the mechanic does not exist rather than to force a pairing that will not fire.

The split is 7 Fuse pairs and 2 Clash pairs. Fuse dominates, which is worth sitting with for a second, because it means most Synchro decisions are really slot decisions. Committing to a Fuse turns two of your six units into one, and the merged unit has to be worth more than the two bodies it replaced. Clash asks nothing of you except that both units are on the field, so it is the easier of the two to build around and the one to reach for first.

Not verified yet. We are confident the 9 pairs above exist and that the Fuse and Clash labels are right. We are not confident the list is complete, because the developer has not published a full pair table, and we are reconstructing it from what we can verify rather than from what looks plausible. It would be easy to pad this out by pairing units that share a franchise, and it would probably even be right occasionally, which is precisely what makes it a bad idea. New pairs land here and in the builder on the same day we confirm them.

There are 7 elements: Fire, Water, Wind, Ice, Rose, Light, Dark. The builder counts how many of them your team covers and lights up when you reach four. That threshold is a rule of thumb rather than a law, and it is worth understanding why it is there instead of treating the readout as a target.

Element coverage protects you against a specific failure: a wave that resists what your whole team does, where you have no answer and simply watch it walk through. A team of six units that all share one element is fast and focused and utterly helpless the moment it meets the thing it cannot hurt. Spreading across four or so elements means that whatever shows up, something in your six can chip it.

But coverage is not free, and this is where a naive reading of the readout will hurt you. Reaching seven out of seven usually means fielding two or three units you have barely levelled, purely because they tick a box. A four-element team of well-invested units beats a seven-element team of tourists nearly every time. Treat the coverage number as a warning light rather than a high score. If it says two, worry. If it says four, stop optimising it and go level something.

Not verified yet. Only 114 of our 115 units have a confirmed element, because the tier lists we can reach publish tier and name but not a per-unit element table. The builder counts only stated elements, so a team of units whose elements are Unknown will read as low coverage even if it is secretly well spread. That is a real limitation of the tool and we would rather you knew about it than quietly got a wrong number.

The role readout does one thing: once you have placed four or more units and none of them is a support, it turns amber and says so. It stays quiet before that, because a two-unit or three-unit team is an early team and telling a new player their opening pair is unbalanced is noise, not help.

Why four? Because that is roughly the point at which a team stops being a collection of damage and starts being a composition. Up to three units you are simply putting your strongest things down and they carry. Past that, the marginal fourth DPS unit adds less than a support would, because supports multiply what the rest of your team is already doing rather than adding a flat amount on top. This is the oldest idea in team building and it is still the one people ignore most, particularly when the tier list is telling them that nineteen units are S+ and every instinct says to field the six highest.

Support units are scarce here, which is the other half of the problem. Only 22 units in our current roster of 115 carry a support role from a source we trust, and a few of the most valuable ones, like Bloody Captain and Iron Billionaire, are also strong enough that people field them for their own output and forget what they are actually contributing. Iron Billionaire in particular is doing two jobs, which is exactly why it turns up in a confirmed Synchro pair.

The genuine downside of our role data, stated plainly: the roles come from third-party tier lists, they are coarse, and a unit tagged DPS may well have a support component nobody has documented. The warning is a prompt to think, not a verdict.

• Tiers come from the post-Update-4.0 community tier lists, cross-checked against the pre-4.0 list where both cover a unit. Where the two disagree, we keep the post-4.0 verdict, because 4.0 changed the meta, and we say so on the unit's page rather than quietly picking one.
• Synchro pairs are only listed when we can source them. Two so far. No inferred pairs, ever.
• Elements and roles are null unless a source states them, which is why so much of this site reads Unknown. That is not an unfinished page, it is the accurate state of public knowledge about this game, and the alternative is a colour we made up.
• Stats we do not have, so we do not show. No DPS, no range, no deploy cost, until we have captured them ourselves.

None of this is modesty. Google's March 2026 update went hunting specifically for confident-sounding fabrication, and more to the point, a player acts on what a guide tells them. A wrong element costs somebody a run. A wrong reward costs them a summon. Saying Unknown costs them nothing except the mild disappointment of an honest answer.