What the planner calculates
The tool builds one target-rarity schedule from six numeric inputs: current base percentage, the number of flat failures before an increase, the additive percentage-point step, current consecutive failures, planned eligible summons, and owned eligible Shards. It multiplies the conditional miss chances until the first target or the end of the plan. It does not predict which Champion appears within a rarity.
Current rates belong to the Summoning Portal
Plarium's Summon FAQ says current drop-rate information is available under Summoning Portal > i. That makes the in-game panel, not a timeless Shard-name selector, the numeric source. When an event changes the displayed rate, enter that effective rate directly and preserve the event capture in the source note.
Mercy counter ownership is part of the model
The official Mercy System page states that counters are tracked separately for each Shard type and rarity. A matching Epic or Legendary result resets the applicable rarity/type counter, while another counter can remain unchanged. Combining lifetime summons, different Shards, or Epic and Legendary misses creates a counter the game does not use.
The counter is not visible to LootCalc
Plarium explicitly says the live Mercy count is internal and not displayed. LootCalc has no account access, API, import, or hidden tracker. Record the personal log behind the current-failure input and describe it as an estimate when history is incomplete. A precise-looking output cannot make an uncertain counter exact.
Additive means percentage points
Plarium distinguishes additive from multiplicative increases. In this model, a base 8% plus one entered 2-point step is 10%, not 8.16% or 16%. The first step applies to the next eligible summon after the entered flat-failure count. This explicit wording prevents the former off-by-one behavior in the site's old curve.
No separate hard-pity preset
If the entered additive schedule eventually reaches 100%, the planner displays the first mathematical 100% step implied by those inputs. It does not separately force summon 20 or 220. A failure count at or beyond the entered 100% step becomes a diagnostic rather than being reduced modulo a guessed cycle.
Temporary events remain separate evidence
A rarity-rate event, boosted Champion pool, Guaranteed Champion Event, and Extra Legendary Event answer different questions. The official FAQ says, for example, that an Extra Legendary bonus does not reset Mercy. The calculator therefore has no generic event switch. Capture the live event terms, update only the input they actually change, and do not treat a named-Champion boost as a rarity-rate multiplier.
Shard inventory is not a spending recommendation
The resource output subtracts already-owned eligible Shards from the planned count. It does not assign cash, gem, pack, or Champion values and does not advise whether to summon. Plans extending beyond the first target boundary retain their inventory count, but their later probability requires a new scenario after the real result.
Continue with the evidence workflow
Use the RAID Mercy Evidence Guide to capture Portal details, keep rarity counters separate, and log state changes. The stateful probability guide explains why the product uses changing conditional rates rather than a single fixed-rate shortcut.