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 Synchro Clash pair, and it lights up both units when they do, telling you which of the two pairs it found and whether that pair is documented or merely reported. 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.

The mechanic is called Synchro Clash, 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 Clash 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 fires. 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.

It has three kinds, and this page used to get the names wrong. There is no "Fuse" — that word was ours, and it is gone. Pro Game Guides distinguishes a Synchro Clash from a Synchro Drive, and separately describes two units merging into one. In a Clash or a Drive both units stay on the board and attack together; a Merge trades the two for one. Deltia's Gaming dates the Clash to Update 2.5, well before the 4.0 rename this site otherwise revolves around.

Both sources give the same four conditions for a Clash, and all four have to hold at once:

• Both units must be placed on the same field.
• They must be within each other’s attack range.
• Both must be fully upgraded, or at least upgraded equally.
• The clash then fires automatically, with no button to press.

The third one is the one people miss. Two units on the list, standing next to each other, will sit there doing nothing if one of them is three upgrades ahead of the other. Level them together or take them both to the top. And when it does fire, it fires on its own: there is no button, and it repeats on a cooldown for the rest of the wave.

This has a real consequence for how you build, and it is the reason the builder exists. You cannot deduce your pairs. You have to look them up, and there is not a great deal to look up, because the developer has never published the pair list and no independent source confirms an active Trello board for Z. So the honest answer for most teams is that they trigger nothing, and the builder telling you None active is not a failure state. It is information.

2 Clashes, 2 Drives, 3 Merges. Two of them come with numbers: Mimicry Sorcerer (Cursed Love) + Jane Juliet (Larper) at 500% of the average damage between the two units, a 60 seconds cooldown and a Water (Ground) attack type, per Deltia's Gaming; and Pirate King (Voyage) + Quake Warlord (Destroyer), which hits the entire map for massive averaged damage on a 300 seconds cooldown, per Pro Game Guides. Those cooldowns are five minutes apart, so we attribute each to whoever published it rather than blending them.

A Clash or a Drive costs you no board presence: you keep both bodies, both keep attacking on their own, and the joint attack lands on top. A Merge does not work like that, which is why the merges are the rows everybody else invents names for. Of the 3 we can source, exactly 1 has a name attached by anybody, and Pro Game Guides adds the useful part about the other two: both inherit Human Spider's Trait and stats, so his build drives their damage.

Not verified yet. We are not confident this list is complete. The developer has not published a pair table, and the only pages carrying longer lists are auto-generated wikis that contradict each other. This table used to carry nine rows with a merged-unit name on every one; six of those names appear in no source at all, and a seventh was the right pair under the wrong name. They are gone. A merged-unit name is the thing a player farms toward, so printing one nobody can source does real damage. New pairs land here and in the builder when a source we can name publishes 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. Worse, the units that quietly hold a team together are not the ones a tier list points at: Iron Billionaire (Genius) is tagged Farm rather than Support, and a damage-led reading will have you bench it for a sixth DPS unit that adds less than the economy it was generating. Read the role column, not just the letter.

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 Clash pairs are only listed when a source names them. Deltia's Gaming documents one. Community trackers report a second, and it is labelled that way everywhere it appears. No inferred pairs, ever, and no merged-unit names, because no source publishes any.
• 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. The single exception is the Synchro Clash damage, cooldown and attack type above, which we print because Deltia's published them and we can point at the page.
• We do not play this game. Nobody here has launched it. This site compiles and cross-checks what independent trackers and guides publish, and names them: Pro Game Guides, Destructoid, Beebom, Try Hard Guides and Deltia's Gaming. Where they disagree, we say so rather than picking the tidier answer.

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.