Observed layout · recorded with these units
BatoForge observations // team meta · daily
Petrirex + Shikitsune
Inspect a Batomon Showdown combination's common full teams, supporting units and battle results by Run Day.
Build notes
Adjacent Knockouts → revival and growth
Petrirex gains permanent Shield stats from Knocking Out adjacent allies. Shikitsune revives allies so those units can contribute again.
How it works
- Put intended sacrifice units next to Petrirex and keep the reviver available.
- Revived units need time to cast. Include a damage source alongside the Shield growth.
Getting started
Conditions to check
- Protect can block an intended Knockout. Keep the reviver available and check whether revived allies have time to cast; an endless cycle is not assured.
- Check the positions and triggers, then fill the remaining slots with damage, protection or support the core lacks.
- Ability reference: build 26170127. Shop locations use older records; the observed teams' game version is unknown.
Completed period Oct 27 16:00 – Oct 28 16:00 UTCpartial
4,135,850 observations · all modes/regions · includes repeats · game version unknownThe selected Ranked / All period contains 970,642 distinct team votes;31,278 are grouped under this combination in Team Meta. Full teams and supporting units use that group. Trainer and rank details include all teams carrying these units, including teams in other groups.
- Appearance share
- 3.22% 31,278 / 970,642 team votes in this mode and region
- Day-battle win rate
- 58.1% n=31,278 (18183W/13095L)
- Avg observed Run Day
- day 9.6 Average age of the recorded teams, not when this combination first formed.
Playing Petrirex + Shikitsune
These suggestions use build 26170127 abilities. Adapt them to your shop and team; the BatoForge observations below do not reveal purchase order, forms, levels or game version.
Get the core units
- Older Jinto shop listings show Rare Petrirex ($40) and Shikitsune ($35): $75 before rerolls, upgrades and other teammates. Availability may differ in your version.
- For Ratacomb, evolve Pipskull by having it experience three Knockouts. Direct Ratacomb purchase is not listed.
Build the team in stages
Before both support roles are ready
Keep the current damage team until revival is ready. An opening Knockout is useful only with a reward or evolution goal worth losing the recipient's casts.
When revival is available
Put the intended Knockout recipients next to Petrirex and keep Shikitsune outside those slots. Check that revived allies have time to cast. Upgrade Petrirex for more permanent Shield per Knockout.
When repeated Knockouts work
Upgrade the reward your team needs: Ratacomb's permanent Multicast, Emburn's permanent Burn or Cawnushi's permanent Damage. Shikitsune levels add more battle speed to revived allies. Preserve trained recipients when their accumulated growth still helps.
What each level adds
Ability values at levels 1–4. The observed teams' levels are unknown.
| Form | L1 | L2 | L3 | L4 |
|---|---|---|---|---|
| Normal | 20 | 40 | 60 | 240 |
| Shiny | 24 | 48 | 72 | 288 |
This grows Petrirex's Shield stat. It is different from the team's remaining Shield during the battle.
| Form | L1 | L2 | L3 | L4 |
|---|---|---|---|---|
| Normal | 15 | 30 | 45 | 180 |
| Shiny | 18 | 36 | 54 | 216 |
The speed bonus lasts for this battle. Shikitsune's base cooldown stays at 3 seconds through these levels.
Place it for the ability
- Put the intended recipients directly left, right, above or below Petrirex. Keep Shikitsune outside those slots so the reviver remains available.
- Protect can keep important support available but can also block an intended recipient's Knockout. Check each target rather than adding Protect to every unit.
Other units for the same role
- Nekoffin as a Knockout recipient
Its Trinket reward serves Furnadon inventory or new-Trinket payoffs; Ratacomb, Emburn and Cawnushi instead grow different combat stats. These recipients change what the team is trying to build.
- Rattleghast + Nekoffin opening route
Rattleghast supplies a Knockout at battle start for resources. Revival does not repeat it, so use it for an opening reward rather than Petrirex's repeated on-cast Knockouts. Neither unit supplies revival.
When to pause or change the plan
- The cycle stops if the reviver is Knocked Out or Protect blocks the intended recipient's Knockout.
- A revived ally needs time to cast before another Knockout. Keep enough damage alongside the Shield growth to finish the battle.
- Watch the battle to check the order of revival and repeated Knockouts. Cooldown numbers alone cannot show that order or guarantee an endless cycle.
Edit and review your team
- Check cast timing.
Petrirex in the calculator → Set your form, level and Cooldown Speed for Petrirex's 5.5-second base timer. Check which recipients will be available when it casts.
Shikitsune in the calculator → Check Shikitsune's 3-second base timer separately. Watch a battle for the Knockout and revival order; the calculator does not simulate them.
Set your form, level and Cooldown Speed in the calculator. Links start at Normal, level 1 and +0% speed; results estimate the cooldown timer.
- Edit positions, then review ability conditions.
Edit this team in Team Builder → Arrange the six slots, then check that each ability reaches the right ally and meets its type and trigger conditions.
Opens a team example from this period. Its label shows whether the positions were observed, estimated, or chosen only to display the units. Set the actual forms and levels; Team Builder starts at Normal, level 1. It shows stats and which slots an ability reaches. Check type restrictions yourself; it does not simulate battles, Trinkets or permanent growth.
- Compare with the current observations.
See the full teams and position samples below →
Compare the sample sizes and dates below. These repeated observations favor teams that survive longer, and the observed teams may differ from the wider player population. They do not prove which build counters another or which upgrade order is best.
Most-seen full teams
These examples use records from Day 4 onward; compositions also seen earlier are included. Counts group Batomon by species; forms and levels are unknown. Each example labels its positions as observed, estimated, or unavailable.
Observed layout · recorded with these units
Observed layout · recorded with these units
Common supporting units
Share of teams in this Team Meta group that carry each additional unit.
These details include all teams carrying this combination, including teams in other Team Meta groups. There are 32,472 carrying team votes in the selected mode, region and period. Position, Trainer and rank samples differ; each section lists its count.
Where the units sit
Positions 1–6 follow the displayed two-row, three-column board. Each percentage uses that unit's position samples, including repeated copies. These separate samples do not show which six positions occurred together.
Trainers behind it
22 listed Trainers, covering 28,709 of 32,472 carrying team votes. Each win rate uses that Trainer's battles; n is its total wins and losses. 3,763 carrying team votes have no available Trainer detail.
Ladder spread
Shares use the 32,472 team votes with a known rank. Each win rate uses that rank's battles.
Master MMR bands
Percentages use all 19,919 Master team votes;19,919 have recorded MMR. Teams without MMR stay in "MMR unknown."
Presence and results by run day
The longest cyan bar marks the Run Day with the most recorded teams in this group. Other bars are scaled to that day. Each label shows that day's wins and losses; smaller samples also show a 95% confidence lower bound.
- Day 322.2%won
- Day 435.9%won
- Day 541.2%won
- Day 646.6%won
- Day 753.9%won
- Day 858.4%won
- Day 962.1%won
- Day 1062.7%won
- Day 1161.8%won
- Day 1260.0%won
- Day 1359.4%won
- Day 1454.4%won
- Day 1555.2%won
- Day 1654.1%won

