The current materials identify a tutorial slime encounter, the story fights against Goblin King and Forest King Aelwynor, repeatable Deed encounters, and two legacy Demo bosses. This page separates current Early Access progression from older or generic boss evidence.
Official boss-system descriptions, dated Early Access guides, community discussion and June Demo gameplay reviewed September 16, 2026. Exact health values, complete roster and universal weaknesses are not established.

On this page ⌄
Named encounters supported by the current material
| Encounter | Current evidence and progression role |
|---|---|
| Tutorial slime boss | Existence appears in launch-day gameplay and a Steam discussion; the reviewed material does not provide a stable name or full tactic table. |
| Goblin King | Current Early Access story encounter late in the goblin chain; Hoard King’s Fall and Tamsin’s explosive lead into it. |
| Forest King / Aelwynor | Current Early Access story endpoint after Crown of Thorns and Forest Path; the captured guide reports post-fight rewards. |
| Alpha Wolf / Corrupted Beast Returns | Repeatable Deed or Bounty examples in the current material; these are farming contexts rather than a complete unique-boss roster. |
| Monstrous Droop / Corrupted Treant | Confirmed in June Demo gameplay and legacy fan material; keep them labeled Demo evidence rather than current EA progression. |
Where the major story bosses sit
| Story signal | Boss implication |
|---|---|
| Find the Goblin Hideout | Earlier navigation stage; the boss is not ready yet. |
| Clear the Raid | The hideout has been reached; continue the goblin chain. |
| Hoard King’s Fall → collect Tamsin’s explosive | The Goblin King setup is active. |
| After Goblin King → return to Corin | The goblin stage has handed back to the deeper Wildwood story. |
| Crown of Thorns → Unlock the Door / Confront the Forest King | The Forest King route is active; Forest Path is the approach. |
| After Forest King | The current linear Early Access story ends and repeatable or personal progression takes over. |
Prepare the attempt around the build you already have
Mudtek’s design guidance recommends scouting what damage type is causing trouble, returning home, choosing useful food or potions, resting and pushing again. The generic boss guide adds the same discipline: keep stamina for a defensive action, read the opening pattern and use short punish windows.
[8][9]- Restore healing and relevant combat-item charges before a difficult story encounter.
- Fill Nourishment and bring cures when the route or boss has already shown a dangerous status effect.
- Confirm that attributes, spells, equipment and the pet all support the same combat plan.
- During the first attempt, prioritize recognizing attack range, delay, follow-up and recovery over maximum damage.
- In co-op, assign space and responsibilities before entering; a community report says enemy and boss stats scale by the number of players within a radius, but no formula is confirmed.
Tutorial slime boss: existence only
The launch-day gameplay record and Steam discussion support the existence of a tutorial slime boss. The available evidence does not provide a stable encounter name, reward, phase table or measured weakness, so use it as an early combat-learning check rather than a documented build target.
[1]Goblin King: unlock cue and fight decisions
The Goblin King guide reports that the encounter becomes imminent when Hoard King’s Fall asks for Tamsin’s explosive from the camp. If the tracker still says Find the Goblin Hideout, keep solving the route first. After collecting the explosive, stay with the goblin storyline and return to Corin after the victory.
[2]- Arrive rested with healing, Nourishment and combat-item charges restored.
- Wait for a committed heavy swing or another readable sequence to finish, then use a short damage window.
- Parry attacks whose timing you recognize; dodge uncertain animations instead of forcing every opening into a parry attempt.
- When extra goblins enter, preserve room to move and reduce the added pressure when it begins to interfere with reading the King.
- Use the post-fight Corin handoff to continue toward the deeper Wildwood route.
The captured Brawler example reached 16 Bleed stacks in a later rematch. That is an observation from one build and version, not a damage requirement or a universal target.
[2]Forest King Aelwynor: Poison, hazards and the Fey
The Forest King guide reports Aelwynor as the final boss of the current linear Early Access route. Bring Poison Cure when the approach has made Poison relevant, keep the floor readable, and remove the Fey when its extra pressure makes the arena harder to manage.
[3]- Use the opening moments to read the arena before committing to a long sequence.
- Cure Poison instead of trying to out-heal its continuing drain; avoiding the hazard remains better than spending a charge.
- Prioritize safe ground over one extra melee attack when floor hazards are active.
- Kill the Fey when it is causing missed dodges, poor positioning or repeated healing; keep the boss target when the Fey is not meaningfully changing the run.
- Use Bleed or another persistent effect when the build needs to keep damage moving while you reposition.
- Treat uncertain parries as optional and preserve the attempt when healing is low.
The successful Brawler example reached 18 Bleed stacks and finished with one potion. The guide treats those numbers as that build’s combat record, not as entry conditions for the encounter.
[3]Rewards and what follows the final story fight
The captured Forest King guide reports an additional Forest Heart charge, Forest King Tine and three new spellbooks after the victory. It also reports no immediate mandatory story destination afterward. Those rewards and the endpoint are source-attributed observations from the current guide material.
[3]How to read Demo bosses and incomplete roster claims
Monstrous Droop and Corrupted Treant are supported by June Demo gameplay and related fan material. They can be useful historical references, but the Demo and Early Access are separate product states. Do not combine their names with current EA encounters to create an all-boss list.
[5]