Slotbound Tier List for Starter Units

A Slotbound tier list for five Normal starters, with role-based priorities, explicit criteria and version notes for older unit recommendations.

This Slotbound tier list ranks five Normal starters for a narrow job: helping a new player build an understandable early army. Warrior and Mage are our A-priority foundations; Archer, Spearman and Cavalry are B-priority options whose value depends on the role you need. These are editorial priorities, not measured win rates or a ranking of all 155 community-listed unit entries.

The reason for the narrow scope is practical. A complete endgame ranking needs current class skills, equipment, imprints, unlocks and repeatable results. We do not have a controlled comparison of those combinations. A clearly bounded starter list is more useful than invented S-tier certainty.

The starter priority table

Priority Unit Why inspect it early Change the priority when…
A Warrior A straightforward melee foundation and an accessible absorption reference Your army already covers that role and needs ranged contribution
A Mage Its promotion tree offers a Shaman or Healer branch to inspect The current board needs immediate survival rather than another ranged unit
B Archer A clear ranged starter with an attack-sequence imprint The board gives it time to attack and needs that role
B Spearman A melee route with a piercing imprint Additional-target opportunities or its promotion branch fit your plan
B Cavalry A mobile melee route with a defeat-triggered imprint Your actual encounter and receiver can use that trigger

No C or D tier is assigned here. The evidence does not justify calling an available starter useless. B means conditional priority in this learning framework, not “feed it immediately.”

How the ranking was made

We used the documented starter roles, promotion branches and imprint triggers, then considered how easily a beginner can make a clear decision around them. Warrior and Mage provide an understandable contrast between a melee foundation and a ranged unit whose branches should be inspected for different roles.

The list does not calculate DPS from the displayed attack-speed number, assume a fixed enemy target order or invent a win-rate sample. It also does not equate base attack with total value. Unit traits, development and the surrounding army can change the comparison you see in a real run.

The underlying values and branch names are linked on each unit page. Treat the ordering as an opinion with explicit criteria. You can disagree with the priority for your board without contradicting the factual reference.

Official Slotbound gameplay screenshot showing the game's unit and battlefield presentation
Official Steam media, © Optima Arch. A unit's class name alone does not describe all the development and effects on a particular run.

How to use A priority

A priority means “inspect this as a foundation when learning,” not “preserve every copy.” If you have several units serving the same job, the next useful decision may be consolidation or a different role. A priority should help you ask a question, not remove the need to look at the board.

For Warrior, check whether the army needs a melee presence and whether the intended receiver can keep attacking. For Mage, inspect the available branch and what the army lacks. Do not choose Healer solely from its name without reading the current class text, and do not assume the Shaman route is automatically the right damage choice for every encounter.

The beginner guide shows how to move from “this is a good unit” to “this unit fills the role I am missing.” That is the decision this tier list is intended to support.

When B becomes the right choice

An Archer can be a sensible priority when the army already has a working melee structure and needs ranged attacks. A Spearman can be worth inspecting when its branch or additional-target effect fits the task. A Cavalry can be useful when its actual movement, class route and trigger suit the board.

Choose the missing role. If your present army needs a role supplied by a B-priority unit, choosing another A-priority duplicate may make the composition less complete. The table should never make you ignore the unit that solves the immediate problem.

Likewise, do not automatically absorb a B-priority unit into an A-priority one. The donor disappears. If it was the only unit performing a needed job, the receiver’s gain must be evaluated against that removal. Use the absorption checklist before treating any tier label as a permission to merge.

Why rarity is not the tier list

Rarity, stars and class are separate things to inspect. A Normal starter with development is not the same game state as a fresh higher-grade summon, and a promoted class is not interchangeable with every other class in the same symbol family.

You also have to distinguish a unit as a fighter from a unit as an imprint donor. An effect might be useful on another receiver even when you do not intend to keep the donor as a separate fighter. Conversely, consuming the donor can be a mistake when its presence is doing more for the army than the transferred effect would.

The imprint guide uses triggers and receiver roles to make that comparison. It avoids declaring an extra-target effect universally superior to a single-target one, because the enemy arrangement determines whether the extra component has an opportunity to matter.

A note on Deadeye and old rankings

Deadeye’s attack was reduced in v1.0.0 (7). The developer did not publish the amount in that announcement. A pre-patch video showing exceptional damage is therefore evidence about that recorded run, not a measurement of the current version.

This page does not respond by inventing a new Deadeye tier. A reduction alone does not establish that the unit is bad, and an old demonstration alone does not establish that it remains the best. Check the current class text and the build’s supporting effects before drawing either conclusion.

The same caution applies to demo-era rankings. The Core system was substantially rebuilt during the demo, and later updates changed progression and Fate Stone quests. Match the game’s version and the recommendation’s actual conditions before copying a result.

How to compare your own candidates

Pick the job first: survive, finish a durable enemy, handle a group, or support another unit. Then compare only candidates that might perform that job. Check their current development and effects, not just their base entry in a directory.

Use the last battle as evidence. If the army is losing because a carry dies immediately, ask which choice improves its ability to act. If the carry remains alive but cannot finish the enemy, ask about damage and trigger availability. These observations are more specific than promoting a unit simply because it sits in a higher row on this page.

Finally, account for what you already own. A hypothetical Rare unit is not an available solution until it is actually in the run. The Hard-mode build notebook shows a named player example in which the final carry plan emerges after an opening army, rather than existing from the first spin.

Sources and update policy

Starter facts are attributed individually in the unit directory, using Wikily’s unit references checked 17 November 2026. The Deadeye change is documented in v1.0.0 (7). Rankings are our stated editorial judgement. We will expand the scope only when class-specific, version-matched evidence supports a broader comparison.

Keep your next decision simple.

Look up a unit · Plan a build · Check the latest covered patch

Evidence-based editorial guidance. We have not independently play-tested these builds. How we check and update this guide.