Mechanic reference

Strength scaling is one of the cleanest evergreen mechanics to explain early

This page exists to explain a simple damage-growth concept in plain language, then route players into the Ironclad pages that apply it.

What strength scaling means on this site

Strength scaling is a simple way to describe a run where damage grows as the fight or run goes on, instead of staying flat from the first turn to the last.

That makes it a strong early mechanic page because it is easy to explain, easy to connect to Ironclad coverage, and useful even before deeper card-level guides exist.

What players should actually look for

At a launch-week level, the important lesson is not "pick every scaling card you see." The better lesson is:

build toward damage that keeps mattering later
keep enough defense to survive until that payoff arrives
avoid stuffing the deck with cards that do not support the same plan

What this page should not overclaim

This page should not pretend the best strength package is already fully solved. A useful first version is about pattern recognition, not a fake final answer list.

That is why the page works best as a mechanic reference, not as a replacement for a class build guide.

Best follow-up pages

Once a player understands the basic idea, the next useful route is usually one of these:

Mechanic snapshot

A launch-friendly damage-growth mechanic that gives Ironclad coverage a clear evergreen teaching page without pretending the late-game meta is already solved.

What to look for

damage keeps improving as the run goes on
the deck still leaves room for enough block and consistency
card picks support a readable, low-friction plan instead of a fragile combo

What to avoid overclaiming

overcommitting to scaling can make early hallway fights slower than they need to be
a strength plan still needs enough defense to survive until the payoff matters
launch-week guides should not pretend every scaling package is already fully optimized

Related routes

Where this mechanic connects inside the site

Mechanic pages should bridge class identity, build guidance, and the parent hub instead of staying isolated.

hub

Slay the Spire 2 Mechanics

A Slay the Spire 2 mechanics hub for evergreen strategy concepts like strength scaling, card sequencing, and orb management.

entity

Slay the Spire 2 Ironclad

Learn what Ironclad offers in Slay the Spire 2 and why it is one of the easiest launch-week classes to recommend.

editorial

Slay the Spire 2 Ironclad Build Guide

A beginner-first Slay the Spire 2 Ironclad build guide focused on simple damage, reliable block, and a conservative launch-week recommendation.

hub

Slay the Spire 2 Classes and Characters

See all Slay the Spire 2 classes at launch, including returning characters and new classes, then jump into class guides, beginner builds, and the current tier list.

hub

Slay the Spire 2 Builds

Browse Slay the Spire 2 builds for every class, compare safe starter builds, and find early co-op build ideas without overclaiming the launch meta.

Official context

Mechanic pages are editorial reference pages. They should stay anchored to confirmed class identity and launch framing before they grow into deeper card-level coverage.

Mega Crit Early Access launch post

Primary source for launch date, class roster, and launch framing.

Next clicks

The best follow-up pages after this mechanic reference

The next useful route is usually either the parent mechanics hub or the class/build page that applies the concept.

Back to the mechanics hub Open the Ironclad class page

FAQ

Questions a mechanic page should answer simply

A useful first mechanic page explains the concept in plain language and sets expectations about current certainty.

What does strength scaling mean on this site?

It means a plan where damage improves over the run instead of staying flat, usually through effects that make later attacks hit harder than the first few turns.

Why is this a strong first mechanic page?

Because it is easy to explain in plain language, easy to connect to Ironclad coverage, and useful long after launch-week answer pages stop being the main traffic driver.

Should this page claim the final best strength package is already solved?

No. The first version should explain the mechanic clearly while staying honest about how much launch-week build knowledge can still move.