Batomon Showdown // Evolutions

Batomon Evolutions
Levels & Conditions.

Find all 13 Batomon Showdown evolutions in Steam build 26170127, covering 11 base Batomon. Each line shows the required level, victory or special ability condition. Dashed entries have an unknown requirement.

Evolution tips

What does the evolution need?

Some units need levels; others count Trinkets, Knockouts or Burn applications. Check the progress on the unit before buying another upgrade.

Ignit evolves On Victory. It has two listed destinations, Basilord and Flarilisk; how the game chooses between them is still unknown here.

01 // Level threshold

Frillet needs level 3.

Normal and Shiny Frillet both evolve at level 3. The ordinary merge route takes three level-1 copies to make a level-2, then two level-2 copies to make a level-3: six level-1 copies from scratch. Items and other levelling effects can shorten that route, though their gift rewards may differ from an ordinary merge.

02 // Additional collection

Kindlepot counts more Trinkets.

Kindlepot evolves after collecting five more Trinkets. Trinkets you owned before its progress started do not fill that requirement. Follow the remaining count on the unit: if it says two remain, plan for two further collections.

03 // Unit-specific progress

Pipskull must experience the Knockouts.

Pipskull must be Knocked Out three times itself. A teammate's Knockout or a lost battle does not advance that condition on its own. Check Pipskull's remaining count, then arrange a Knockout on that unit while keeping your revival support available.

04 // Applications versus amount

Emberpaw counts Burn inflictions.

Emberpaw counts 25 times your team inflicts Burn. Raising the Burn amount on one cast is different from applying it more often. Look for repeated Burn applications and use Emberpaw's remaining counter to check how your effects are counted.

05 // Timing and cost

Riglet consumes a specific ally next day.

At the start of the next day, Riglet devours the ally in front and evolves into Rigalord. Check which ally “in front” selects before advancing, especially if it is important support. The exact target and empty-slot behavior are still unconfirmed.