Horde Invasion Meta Guide

Last Updated: July 5, 2026

Introduction

Horde Invasion is starting to look less like a simple "bring fifteen strong Tatari" mode and more like a two-player formation puzzle. The subtitle behind this guide showed a creator testing a newer community setup after checking the Horde Invasion Discord chat, then landing around 1,080 kills on a run where they usually sat closer to the 950-970 range.

That number is useful, but do not worship it. The creator also made the important disclaimer: almost everything they brought was around Tier 3, and the account already had several Tier 4 pieces. If your roster is still a pile of T1 and T2 projects, copying the exact board will probably feel awful. You can still steal the logic, though, and that is the point of this guide.

This is an original strategy guide based on the provided Horde Invasion subtitle and the site's current Tatari data. It is not an official balance note, and it is not a word-for-word transcript. Use it with the Horde Invasion beginner guide, team-building framework, Tatari progression guide, and Tatari database.

Quick Answer

The new Horde Invasion meta idea is built around partner-aware support stacking:

Swap your Sonarbat to the teammate side when the run plan uses bat swap value.
Use Bat: Fragile with Tideon-style Slow and Fragile instead of relying on duplicate Tideon effects.
Split utility jobs between Toucanzam and Pandarrior instead of both players blindly mirroring the same slot.
Build the backline around Waveflutter, Sealoon, Chefugu-style food support, Cheer support, Sunfleur-style healing, and one carefully controlled spore support piece.
Push Toucanzam toward level 7 early in the run if your setup depends on Charged attack boost and damage reduction.
Keep the spore support line low until you understand the ally-damage risk.
Treat Zapantler, Voltmare, Tideon, and similar damage pieces as protected tools, not random frontliners.

The short version: this setup wins by stacking buffs, debuffs, slow, sleep, Weaken, Fragile, and partner-side damage value. It is not just a DPS check. If you copy only the names and ignore placement, you will miss the whole joke and probably blame the wrong Tatari.

Who This Meta Is For

This is not the first Horde board a beginner should build. A beginner should first learn why Horde punishes weak frontlines, scattered healers, and campaign teams that run out of gas after a few waves. If that is where you are, read the Horde Invasion beginner guide first.

This guide is for players who have at least some of these things ready:

Several T3 Tatari that can enter Horde without embarrassing themselves.
A partner who can coordinate side placement instead of hitting deploy and leaving.
Access to Sonarbat or a bat-style setup.
Access to Waveflutter or another serious setup piece.
Enough in-run upgrade discipline to avoid leveling every shiny button.
A willingness to move a unit for a reason, then test the result instead of rebuilding the whole board.

The creator's run had a stronger account context than many players will have. That matters. A Tier 3 Waveflutter, T3 Sonarbat, T3 Sealoon, and a few T4 damage or utility pieces create a different floor than a mixed account with half-finished lines.

But the core idea scales down: Horde rewards a coordinated pair more than two solo players standing near each other. Even if you cannot build the exact version, you can still use the same questions:

Which side gets the bigger ally buff?
Which Fragile sources stack, and which ones are redundant?
Which support unit needs to be on my partner's side instead of mine?
Which unit should stay low level because its later upgrade causes risk?
Which damage unit needs protection instead of a brave little trip to the front row?

That thinking is the meta. The exact screenshot is just one account's answer.

The Formation at a Glance

The subtitle describes a setup with three main layers.

The first layer is the partner-swap layer. Sonarbat is not only there because "bat good." The important play is the bat swap: your bat goes to the ally side, and the ally's bat comes to your side. In the creator's explanation, the teammate side receives the larger damage boost, so both players can benefit more by crossing the bats instead of keeping them selfishly on their own side.

The second layer is the status layer. Sonarbat brings Perfectly Scouted and Bat: Fragile. Tideon brings a Slow and Fragile package. Sealoon contributes Weaken through bouncing ball pressure. Waveflutter can add Slow and upgrade pressure into Sleep when placed correctly. The spore support line can add another Fragile-style tool, but it comes with ally-damage risk. This is why the board can feel much stronger than a normal "fifteen decent Tatari" pile. The enemies are not simply taking hits; they are getting softened from several angles.

The third layer is the utility-and-position layer. Toucanzam, Pandarrior, Waveflutter, Chefugu-style support, Cheer support, Sunfleur, Zapantler, and Voltmare are not all doing the same job. Some hold or manipulate space. Some buff. Some heal. Some create debuffs. Some clear. Some look strange up front but make sense because the rest of the formation is built around them.

When those layers line up, the run gets smoother. When one layer is missing, the same formation can look silly. That is why people can copy a strong Horde board and get very different results.

Why Bat Swap Matters

"Bat swap" is the first concept to understand because it changes how you think about sides.

In a normal solo mindset, you put your best support near your own best damage. That is simple and sometimes fine. Horde Invasion can reward a less selfish pattern. If Sonarbat gives stronger teammate-side value in the run setup, then the best place for your Sonarbat may be on your partner's side, while their Sonarbat sits on yours.

That feels wrong for about five seconds. Then the numbers start to make sense.

The goal is not to show off that you understand a trick. The goal is to make each side receive the better version of the support effect. If both players keep their bats at home, both sides can end up with the smaller value. If both players swap cleanly, each side can get the larger teammate-side value while still keeping Bat: Fragile pressure in the fight.

The creator also points out the second reason bat swap matters: Bat: Fragile can stack with Tideon-style Fragile value. That is a big deal. If your partner already brings Tideon, adding your own Tideon may not be the best use of the slot if the same effect does not stack in the way you hope. But Bat: Fragile and Tideon pressure are different enough that the combined setup can be stronger than doubling the same unit.

That gives you a practical rule:

If nobody has bat value, adding Sonarbat may be a priority.
If one side has Tideon already, test Sonarbat plus Tideon before running two Tideons.
If both players own Sonarbat, plan who swaps where before the wave chaos starts.
If your team damage is almost enough but enemies survive too long, add Fragile or scout value before adding one more random DPS.

Bat swap is not magic. It still needs damage behind it. But it turns damage into better damage, and Horde loves anything that turns repeated hits into a bigger payoff.

Fragile Stacking Is the Real Damage Plan

The headline looks like "new Horde meta," but the actual engine is status layering. This is why the formation can outperform a more obvious damage board.

Sonarbat's public data lists Sonar Power as a wide-area effect that inflicts Perfectly Scouted and Bat: Fragile. Tideon creates a large cloud that deals continuous AoE damage while inflicting Slow and Fragile. Sealoon's Tide Tumble launches a bouncing ball that inflicts Weaken. Waveflutter's Somno-Shot can turn nearby ally damage into Slow and potential Sleep pressure. Hyphoria-style spore support can apply Fragile while giving ally-side boosts, but the line can also slightly damage allies.

Those words matter. Horde enemies do not arrive politely one at a time. They come in clumps, they survive through sloppy damage, and they punish boards that spend all their power on the first target. Wide-area debuffs and damage amplification make your whole formation more useful.

Here is the simple mental model:

Bat: Fragile helps damage matter more.
Tideon-style Slow and Fragile helps enemies stay under pressure longer.
Sealoon's Weaken makes enemies worse at killing your board.
Waveflutter's Slow/Sleep setup buys time and adds wake-up damage value.
Spore support can add another fragile-style layer, but it needs restraint.
Cheer and Sunfleur-style support keep the board alive long enough for the layers to matter.

This is also why the setup can be fragile in the human sense. If you place these pieces badly, nothing lines up. Sonarbat can hit the wrong area. Tideon can duplicate a role your partner already covers. Waveflutter can fail to support the group. Spore support can become a self-inflicted problem. Sealoon can bounce value into the wrong lane.

When you test this meta, do not ask only, "Did I bring the right Tatari?" Ask, "Did the enemy stand inside the problem I created for them?" If the answer is no, move the formation before blaming the roster.

Toucanzam, Pandarrior, and the Partner Split

The subtitle highlights a partner split where one player uses Toucanzam and the other uses a Panda-style utility option, which is best understood as Pandarrior or that Grass utility line depending on the account.

That split makes sense because Horde does not need both players to solve the same problem in the same way. Toucanzam brings Lightning tank utility and Charged support. Its Bolt Bond skill can link allies and grant Charged attack boost, with stronger value for Lightning allies. Pandarrior brings a different Grass damage/control shape through bamboo pressure and slow value.

If both players bring the same utility job, the run can lose flexibility. If one side handles Toucanzam's Charged plan while the other brings Panda-style field pressure, the two boards can cover more situations.

The creator's Toucanzam placement also uses a weird but important trick: Toucanzam starts far back, then a worm pull drags it forward into enemy territory. Once that happens, the unit sits much farther up than you could normally place it, and the original front area effectively opens up. That can create a free-feeling slot at the front while Toucanzam keeps doing its job in an advanced position.

There are two warnings here.

First, if you move the pulled unit out of that advanced position, you may not be able to put it back unless the worm repeats the pull. Do not casually adjust it after the trick works. That is like finally finding a parking spot and then driving away because you wanted to check the paint.

Second, do not sabotage the pull with control effects. The subtitle warns against leveling Sunfleur to the point where it can stun at the wrong time, and against placing units inside Waveflutter effects if Sleep can interfere with the worm. The exact interaction can depend on timing and version, but the practical rule is easy: if the pull is part of the plan, do not add stun or sleep in the pull path before the trick happens.

That is the kind of detail that separates a copied formation from an actual Horde plan.

The Backline Engine

The backline in this setup is not a lazy pile of supports. Each slot has a job.

Waveflutter is the setup piece. It can help nearby allies apply Slow and Sleep pressure, which matters more in Horde than in short fights because the waves keep feeding enemies into the danger area. The creator usually left Waveflutter low in other contexts, but in this version they were told to push it up to level 7 later because the risky mushroom/spore placement concern was not the same.

Sealoon sits near Waveflutter to keep wave and bouncing-ball value moving. The subtitle calls out Sealoon's ball pressure and Weaken effect, which helps enemies struggle to kill your board. Sealoon is not only there for damage; it is there because Horde rewards repeated softening.

Chefugu-style food support sits in the Waveflutter wave area in the creator's setup. The transcript calls it a "pig," but the site data lines up better with Chefugu-style support: food or sushi-style projectiles, attack boost, and healing or support value. In this guide, treat that slot as the food-support job. If your account uses a different unit for that job, the question is still the same: does it boost the teammate side, help the clustered group, and avoid ruining Waveflutter's setup?

Cheer support, including Cheerling, Cheerstella, or related forms, gives healing, attack boost, defense boost, and sometimes emergency survival value. The creator did not rush those levels immediately because damage dealers had to come online first. That is a useful habit. Support is excellent, but early run upgrades should still answer the current wave failure.

Sunfleur-style healing is strong but can be awkward if a later upgrade creates control that interferes with the worm pull. That does not make Sunfleur bad. It means you should not autopilot upgrades. Horde often asks you to stop at the level that serves the plan, not the level that feels nicest on the menu.

The spore support line is the spicy one. Funglet, Trippet, and Hyphoria-style skills can create spore rings, boost allies, reduce damage, and in later forms apply Fragile. They can also damage allies. The creator was specifically told to leave the shroom/spore piece at level 1. That advice should not be ignored just because an upgrade button is glowing at you.

If you want the backline engine to work, use this order of thought:

Put Waveflutter where its setup reaches the cluster that will actually fight.
Put Sealoon where its bounce and Weaken path matters.
Place food support where it boosts the right side and does not disrupt the pull trick.
Keep Cheer and Sunfleur close enough to help the units that take repeated pressure.
Add spore support only when you understand its ally-damage and upgrade risk.

That is a lot of work for a backline. That is also why Horde is fun when it clicks.

Damage Slots: Zapantler, Tideon, Voltmare, and Friends

The damage layer is where many players will overcorrect. They see a support-heavy meta and decide damage no longer matters. Then the run times out, enemies pile up, and everyone pretends RNG betrayed them.

Damage still matters. The point is that damage should be placed inside the support engine.

Zapantler is one of the most interesting pieces because the creator was not used to throwing it farther forward. Zapantler's pierce and paralysis-style pressure can be excellent when enemies line up, but it needs protection and setup. If Zapantler is shoved into a spot where it dies or wastes pierce, it will look worse than it is.

Tideon is a large-area pressure piece. Its Haze Hex creates continuous AoE damage while applying Slow and Fragile. In the creator's team, the partner was running Tideon, so the creator did not double it. That is a clean lesson: if your partner already provides the Tideon layer, your slot may be better spent on Sonarbat, Zapantler, Voltmare, Sealoon, or another job.

Voltmare is the straightforward "this thing is strong" option. The creator mentions having Voltmare in the formation depending on RNG and setup. Voltmare can be a heavy Lightning damage piece when you need power, but it still benefits from Bat: Fragile, Weaken, Slow, Sleep, and support buffs. Do not isolate your best damage and then complain that it underperformed.

Silversear is mentioned as a possible replacement for the Chefugu-style support slot by some players, but the creator is cautious about it. That is the right tone. Silversear may need to be deployed after allies are already out to get its attack boost value, depending on the interaction being used. If you test Silversear, write down the timing. Do not just ask whether the unit is good; ask whether you deployed it when its value actually exists.

Blitzmane, Stormlion, Tikowl, Goonbug, and similar account-specific options can appear as substitutes. But substitutions should follow a job, not a name. If you lack Zapantler, find the unit that gives the closest useful damage or control pattern. If you lack Tideon, find another way to supply wide-area pressure. If you lack Toucanzam, you need another durable utility plan and should not pretend the formation is unchanged.

Upgrade Order Inside the Run

The subtitle gives a practical upgrade order, and this is where a lot of players can improve quickly.

The creator pushed Toucanzam to level 7 early. The reason was not "because Toucanzam is cool," even though, yes, big charged bird magic is not exactly boring. The reason was Charged attack boost and damage reduction. If Toucanzam is the utility anchor for your side or your partner-side plan, getting that level spike online can stabilize the whole formation.

After that, the creator remembers moving toward Sealoon. That makes sense if Sealoon's wave and Weaken pressure are part of the backline engine. Weaken helps the team survive; bounce pressure keeps value moving through crowded waves.

Waveflutter came later than usual in this specific setup. The creator normally left Waveflutter around level 1, but was told to push it up when the setup no longer had the same mushroom/spore risk. That is not a universal command to slam Waveflutter every run. It is a reminder that upgrade priority changes with placement.

Damage dealers still need attention early. The creator delayed Cheerling and Sunfleur-style support upgrades until later because the run first needed damage. That is a good rule for support-heavy boards: do not turn your early upgrades into a cozy spa day while enemies are still walking through your front line. Healing and buffs matter, but dead enemies also heal your board in the very technical sense that they stop punching it.

The spore support line is the exception. The advice was to leave it at level 1. This matters because later spore effects can damage allies or create placement risk. If the community tells you a support should stay low, test that exact instruction before "improving" it. More levels are not automatically more value in Horde.

A practical order can look like this:

Rush the utility breakpoint that makes the formation work, often Toucanzam level 7 in this setup.
Level the damage or debuff piece that fixes the current wave failure.
Bring Sealoon or similar Weaken/support pressure online if enemies are killing you through the front.
Upgrade Waveflutter when its setup is safely positioned and actively used.
Add Cheer and Sunfleur levels when survival, not damage, becomes the blocker.
Keep spore support low unless your tested version proves it is safe.
Save enough in-run currency to redeploy important units when overcrowding or bad pulls happen.

Do not follow that as a sacred script. Follow it as a checklist for why each upgrade happens.

The Worm Pull Trick

The worm pull is one of the most specific ideas from the subtitle, and it deserves its own section because it is easy to misunderstand.

The creator placed Toucanzam all the way in the back. When the worm appeared, the team was pushed forward, and Toucanzam got sucked into enemy territory. Once there, it occupied a much more aggressive position than the player could normally choose. The original front slot then became available for another unit.

That is powerful because Horde formation space is limited. Getting a unit pulled into a legal-but-unusual position can create an extra layer of pressure and utility. It can also make your board look like nonsense until the trick happens, which is why random teammates may panic if they do not know the plan.

The trick has three rules:

First, do not block the pull. Stun, sleep, or other control can ruin the timing if it hits the worm before it does the job. This is why the subtitle warns about Sunfleur level 5 and Waveflutter Sleep placement.

Second, do not move the unit after it lands unless you are ready to lose the position. The creator notes that if they moved it out, they could not simply place it back there unless the worm pulled it again.

Third, keep spare in-run currency for cleanup. The subtitle mentions dropping everybody back when the screen gets overcrowded and then spending currency to bring key pieces back in. Horde gets messy. A formation that only works in a calm screenshot is not a formation; it is a souvenir.

This trick is advanced. If your team is already collapsing in early waves, fix basics first. But if you have the pieces and a partner who can coordinate, the worm pull can turn a back-row utility unit into a front-line advantage without wasting the original front slot.

Substitute Rules for Imperfect Accounts

Most players will not have the exact board. That is fine. The wrong response is to say, "I do not have one piece, so the guide is useless." The better response is to replace jobs.

Use this job map:

Sonarbat job: Bat: Fragile, scouting value, partner-side damage boost interaction.
Tideon job: large-area damage, Slow, Fragile.
Toucanzam job: durable Lightning utility, Charged attack boost, damage reduction, ally linking.
Pandarrior job: Grass pressure, slow field value, partner-side utility split.
Waveflutter job: setup zone, Slow/Sleep pressure, ally damage conversion.
Sealoon job: bounce pressure and Weaken.
Chefugu-style job: food/sushi support, attack boost, healing or teammate-side support value.
Cheer job: repeated healing, attack boost, defense boost, emergency stability.
Sunfleur job: healing plus attack and defense support, with level-timing caution.
Spore support job: ally boost plus Fragile-style pressure, with ally-damage risk.
Zapantler job: piercing Lightning damage and paralysis-style pressure.
Voltmare job: heavy Lightning damage when the team needs raw punch.

If you lack one piece, do not replace it with your highest-power Tatari by default. Replace it with the closest job. A lower-power unit doing the correct job can outperform a shiny unit that does not interact with the formation.

For example, if you lack Tideon, you are missing wide-area Slow and Fragile pressure. A random single-target attacker does not replace that. If you lack Sealoon, you are missing Weaken and bounce value. Another healer does not replace that. If you lack Toucanzam, you are missing a Charged utility anchor and possibly the worm pull plan. Another DPS does not replace that.

This is also where your partner matters. Maybe you do not own Tideon, but your partner does. Great. You can spend your slot on Sonarbat, Zapantler, Waveflutter, Chefugu-style support, or another missing job. Horde is not an account flex contest. It is a shared machine, and shared machines get worse when both players install the same part twice.

Common Mistakes

The first mistake is copying the exact board without the Tier 3 context. The creator's run used mostly Tier 3 pieces and several Tier 4s. If your board is weaker, copy the roles and upgrade logic before copying every slot.

The second mistake is skipping the bat swap. If the setup assumes teammate-side boost value and both players keep Sonarbat at home, the board loses one of its main reasons to exist.

The third mistake is running duplicate Tideon when the partner already covers the Tideon layer. Two copies may not give the stack you imagine. Test Sonarbat plus Tideon first.

The fourth mistake is overleveling the spore support. If the community version says leave it at level 1, there is probably a reason. Ally damage is funny exactly once, and usually only for the person watching your run fail.

The fifth mistake is upgrading support before damage. Cheer, Sunfleur, and food support are excellent, but they need a board that can actually kill waves. If enemies survive forever, your healing just gives them a longer appointment.

The sixth mistake is breaking the worm pull. Do not add stun or sleep where it stops the trick. Do not move the pulled unit out of its special position unless you have a plan to recover.

The seventh mistake is ignoring your partner's side. Horde is not two people playing separate mini-games. If your partner brings Tideon, maybe you bring Sonarbat. If your partner brings Toucanzam, maybe you bring Panda utility. If your partner has the stronger Zapantler, protect that lane instead of duplicating a weaker one.

The eighth mistake is treating the result as guaranteed. A 1,080-kill run proves the setup can work. It does not prove every account will land there today. RNG, upgrades, partner timing, cards, and unit levels still matter.

Testing Checklist

Before you call this meta bad, test it cleanly.

Use this checklist:

Did both players agree on bat swap before the run started?
Is Sonarbat actually on the side where the larger teammate-side value applies?
Is Tideon duplicated, or is one player using a different Fragile layer?
Is Toucanzam or the utility anchor positioned for the worm pull if that trick is part of the plan?
Did you avoid Sunfleur or Waveflutter control that blocks the worm pull?
Is Waveflutter placed near allies who can use Slow/Sleep setup?
Is Sealoon placed where bounce and Weaken matter?
Is Chefugu-style food support boosting the correct cluster?
Is the spore support still low level if ally damage is a risk?
Did you level Toucanzam or your utility breakpoint before spending everywhere else?
Did you protect Zapantler, Voltmare, Tideon, or your main damage slot?
Did you keep enough in-run currency for redeploys when the field got crowded?

After the run, write down the first failure, not the loudest failure. If the first problem was "worm pull never happened," fix the pull. If the first problem was "Waveflutter did not reach the damage cluster," move Waveflutter. If the first problem was "enemies lived forever," upgrade damage or add a better Fragile layer. If the first problem was "front collapsed," add support or stop exposing your damage slot.

One clean note after a run is worth more than five angry guesses.

Final Recommendation

The newer Horde Invasion meta is worth testing if you have the pieces, but the real value is the formation logic.

Bat swap teaches you to think across sides. Sonarbat plus Tideon teaches you to stack different debuff layers instead of duplicating the same one. Toucanzam and Pandarrior teach you to split utility jobs with your partner. Waveflutter, Sealoon, Chefugu-style support, Cheer support, Sunfleur, and spore support teach you that the backline can be the engine, not decoration. Zapantler, Tideon, and Voltmare teach you that damage still matters, but it should fire through the support machine.

If you are close to the required roster, try the setup. If you are not close, do not panic-build every named Tatari overnight. Build toward the jobs:

one bat/scout/Fragile layer,
one wide-area Fragile or Slow layer,
one utility anchor,
one setup zone,
one Weaken or defensive softening tool,
one healing and buff core,
one protected damage plan.

That path will help your Horde Invasion team even if the exact community meta changes next week.

FAQ

What is the new Horde Invasion meta in Clash of Critters?

The current community idea is a partner-aware support stack built around Sonarbat bat swap, Fragile layering, Toucanzam or Panda-style utility, Waveflutter setup, Sealoon Weaken, Chefugu-style food support, and protected damage pieces such as Zapantler, Tideon, or Voltmare.

Do I need every Tatari at Tier 3?

You do not need every Tatari at Tier 3 to learn the idea, but the tested run behind this guide used mostly T3 pieces and several T4s. If your account is earlier, copy the jobs first and upgrade toward the key breakpoints over time.

Why do players swap Sonarbat in Horde Invasion?

The subtitle describes bat swap as a way for each player to give the stronger teammate-side damage boost to the other side while still using Bat: Fragile pressure. It also lets Bat: Fragile stack with Tideon-style Fragile value.

Should both players run Tideon?

Not automatically. The creator avoided running Tideon because the partner already had it, and duplicate Tideon effects did not appear to be the main stack. Sonarbat plus Tideon can be a better test than two Tideons.

Why keep the spore support line at level 1?

The subtitle warns to leave the shroom or spore support low because later effects can damage allies or create placement risk. Treat Funglet, Trippet, or Hyphoria-style support as a tool to test carefully, not an automatic max-level button.

Is this better than the beginner Horde team?

It is a higher-investment version for coordinated players. Beginners should first build stable lanes, healing, support, and reward discipline with the Horde Invasion beginner guide, then move into this meta when they have the pieces.