Ascension calculator

Forge, Mounts, Pets and Skills ascension math — from the actual game configs, not a guess. Everything below recomputes live as you type.

Forge

Forge levels run 1–35. The 34 upgrades in the config each take you from one level to the next, so all 34 together carry you from level 1 to level 35 — reaching 35 is what unlocks ascension, which resets the forge back to level 1 and multiplies equipment Damage & Health. Ascension itself only costs Coins — no gem cost exists in the config for it.

Current forge level

Target forge level

Target item Age instead (optional, overrides target level)

Cost reduction

Timer speed

Coins needed

–

Build time

–

forging in real time, no skips

Gems to skip

–

Item Age odds at the target level

What forging actually drops at that level — not a threshold, a distribution.

Ascension payoff

Gate: reach forge level 35 (all 34 upgrades complete). Cost is flat regardless of how you got there, every time.

Assumptions and sources

All summon-banner odds, level thresholds, ascension costs/values, forge levels, and item-Age drop chances are read directly from the game's own shipped config (MountSummonConfig.json, EggSummonConfig.json, SkillSummonConfig.json, AscensionConfigsLibrary.json, ForgeUpgradeLibrary.json, ItemAgeDropChancesLibrary.json, TechNodesLibrary.json / PlayerTechTreeNodeValuesLibrary.json) — version . No values here are estimated.
Mounts/Pets/Skills results are an expected-value simulation, not a dice roll: each summon adds its exact probability of each rarity, so results are deterministic and reproducible, matching the same calculation the Forge Master helper app uses internally.
Reaching banner level 100 with an ascension still available auto-ascends for free (matching the game: ascension has no separate summon-currency cost) and resets the banner to level 1 for the next phase — shown as a phase breakdown, not folded into one number.
Rarity is a banner-odds tier, not a level threshold — a level doesn't "unlock" a rarity so much as raise its chance from 0%. There's no level at which a rarity becomes guaranteed except Common at level 1.
Skills have no extra-chance tech node in the game's config — only a cost-reduction node exists for that track, so the extra-chance input is intentionally omitted from the Skills tab. Pets have the opposite gap: no cost-reduction node, extra-chance only.
Cost reduction is clamped at 90% — matching the in-app calculator's own clamp.
Every tech-tree input here is the player tree only — the separate clan tech tree is a different system entirely and isn't modeled.
Each tech stat is actually 5 identical node copies, each independently leveled 1–5 (25 total levels per stat) — every level within a stat adds the same fixed amount (e.g. 1% per level for cost-reduction nodes, 2% per level for chance/speed nodes), confirmed directly from the config's own per-level tables. On Mounts/Pets/Skills, the "nodes maxed" input is how many of those 5 copies you've fully leveled to 5 — each one worth the table's full per-node value (5%, 10%, etc.) — so 5 nodes maxed is the true cap (25% for cost-reduction, 50% for chance), not the 5%/10% a single node alone would give. Forge's two node inputs skip that abstraction entirely and just take the resulting percentage directly (0–25% cost reduction, 0–50% timer speed).
Skills has a second way to fill in its cost reduction: enter the actual discounted price you see in-game for a batch of tickets (the size of one summon) instead of a percentage — e.g. paying 166 for 5 tickets against a base of 200 works out to a 17% reduction, and the calculator does that division for you.
Mounts/Pets/Skills calculations always start from ascension 0 relative to whatever level and progress you enter, and "Cost to a target" targets a level within that same pass — there's no ascension-tier input anywhere on these tabs, since the summon-banner odds and level thresholds never depend on which ascension tier you're on, only on your current level.
Reaching level 100 alone is ascension-ready — confirmed directly from the decompiled client (Game.Logic.SummonModel.IncrementSummonCount, RVA 0x77b0680), not inferred. The entry it consults to level up is the destination level's own row, not the level you're leaving — e.g. going from level 1 to 2 spends Levels[1]'s requirement, not Levels[0]'s (so Levels[0], the entry for level 1, is never actually spent — level 1 is just the free starting point). Since the list only has 100 entries, there's no Levels[100] to spend on a "leaving level 100" step — the decompiled bounds check fails exactly there, confirming level 100 is a hard ceiling with nothing further to fill. Also confirmed directly (SummonModel.Reset, RVA 0x77b0758): ascending zeroes progress completely — it never carries over. "Ready for ascension" is a convenience, not a workaround for an ambiguity: checking it just locks the level field to 100 and starts the calculation fresh at level 1 of the next ascension, skipping the (now-optional) step of resetting the fields yourself.
Item Age names (Primitive…Divine) come straight from the game's own localization strings, not a placeholder numbering — a level doesn't "unlock" an Age any more than it unlocks a rarity; it just raises that Age's drop chance from 0%.
Forge levels run 1–35, not 1–34: the 34 upgrade entries in the config each carry you from one level to the next, so all 34 together span level 1 → 35, and 35 is exactly where ascension unlocks. ForgeUpgradeCost (a genuine coin-cost discount) and ForgeTimerSpeed (a build-time speedup, applied as duration ÷ (1 + bonus) — a divisor, not a percent-off) are the two forge tech nodes modeled here. A third node, FreeForgeChance, exists in the config but governs free item crafts (hammers), not upgrade cost or time — it's unrelated to forge leveling and is deliberately left out of this tab.
Forge ascension resets forge level back to 1, same as the other three pillars, and each of forge's 3 ascension steps costs the same flat 3,000,000 Coins regardless of which one — shown in the Ascension payoff table below. A full-Apex projection isn't offered on the Forge tab: at 34 upgrades and up to 121 days per cycle, three cycles is a months-to-years-long plan, not something worth reducing to a single number.