Beyond the promotion
Slotbound awakening: 30, 60 & 100
For Ringmaster, reach level 30 for Awakening I, 60 for II and 100 for III, then choose on the awakening panel. Read the highest awakening already chosen before targeting the next checkpoint. Other classes need their own options checked.
The three checkpoints
Think in thresholds, then inspect the prompt on your unit. At 09:18, the recording shows High Elf’s first awakening locked until level 30 while Dabble explains 30, 60 and 100.
The later Ringmaster sequence follows those checkpoints: Awakening I is shown at level 32, II at 61, and III at 105. Those higher levels are where the unit ended up after gaining levels; they do not replace 30, 60 and 100 as the stated checkpoints.
Level explanation at 09:18 · Ringmaster I at 36:09 · II at 41:26 · III at 45:26
Reach the next checkpoint, then choose on the panel
- Read the level and awakening state on your current unit. A class promotion and an awakening choice are different screens.
- Inspect the level gain offered by the current Absorb conversion. In the recorded example, Ringmaster goes from 24 to 32 after a displayed +8 conversion.
- Use the awakening selection when it appears. The observed Ringmaster panel says Choose Awakening I; compare the options shown for that unit.
The second example goes from level 59 to 61 after +2, then shows Awakening II. A gain that crosses a checkpoint can land above it, which is why the result level and unlock threshold are different.
Use the displayed gain rather than assuming every absorption is worth the same number of levels.
Use the right unit’s awakening options
High Elf’s first requirement is visible at level 30. Ringmaster provides the recorded three-choice sequence. For a class you have just promoted, read its own awakening options before carrying over another class’s plan.
plum reports seeing no Phantom awakening in one run. For that unit, inspect the current options rather than applying Ringmaster’s sequence.
Sources & version
For the 0.4.x demo. Version reference: the official 0.4.1 announcement, reviewed 17 October 2026.
Dabble’s recording is from the 0.4-era demo; its exact running build is not visible.