Soul Chained Major Encounters and Trials
Quick answer
Soul Chained achievements expose several major encounter names, but this hub does not invent weaknesses, phases, or rewards before dependable gameplay evidence supports them.
This guide separates confirmed public details from practical advice. It does not present unconfirmed exact values, hidden systems, or unpublished rewards as facts. Official Steam and developer links are listed in the footer for context.
Quick answer
The Tower of Purgatory contains deadly trials and major encounters. Launch achievement names now provide a safer starting list of named encounters, but they still do not prove full encounter order, phases, weaknesses, or reward tables.
Use this as a major-encounter hub, not a full strategy index. Individual encounter guides should wait until there is real gameplay evidence or search demand for that encounter.
Confirmed encounter structure
| Field | Confirmed information |
|---|---|
| Location | Tower of Purgatory |
| Progression unit | Deadly trials |
| Major encounters | Present |
| Achievement-exposed names | Tower Warden, Grundle The Defiler, Bibiyel The Enslaver, Heart of The Mountain, Gerth The Executioner, Humble Guide of Purgatory |
| Strategy status | Names are useful; phases, weaknesses, and exact order still need live evidence |
Encounter names currently worth tracking
| Encounter or achievement clue | Conservative note |
|---|---|
| The Tower Warden | Linked to the Attrition achievement |
| Grundle The Defiler | Linked to the Pillage achievement |
| Bibiyel The Enslaver | Linked to the Slavery achievement |
| The Heart of The Mountain | Linked to the Razed Earth achievement |
| Gerth The Executioner | Linked to the Autocracy achievement |
| The Humble Guide of Purgatory | Linked to the Not so humble... achievement |
These names are enough to support one central encounter hub. They are not enough to publish separate encounter guides with mechanics unless a player-facing source confirms the fight behavior.
How to use this index
- Follow the Tower route as the confirmed progression spine.
- Enter each trial prepared to manage stamina and the Soul Chain's effect on team position.
- Use the live game order to identify the next encounter; the available official descriptions do not establish a dependable named sequence.
What can be planned now
The confirmed structure supports preparation at a general level. Players can practice stamina management, attacks, blocking, parrying, rolling, weapon handling, and group movement around the Soul Chain. Those systems provide a sound checklist before a major encounter even when its exact name and behavior are not published.
In co-op, choose a player to call large movements and reserve a clear retreat direction. Avoid having the entire group spend stamina aggressively at the same time. A stable formation gives each person more room to observe the encounter and choose a defensive response.
First-attempt observation checklist
- Identify the usable space before committing to a long attack.
- Watch how the encounter signals danger without assuming a specific timing value.
- Keep enough stamina for a block, parry attempt, or roll.
- In co-op, note whether group movement removes another player's defensive space.
- After failure, name the first decision that went wrong and change only that decision.
The purpose of the first attempt is to learn a repeatable pattern from the live game. This page does not invent phases, damage types, or weaknesses that are absent from the official descriptions.
Solo preparation
Solo play removes human coordination from the equation, which makes individual timing easier to inspect. Test the reach and stamina behavior of the weapon available to you, then practice leaving a defensive option after a short offensive sequence. Keep the route simple until you can explain why an attempt succeeded or failed.
Co-op preparation
The Soul Chain makes position a shared resource. Before the encounter, agree on who will call movement and which direction remains open for retreat. If a player is preparing to block or parry, avoid sudden movement that changes their location. If someone needs to roll, keep the intended lane clear.
After a failed attempt, regroup away from immediate danger. Discuss one observable problem—stamina, timing, spacing, or route choice—and adjust it. Changing several weapons, positions, and tactics simultaneously makes the next result harder to interpret.
How to record a live encounter
When the game supplies dependable details, record only what is visible: the displayed name, Tower position, clearly observed phases, explicit weaknesses, and stated rewards. Separate a consistent observation from a one-time impression. A weakness should not be listed merely because one attack appeared effective during a single attempt.
This cautious method allows the index to become more specific after release without turning guesses into permanent advice. It also accounts for balance or content changes between builds.
The unresolved trial count
The developer site describes five trials, while the official demo description says six. Both are official sources, and neither resolves the discrepancy. The final live sequence or a later developer statement should take priority. Until then, use the Tower's presented progression rather than expecting a particular numbered encounter.
Common planning mistakes
- Assigning names or locations that do not appear in official material.
- Treating the five- or six-trial description as conclusively resolved.
- Building around exact damage or stamina values before they are published or observed.
- Assuming a strategy from one weapon applies to the complete roster.
- Letting several co-op players change direction without a shared call.
Frequently asked questions
Is there a complete list of major encounters?
No authoritative complete named list appears in the official sources used here.
Are weaknesses or rewards known?
Not reliably enough to publish as fact. Use explicit live descriptions and repeatable observations when the game is available.
How should a group prepare?
Practice controlled movement, reserve stamina for defense, keep retreat space open, and adjust one observable problem after each attempt.