How Does Multicast Work in Batomon Showdown? — Rules & Triggers Explained

How does multicast work in Batomon Showdown?

The answer players give each other, thread after thread: one stack of Multicast makes an ability fire one extra time, every trigger takes 0.1 seconds, no monster can trigger faster than once per 0.1 seconds, and any stacks left over after the cooldown window closes simply do nothing. That rulebook matches every “how does multi-cast work?” thread on the game’s subreddit. Multicast the keyword is real and printed on the cards; the per-stack arithmetic around it is still community consensus — and this page keeps that distinction visible in every section, even where official text has started to echo one of the numbers.

What Multicast is — on the record

Multicast is one of the game’s printed mechanic keywords. Patch 1.0.0 formally introduced keyword styling (its notes call out Cooldown Speed and Income “becoming keywords”), and Multicast behaves the same way in the balance notes: it names a stat, and patches move that stat’s number. The clearest official sighting sits on an ordinary monster card in the game’s own store screenshots — an event reward panel for Brawlmantis showing a 5.5-second cooldown, “Deal 50 damage” and a blue keyword line reading “Multicast: 2”:

Screenshot: official Steam store page (berrymint, September 2026).

Three official facts anchor the keyword:

What the record never shows is the word used in a sentence of rules — no note explains what a second Multicast point does. That silence is why the community threads exist, and why the best-teams overview treats Multicast as an archetype anchor while its mechanics still live on this page.

The rules players agree on — with proof status attached

Three rules recur across every mechanic thread. Each one is quoted back consistently by multiple commenters, and none of them is official:

Read together they sketch a coherent model — the cooldown window is the boundary, 0.1 seconds is the tick rate, stacks only buy extra ticks inside it — and that coherence is probably why the answers keep repeating. The 0.1-second figure now has the strongest paper trail of the three: three independent Reddit sightings with the same number, one of them turned into math (cooldown ÷ 0.1, plus one for the base cast), one creator stating it on camera while explaining why his 31-stack build stopped scaling — and, since October, two official footnotes that use the same figure for the cooldown floor. Neither official line says it is the trigger tick rate, so the community reading stays a reading — but it is now a reading with official numbers to test against. A stopwatch on a real battle is still the only thing that can confirm any of the three rules.

The on-cast vs on-trigger dispute

One thread asks a sharper question than “how many triggers”: does Multicast count as one cast or many? The dispute concerns monsters whose abilities are worded around events — the thread uses Puffloon as its example, whose card text reads “triggers when adjacent…” per the original poster’s screenshot — and whether an effect that reads “on cast” resolves differently from one that reads “on trigger”. The thread’s most specific position, quoted exactly: “Puffaloon says ‘on cast’ not on trigger. Multicast 100 only counts as 1 trigger.” (That commenter spells the name Puffaloon; other posts write Puffloon.) The same commenter adds a history claim no official text confirms either way: “They fixed it in beta to say on cast 3 months ago. They messed up and reverted the wording on release but the mechanics are still On cast.” A reconciliation reading from another reply: “just think of it as, ‘Triggering the whole attack box’ so its triggered the whole sequence of multi cast, but its 1 trigger, not ‘trigger this when adjacent ally casts’”. Nobody in the thread tests any of it, and the two readings still disagree on the only question that matters for builds: whether a trigger-worded support fires once per Multicast hit or once per sequence.

Why a wiki should care: if the two wordings resolve differently, then Multicast multiplies cast-worded effects but not trigger-worded ones — which would reorder half the build advice in the game. If they resolve identically, nothing changes. The thread does not settle it either way, no official text addresses wording, and this page claims no verdict. It is the first thing a controlled test should adjudicate after the base rules.

One piece of official text entered the dispute after this page’s first pass: patch 1.2.0’s QoL notes — “The post-battle stats now count how many times a monster triggered, instead of counting every Multicast cast separately.” The sentence uses both words in one breath, for stats display — which confirms the game’s own vocabulary treats a ‘trigger’ and a ‘Multicast cast’ as distinct counts. It does not settle whether cast-worded and trigger-worded abilities resolve differently, but it is the first official reason to think the distinction is real.

How you get more Multicast

Four sources are officially on the record. The rest are player accounts — the answers under the “x15+ multicast” thread are where the community’s early-stack stories concentrate.

The official four prove the game deliberately sells, buffs and hands out Multicast as a build-around stat — which is what makes the missing rules document so conspicuous. The community accounts, if they survive verification, explain the eye-watering stack counts in clip titles like “31 Multicast”. A complete source list — every monster and trinket that grants stacks, with exact values — still waits on an in-game sweep rather than thread quotes and fan databases.

Combining monsters: the merge question

Searches for how to merge in Batomon Showdown land here because combining and Multicast are entangled — the community’s explanation for huge stack counts is that bonuses pile up through combines. When this page first checked (October 2, 2026), the word “merge” appeared nowhere in official text, and the developers’ vocabulary was “level up” and “evolution”. Patch 1.3.0 (October 6) changed that in its bugfix list, three times over:

“Fixed Twins’ copy missing buffs the merged monster got right after the merge, like Silver Watch’s Cooldown Speed or an Aviarab’s armed charge.”

“Fixed the shop’s merge preview saying LV 3 when buying a Swoonet would chain past level 3.”

“Fixed a Twins copied by Mysterious Mask not making its twin when a Mega Upgrade Disc fired on the same merge.” (1.4.0)

So the record now officially confirms: a merge interaction exists, the shop previews it before you buy, two of the same species can chain levels past 3, and merged monsters carry buffs that other effects can miss. What the record still does not document is the part a Multicast run needs — whether the Multicast bonuses a copy accumulated survive the merge and stack on the result.

What exists beyond that is a consistent player description: buy (or otherwise end up with) two copies of the same Batomon, they combine, and bonuses the copies were carrying accumulate on the result — “when it merges the multiattacks gained get added to the total”, as one commenter puts it in the x15+ Multicast thread. A separate morph-and-fuse thread describes monsters independently turning into the same species and fusing on their own. Those accounts stay unverified, and the mechanics that would make or break a Multicast run — whether carried stack bonuses truly persist, how levels transfer, what a merge costs — are still inside that unverified zone.

The level-up guide treats the level side of the same system, and the Level 4 guide keeps a running table of exactly these community accounts. When the merge interaction is verified in a real run, all three pages update together — and if this section starts pulling its own search traffic before then, it graduates into a dedicated merge page rather than a subsection.

Patch 1.1.0 slowed the whole engine down

If multicast-and-cooldown builds were a niche, the developers would not have spent a balance patch on them. Patch 1.1.0 (September 22, 2026) nerfed the entire cooldown-trinket family by name — Quick Bell, Quick Flag, Tempo Charm (5% → 4%), Speed Whistle, Silver Watch, Speed Crest, Blitz Bell, Haste Crown, Haste Orb, Momentum Flag and Alpha Crown — and also trimmed Boomagon, the game’s most popular monster, whose power rides the same fast-cast economy. Alpha Crown’s rarity moved up to Mythical in the same breath.

For this page’s topic the nerf wave is indirect evidence: the developers visibly agree that trigger speed was the strongest axis in the game, even though the patch notes publish the trinket percentages and never the trigger math underneath. For build planning the practical takeaway is date-stamped: every cooldown value and Multicast interaction discussed above describes patch 1.1.0, and the developers have said balance patches are planned roughly every two weeks — so verify the current numbers before copying a stack-heavy build into ranked. Patch 1.2.0 (September 30) followed a week later and left the cooldown-trinket family and Clawnetic alone — its balance went to monster numbers instead — while quietly adding the first official 0.1-second mention in a bugfix line.

Patch 1.4.0 (October 21, 2026) then gave the topic its most official breadcrumbs yet: the red LIMIT badge for cards at the 0.1-second cooldown minimum, a bugfix for monsters “attacking a fraction of a second off the cooldown their card shows”, a second Zephyrex exclusion — “Fixed Black Feather wasting its Multicast on a Zephyrex” — and a second tax on Aviarab, the Flying multicast enabler (Rarity Uncommon → Rare, Cost 25 → 30, “still looking like the strongest Uncommon in Jinto even after the nerf last patch”). The developers are still tuning the multicast axis hard, and still publishing no rules for it.

Multicast showcases from the community

Three videos carry the Multicast conversation. They demonstrate outcomes, not rules — treat their builds as leads to test, not as confirmation of the consensus above. View counts are as of September 27, 2026.

Haelian — Do we think 31 Multicast is enough? — YouTube

Haelian — Do we think 31 Multicast is enough?

Danagast — I Broke Batomon Showdown with 0.0s Cooldowns — YouTube

Danagast — I Broke Batomon Showdown with 0.0s Cooldowns

Haelian — So. Much. Multicast!!! — YouTube

Haelian — So. Much. Multicast!!!

The “31 Multicast” and “0.0s cooldowns” titles are also a stress test of the consensus rules — and the 31-stack video now doubles as the loudest public statement of them: Haelian tells his audience that “when a monster cannot attack faster than every 0.1 seconds with multicast, that basically means it takes 3.1 seconds” for his 31-stack monster to finish multicasting — the same arithmetic the Reddit threads use, which is why his build “kind of just doesn’t matter” past a point. If the 0.1-second interval is real, extreme stacks must eventually stop scaling inside a fixed cooldown window — exactly the point where players report wasted stacks. Watching the footage with the three rules in mind is the closest thing to a replication attempt the public record currently offers; a timed screenshot run is still the only thing that can confirm them.