Batomon Showdown Jinto Region Guide — Monsters, Trainers, Nerf Waves

What is Jinto in Batomon Showdown?

Jinto is one of the game’s two main regions — the monster pool that patch 1.0.0 added at full release on September 15, 2026, in the developer’s own words: “Added the Jinto region with 50+ new Batomon!” It is not a monster and not a trainer, though the name gets searched as if it could be either: Jinto is where those monsters come from.

The patch notes file every Batomon under four pools — Pantra, Jinto, Event and Cross-Region — and the monster list keeps that exact structure. The free demo shipped with Pantra only, so the full release’s Jinto wave (50+ monsters at once, by the official count) is the biggest roster event the game has had. Community showcases framed it that way too — the launch window’s roster videos cover little else.

How many Batomon are in the Jinto region?

Officially 50+ — and that is the only total the developer has ever given. No complete public roster exists; the in-game Batopedia is the only full list. What the official record does have is 31 named Jinto monsters, each traceable to a dated source:

That leaves 19+ of the promised fifty-plus unaccounted for by name — they enter the record as the developer rebalances them or as in-game collection lands, one batch at a time. The monster list is the running account.

Why did Jinto monsters get nerfed three patches in a row?

Because the developer measured the gap and published the numbers. One week after launch — first in the Future Update Plans post (September 21, 2026), then again in the 1.1.0 notes — berrymint wrote:

“Jinto end game is full of one-shot kills, which I think is unhealthy and unfun for most players. At days 10+, median DPS of Jinto teams are almost 2 times higher than Pantra teams. I’m aiming to get the power level of all regions into a similar ballpark.”

The three patches that followed are that quote, executed:

• Patch 1.1.0 (September 22) — sixteen Jinto Batomon rebalanced downward (Sukoi’s cooldown tripled, Rattleghast lost poison output and a third of its affordability, Petrirex’s knockout payout halved) plus the Pipskull → Ratacomb evolution delayed to a third knockout, while fourteen Pantra monsters were buffed in the other direction.
• Patch 1.2.0 (September 30) — the notes concede the first wave under-corrected, “still around 1.5x higher” at day 10+, and cut fourteen more Jinto engines. The same patch produced the game’s first reverts: Cinnabark’s and Drumire’s 1.1.0 cuts were rolled back as “a little overzealous”.
• Patch 1.3.0 (October 6) — fine-tuning in both directions: nine Jinto entries, mixing cost cuts and cooldown reverts (Opalion 9 → 6, Petrirex 7 → 5.5, Dollhime’s trinket payoff raised) with fresh nerfs (Steamscuttle “very popular and overperforming”, Aviarab’s multicast tax, Kappow’s gold engine retuned). Sarudo got cut and an apology of sorts — Cost 35 → 25, “underperforming hard. May need another round of buffs.”

The through-line: Jinto launched as the late-game region, and every patch since has been moving power out of it — unevenly, and with visible second-guessing. Which engines survived is what the Batomon tier list tracks per patch.

Which trainers are best in Jinto?

The game’s trainers rate differently by region — the pools differ, so the same ability feeds different engines — and the clearest record of it is the September trainer board thread, whose comment section demanded the split: “You can’t just make a tier list of both regions at the same type, the tiers change a lot depending on which one.” The Jinto-leaning reads from that thread, each a single-voice claim:

Every line above is one thread’s testimony — the trainer tier list carries the full board with the same labels. No official source rates trainers by region; the developer publishes balance notes, not ratings.

How is Jinto different from Pantra?

Three differences, in rising order of consequence:

1. Separate pools, officially filed. The 1.1.0 notes list Jinto, Pantra, Event and Cross-Region Batomon under their own headings — and the community treats region-blind tier lists as distorted for exactly that reason.
2. Different engines. Jinto’s officially documented identity is burst: the developer’s launch-window diagnosis was “Jinto end game is full of one-shot kills”, and the engines it nerfed were poison-per-knockout scaling, ally-damage sharing, KO-triggered shields and cheap fast cooldowns. Pantra’s documented story is the opposite — fourteen of its monsters were buffed because they underperformed.
3. The wall between them is now porous. Patch 1.2.0 added the Smuggler, the first trainer that “brings Batomon from the other regions into your shop” — the first official path to mixed-pool teams, though nothing about its cost or rate is documented.

When Jinto’s burst comps are the ones beating you, the nerfed engines behind them have pages of their own — Petrirex and Opalion each track their full three-patch trail.

What does the Jinto meta look like after patch 1.3.0?

Two signals worth reading together:

• Players still rate the pool’s variety highly. In a dedicated Reddit thread, players argue Jinto has more build diversity than Pantra even after two nerf waves — the region’s identity as the home of burst and synergy chains survived its own rebalancing. The best teams overview tracks the engines that argument is about.
• The region is still being tuned, not abandoned. Nine Jinto entries in 1.3.0 — reverts, cost cuts, a named-synergy nerf — plus Sarudo’s “may need another round of buffs” promise. The same patch gave Master-rank players a top-10 leaderboard, and the high-diamond players pushing for Master are exactly the ones living with those margins.

Concrete six-slot rosters remain unverified — no public win-rate data exists for any monster, in either region. What is verifiable is the direction of every patch line, and that is what the tables above record.

The region’s full roster accounting lives on the monster list, the per-patch engine rankings on the Batomon tier list, and the trainer half of the region split on the trainer tier list. All three refresh with the two-week patch cadence — the gameVersion badge above says which patch this page describes.