Last Updated: July 10, 2026
Introduction
If your Fire lane keeps leaking Zobos while your back-row damage watches from a safe distance, Poakie has a very direct answer: stand up front and set a wide patch of enemies on fire.
The T3 form, Lickflicker, is built for that job. The Fire DPS line starts with Burn, gains a Burn follow-up at T2, then turns into a broad forward cone at T3. It does not bring Sleep, Paralysis, or a flashy hard-disable. It brings repeated AoE damage in the part of the board where lanes usually start going bad.
That makes it tempting. It also makes it easy to waste a painful amount of Fire food on a unit that only performs in a friendly test. This guide breaks down where Lickflicker fits, how to place it, and when the T4 plan should wait.
This guide uses the evolution line Poakie, Lickflicker, and Ignatoad. The public Clash of Critters Tatari list confirms Poakie as a Fire Tatari. Check the in-game evolution screen before committing resources to the newer forms. For wider team choices, pair this guide with the chapter formation guide, Horde Invasion meta guide, Tatari progression guide, and F2P resource habits guide.
Quick answer
Poakie is worth taking toward T3 when you need a Fire unit that can do all of the following:
- Hit a crowded frontline instead of one target.
- Keep Burn rolling after the first impact.
- Cover a broad forward area from a front or near-front tile.
- Work beside a support that improves damage or keeps the frontline alive.
- Enter Horde Invasion without forcing you to retire a better Fire project.
Lickflicker is a strong candidate for a Fire AoE slot. It is not an automatic account-wide priority. My Gold Rush report showed good damage, and its Horde kit is useful, but the unit has no baseline hard control and carries a painful T4 cost. Build it because it fixes a real lane, not because a new frog with fire breath looked cool for twelve seconds.
What changes when Poakie reaches T3
Poakie begins as a Fire AoE attacker. Its early skill spits flame, deals area damage, and applies Burn. After every three attacks, it can switch into a continuous flame sequence. The displayed numbers are straightforward:
- Continuous flame lasts four seconds.
- It ticks every half second, which gives roughly eight damage ticks during the channel.
- Burn has a 20 percent damage factor.
- Burn ticks once per second for five seconds.
At T2, the tooltip adds a follow-up tied to enemies that are already burning. It consumes Burn on the target to deal extra damage at 20 percent per second. That makes repeated Burn application the key partner requirement.
Treat that part as a test item, not a settled rule. Run Poakie beside another Burn source, watch the target's Burn state, and compare the result against the same wave without the second source. A few clean tests tell you more than trying to interpret a cramped tooltip at 2 a.m.
T3 changes the part that is much easier to see. Lickflicker attacks in a broad forward cone covering its own tile and six tiles ahead, arranged as two rows of three. The outermost lanes were not hit in my test. Picture a three-lane-wide damage wedge directly in front of the unit.
That shape is why Lickflicker has real formation value. A narrow attacker can win a good lane. A three-wide front attacker can stabilize the places where enemies bunch up and spill into neighboring lanes.
Lickflicker is a front-line Azurion, with a different job
The cleanest comparison is Azurion. Azurion can sit farther back and apply ranged AoE pressure. Lickflicker operates closer to contact. It trades safety for the chance to burn down a packed area before that pack reaches your softer units.
That does not make one strictly better. They solve different failures.
Use Azurion when your frontline already holds and you need damage that reaches into lanes from safety. Use Lickflicker when the frontline itself is the problem: Grass Zobos enter together, your first contact melts too fast, and a single-target attacker cannot clear the pile before it grows.
Its attack direction mirrors Pyropup from the opposite side of the board. Lickflicker is not a delicate back-row caster. It is a Fire damage project that expects to see enemies nearby.
There is one obvious limitation. Its kit, as shown, has no Sleep, Stun, Paralysis, or similar control on the core battle skill. That means Lickflicker cannot cover every job by itself. It creates damage pressure. It does not replace the Tatari that buys the team time or keeps a dangerous enemy locked down.
If a lane is failing because enemies live too long, Lickflicker can help. If a lane is failing because one enemy charges through a gap or needs a specific control answer, start with the mechanic that stops that enemy. More fire damage is not a universal apology letter.
Where to place Lickflicker in chapters and managers
The T3 cone rewards placement more than raw star count. Before you feed Poakie again, make sure you have a tile where the cone can matter.
For a crowded center push, place Lickflicker in a front or second-row tile that faces the two or three lanes taking the most pressure. If the unit sits at an edge while enemies arrive through the middle, you are paying for a wide attack and using half of it. Slide it inward, run the stage again, and watch the first ten seconds.
Two Lickflickers can be tempting because two forward cones cover a large part of the frontline. That is a valid test for a Fire-heavy Grass stage, especially when the board feeds enemies into the middle. It is not a default formation. Two copies can leave you short on sustain, control, or a counter for another lane.
Use this supporting shape:
- Put Lickflicker where its three-wide cone catches the packed lanes.
- Keep a sturdy first-contact Tatari on the lane that receives the harshest hit.
- Put a support such as Cheerspring or Cheerflutter behind the damage cluster when its boost can reach the Fire unit.
- Use a second Fire attacker only if the report shows you are timing out after the frontline survives.
Do not put a support in the front simply because it is close. If that move makes the support die before it buffs the people doing the work, the formation is doing comedy at your expense.
My Manager-style test reported strong early damage, especially for a pure AoE unit. One report on one account does not establish a boss ranking. Manager tests depend on level, other Tatari, elemental matchup, placement, and how quickly the boss reaches the damaging area. Use the report to start a same-board comparison rather than call it the new best Fire DPS.
Burn damage needs a plan, not a pile of Fire units
Lickflicker has three sources of pressure layered together: the normal flame hit, the continuous flame sequence, and Burn. The T2 follow-up wants an enemy that already burns. That makes stacking Fire units look logical. It can also create a bad team if every slot fights for the same food and nobody provides support.
Start with one question: who applies the first Burn, and who benefits after that?
If Poakie applies Burn reliably by itself, it cannot need a second Burn unit. You can use the remaining slot for healing, an attack boost, a tank, or control. If another Fire unit applies Burn across a wider area, Lickflicker can gain more targets for its follow-up. That setup only pays off if the two units hit the same enemy group often enough.
Overlapping attack buffs do not stack. Test one source, then two, and compare the attack display or combat result. If the second support changes nothing, replace it with a unit that adds a different kind of value.
The same rule applies to Burn. More red icons on a target do not automatically mean a better team. Compare clear time, survival, and damage reports. Your account needs a formation that wins, not a campfire with excellent vibes.
Horde Invasion gives Poakie more to do
The Horde kit makes this line more interesting than a basic chapter DPS. The first Horde skill lets the unit jump to a destination tile and grants nearby allies an attack and damage boost. The important part is speed: it jumps where you tap instead of walking slowly across the board.
Move it out and back to trigger the benefit without leaving it away from the fight for long. Use a quick tap out, then a tap back. That is much more practical than a support unit that spends half the wave taking a scenic route.
There are still two placement traps.
First, do not move it so far that the buff reaches disposable units and misses your actual carries. Check who is inside the nearby area before you tap. A movement skill is only clever when the right allies receive it.
Second, do not play it from the back. The T2 Horde skill shares a song that continuously stuns enemies across a large forward area. In my test, the skill did nothing from the back until enemies entered range. The cone-shaped effect needs a real target in front of it.
That makes its Guardian role sensible. Put it near the frontline where it can see enemies, use the movement trigger to help nearby damage, and avoid sliding it into an empty corner where the song never fires. The unit can still die if it takes too much focus, so test a front tile and a near-front tile instead of deciding after one bad wave.
The third Horde skill sprays scalding oil over a large forward area. The oil slows enemies, ignites for continuous damage and Burn, then ends with a follow-up explosion. This is the part that can make Lickflicker useful against stacked waves. A slow keeps enemies inside the fire area longer. Longer exposure gives the other damage pieces more time to work.
Horde is usually the best place to test the whole kit because the mode gives you packed targets, repeated waves, and room to compare the same formation. Keep the other four pieces stable, change only Poakie's tile or nearby support, and note the first wave where the setup breaks. That is how you find out whether the Guardian helps your team or simply looks busy.
Gold Rush shows why the formation shape matters
In my Gold Rush test, Lickflicker occupied a large square influence area with three connected edge tiles. The attack report placed it at the top of damage in that run.
This is the useful takeaway: Gold Rush is a good place to test whether the T3 range creates value across your actual attack formation. A wide attack is only good when enemies or objectives line up with it. If the board forces your unit to aim through empty tiles, the same T3 can feel ordinary.
Use this small Gold Rush check:
- Run one attack with Lickflicker in its normal Fire slot.
- Save the report or remember its damage position.
- Move it one tile toward the area with the most targets.
- Run a comparable attack.
- Compare damage and team result, not damage alone.
If it climbs the report while the team still wins cleanly, you found a better tile. If it climbs but another lane collapses, the placement is stealing more value than it creates. Gold Rush reports are helpful, but they are not a trophy screen. They are a map of what the formation did.
T4 is the expensive part of this story
The T4 target is Ignatoad. Its displayed cost matches a T4 Pyropup project: 20,000 energy drinks and 15 Volcano Pizzas. The numbers are big enough that you should stop treating this as a casual upgrade.
Volcano Pizzas are the choke point in my account. Energy builds up over time, but a specific food item can keep a good T3 stuck for days while the rest of your account waits.
That does not mean Ignatoad is a bad goal. It means T3 should earn the T4 plan first. Put Lickflicker into the modes you care about. If it keeps a chapter lane alive, helps a Horde wave, and still makes sense after you compare it with your existing Fire line, start saving. If it only wins a friendly Gold Rush report, keep it at T3 and spend the pizzas where they solve an immediate problem.
Before starting the T4 food grind, answer these questions honestly:
- Does Lickflicker have a permanent slot in one of my main formations?
- Does it beat or complement the Fire unit I otherwise build?
- Does my team need more AoE damage more than it needs control, healing, or a different element?
- Can I complete the evolution trial in the event window I have?
- Will farming these resources delay a more proven T4 project?
One "yes" is excitement. Four or five "yes" answers are a plan.
Who should build Poakie now
Poakie is a good T3 project for players who have a Fire gap in crowded lanes, can place a forward cone cleanly, and have supports that keep a close-range damage unit alive. It also makes sense for players who enjoy actively moving a Guardian in Horde rather than leaving the board on auto-pilot.
Poakie is a weaker priority for players whose Fire line already solves Grass stages with Azurion, Pyropup, or another established project. It is also a weaker choice when your account fails because of control, tanking, or the wrong elemental counter. A new T3 cannot rescue a formation that is solving the wrong problem.
For F2P players, the sensible route is T2 testing first. Use the Burn effect in a chapter stage, then test the forward range in Horde or Gold Rush. If the unit gets picked, keeps damage high, and does not force an ugly resource trade, continue to T3. Save the T4 commitment for after you have seen it work in more than one mode.
For players who spend, the same test still matters. Spending can skip the wait. It cannot make a poorly placed cone hit enemies that are not there.
Mistakes that make Lickflicker look worse than it is
The first mistake is treating the T3 cone like a back-row projectile. It wants enemies in front of it. Give it an empty lane and it contributes a very expensive light show.
The second is judging it against a bad target set. Test it against crowded Grass lanes, a Manager where it can keep hitting, and Horde waves that stay inside the forward area. A single scattered lane is a poor audition for an AoE Fire DPS.
The third is doubling down on Fire when the team lacks a role. If another Fire unit has the same food cost and you still cannot stop enemy charges, build the unit that controls or survives. Damage screenshots do not clear content by themselves.
The fourth is pushing T4 before checking the trial and event schedule. The Update 0.43.1 planning guide explains why Trial Quest filtering and the two-week event calendar are now worth checking before an evolution project. New units do not get a special pass on bad timing.
The fifth is copying a late-game report without copying the conditions. A high-damage Gold Rush result can rely on a level gap, other Fire pieces, a particular tile, or enemy placement. Copy the test method. Do not copy the confidence level.
A seven-day test plan before you commit
You do not need a spreadsheet the size of a tax return to decide whether Poakie deserves Fire resources. Seven focused days are enough.
On days one and two, use T1 or T2 in a chapter lane where Grass enemies bunch up. Record whether it helps the lane survive or simply adds damage after another unit already solved the fight.
On days three and four, test the same account in Horde Invasion. Keep four Tatari fixed. Move Poakie between a front and near-front tile. Trigger the movement buff around your core damage cluster. Watch whether the song and oil skills see enough enemies to justify the placement.
On day five, run comparable Gold Rush attacks with two different tiles. Do not chase the largest single number. Look for a result that keeps the whole attack formation healthier.
On day six, compare it with the Fire project you would have built instead. Use the same stage, same support, and same placement logic. If Poakie wins only when you give it every buff, that tells you something.
On day seven, open the evolution screen. Check the trial, the calendar, your energy drinks, and your Volcano Pizzas. Then decide whether T3 is an immediate push, a slow project, or a fun side experiment.
That pace sounds boring. It is also how you avoid turning 20,000 energy drinks into a very confident mistake.
Final recommendation
Lickflicker has the right kind of early value. The T3 forward cone fixes a common Fire-team problem, the Burn kit rewards packed enemies, and the Horde skills give it more to do than stand still and breathe fire. Keep it at T3 until it earns a permanent formation slot.
Take Poakie to T3 when you can point that cone at a real frontline problem. Keep it there while you test chapters, Horde, and Gold Rush. Move toward Ignatoad only after the T3 has become part of your regular formation and the resource cost no longer wrecks a better plan.
FAQ
Is Poakie worth evolving to T3?
Poakie is worth evolving to T3 when your Fire team needs wide front-line AoE against crowded enemies. Lickflicker gains a broad forward cone and keeps Burn pressure, so it is more useful than a narrow damage unit when several lanes meet near the front.
What does Lickflicker's T3 attack hit?
Lickflicker hits its own tile plus six tiles directly ahead in a three-wide, two-row shape. The outermost lanes were not hit in my test. Place it against the same enemy route before comparing damage reports.
Is Lickflicker good in Horde Invasion?
It looks promising in Horde Invasion. Its shown kit includes a tap-to-move ally buff, a forward stun song that needs enemies in range, and a large oil effect that slows, burns, and ends with extra damage. It needs a front or near-front placement where those effects can see enemies.
Should I build Ignatoad right after T3?
Usually no. The displayed T4 cost is 20,000 energy drinks and 15 Volcano Pizzas. Build toward Ignatoad after Lickflicker earns a stable role in your main teams and you have checked the evolution trial and upcoming event timing.
Does Lickflicker replace Azurion?
No. Azurion is safer as a ranged AoE Fire damage option. Lickflicker is closer to the frontline and does its best work against packed enemies in its forward cone. Use the unit that fixes your current lane failure, or run both only when the formation can support the Fire investment.