Start with the unit you want to keep
An absorption decision redirects an incoming or expendable unit into a recipient. Before dragging or confirming anything, identify the class and copy you are developing. Its useful traits, army role and next checkpoint are more informative than whether another unit has a higher-looking rarity colour.
Then identify a donor you can afford to lose. A donor is not automatically worthless because another unit can absorb it. It may be the only defender, a distinct faction type or a support recipient that keeps the army’s other pieces useful. Compare the whole exchange rather than one card in isolation.
Use the prompt as a decision point
The absorption prompt lets you inspect the proposed recipient and the choice being offered. Confirm both before committing. If your intention was merely to move a unit, check the active mode and cancel the prompt. That is a normal correction to an input choice, not a reason to rush through a destructive action.
The developer added a manual absorption lock in the 0.3 update. A protected unit can be intentionally excluded from use as material. Before concluding that absorption is broken, inspect the lock state using the current interface; we do not invent a universal lock-button position or shortcut.
Compare an Imprint with the displayed conversion
Choose an offered Imprint because its actual effect fits the recipient. Check what it triggers from, whom it affects and whether the current build supplies its prerequisite. If the level conversion is more useful, use the number shown on that particular prompt rather than a fixed gain copied from another run.
This is especially relevant near an awakening checkpoint. A displayed conversion can cross the target even if it lands above the threshold. The arithmetic can clarify the result, but it does not establish that sacrificing this donor is worth the army role you lose.
Promotion progress is not the same as awakening
The current recipient has a class and a promotion progress display. A later awakening choice belongs to the resulting class and its own state. Do not treat every level gain as a new class, or assume a promotion automatically completes the recipient’s next awakening.
For the recorded Ringmaster route, inspect the actual class before using its known 30, 60 and 100 checkpoints. A Ferret Tamer still needs its promotion choice; another class may have a different or unverified awakening set. Keep the next desired screen explicit in your plan.
A blocked spin needs a state check
A full-army situation can leave an additional unit waiting for a decision, and older community reports note that units can overlap. Inspect what is actually present before trying to solve the counter by sacrificing an important member at random. Decide which recipient would benefit, then resolve the matching donor choice carefully.
The developer also notes that some traits exclude a unit from the maximum-slot count. A raw headcount above the visible cap is therefore not enough to identify a bug or its cause. Check the trait and lock state, not just the number of sprites you can count.
Make one better exchange next run
If the army weakened after absorption, identify what disappeared. Did you remove your only body in front, a relevant Forest type, useful damage or the ally a support skill was helping? That is a more actionable observation than simply concluding that the recipient needed more levels.
For the next attempt, change one exchange. Keep the same main recipient if it is working, preserve the missing role and compare the result at a similar stage. This gives you a cleaner way to learn than replacing every donor rule, Core and class route together.
THE NEXT USEFUL CHECK
Before the next choice.
Page-only preparation checks. Reloading clears these ticks.QUICK ANSWERS
One more useful detail.
Does every donor provide the same number of levels?
No fixed conversion is established here. Read the gain on the current prompt; the recorded +8 example is specific to that exchange.
Does being above the visible unit cap prove the game is broken?
No. A developer reply identifies traits that can exclude units from the maximum-slot count. Inspect the actual state before concluding the counter is wrong.
THE SOURCE DESK / DEMO 0.4.1 CONTEXT
The reference behind
the next decision.
The publisher establishes the demo systems and updates. Detailed unit and effect examples are attributed 0.4-era observations. Our build plans and tier letters are editorial learning advice, with no claimed playtest or damage benchmark.
Open the references and their scope
- PublisherOptima Arch — official Slotbound Demo ↗
The 3×3 machine, absorption, Random Stats, Imprints, Items and Cores; demo identity.
- Independent guideSlotbound Hub — donor and recipient reference ↗
Absorption direction, displayed level gains and lock-state checks.
- Developer replyDeveloper reply — absorption lock and slot exceptions ↗
An absorption lock can explain a reported block; some traits exclude a unit from the maximum-slot count.
- Player recordingDabble — Jester and Ringmaster playthrough, 9 October 2026 ↗
A developed-character 0.4-era Open Forest Hard run. Exact running build not visible; observations are not a fresh-save test or guaranteed result.
