On this page
OVERVIEW
Quick summary
Fate of the vaal was the 0.4.0 league whose signature content is a buildable atziri temple you place beacons that spend energy to construct rooms deeper rooms lead to chambers and ultimately the vault and atziri herself
At launch the system had two serious problems fragile room connectivity and automatic destabilisation that could brick a run without warning both were addressed by 0.4.0d and 0.4.0e so current temple behaviour is materially different from launch week videos
- Beacons spend energy to place and upgrade rooms
- The architect builds and defends rooms atziri is the final boss
- 0.4.0d fixed room connection logic and death retry flow
- 0.4.0e removed automatic destabilisation and added warnings
- Old temple guides from launch week describe removed behaviour
IMPACT DASHBOARD
System flow
Beacons
Core loopBeacons are placed in the Temple area and consume Energy to construct rooms. Their placement determines which rooms connect.
Energy
ResourceEarned from cleared rooms and league activities; gates how many rooms you can build and upgrade.
Rooms
BuildableEach room has a function (reward, hazard, boss antechamber). Connectivity was the launch-week pain point.
Chambers / Vault
Deep progressionChambers gate the Vault; the Vault leads to Atziri, the Red Queen.
BOSS IMPACT
Boss access: Architect, Atziri, Chambers
The Architect
Builds and defends Temple rooms. After 0.4.0e its pacing was tuned so it is a threat, not a run-ender.
Treat as pacing threat; do not over-invest in anti-bricking plans.Atziri, the Red Queen
Final boss reached through the Vault. Her identity is unchanged, but arena access follows post-0.4.0d connection rules.
Update access guides to current connection rules.Vaal-touched rares
Corrupting modifiers inside Temple rooms; part of the league's risk/reward.
Map under Endgame/Temple, not a separate league.ITEM IMPACT
Reward map
Currency
Orb of Sacrifice
Central to Temple crafting and Vaal-corruption workflows introduced with the league.
Currency
Vaal Orb
Its corrupting role is consistent with earlier behaviour, promoted alongside the Vaal storyline.
Base item
Talisman
Shapeshift weapon base introduced in the same 0.4.0 window; frequently drops in Vaal content.
CHANGE EXPLORER
0.4.0d fixes
Room connection logic
0.4.0d rewrote how placed rooms connect, reducing unreachable rooms and dead-end paths.
Death-retry flow
Improved feedback and retry after death inside the Temple so a wipe did not silently corrupt room state.
Map-state feedback
Added clearer indicators for which rooms were connected versus pending.
CHANGE EXPLORER
0.4.0e fixes
Removed automatic Destabilisation
0.4.0e deleted the auto-Destabilisation that could brick a Temple without warning; rooms now only destabilise after explicit warnings.
Architect pacing
Tuned Architect pressure after Destabilisation was removed so the league kept tension without run-ending randomness.
Temple UI warnings
Added explicit warnings before a room destabilises, replacing the silent auto-brick.
THEN VS NOW
Then vs Now
Room connectivity
0.4.0 launch: rooms frequently disconnected or became unreachable.
0.4.0d connection logic keeps rooms reachable; map feedback is explicit.
Destabilisation
0.4.0 launch: Temple could auto-destabilise with no warning.
0.4.0e removed auto-Destabilisation; rooms warn first.
Death inside Temple
0.4.0 launch: a death could silently corrupt room state.
0.4.0d retry flow preserves state and gives clear feedback.
CURRENT APPLICABILITY
Current applicability (0.5.4e)
| Mechanic | Status | Current rule (0.5.4e) | Superseded by | Read |
|---|---|---|---|---|
| Beacon / Energy room building | Still current | Core Temple loop unchanged in identity; build rooms with Beacons spending Energy. | — | Atziri Temple guide |
| Room connectivity rules | Changed later | 0.4.0d rewrote connectivity; later map updates may have adjusted further. | 0.4.0d, 0.5.x map updates | Atziri Temple guide |
| Automatic Destabilisation | Removed | Removed in 0.4.0e; rooms no longer auto-brick. | 0.4.0e | Fate of the Vaal guide |
| Atziri as final boss | Still current | Atziri remains the Temple's final boss in 0.5.4e. | — | Atziri boss page |
COMMUNITY EVIDENCE
Community evidence
Half my Temple was unreachable and then it destabilised with no warning.
Now I actually get a warning before a room goes.
KNOWN ISSUES
Troubleshooting
- TrackingA room shows 'pending' and will not connect — verify Beacon placement and Energy; this is expected pre-connection, not a bug.
- OpenAtziri unreachable — confirm Chamber routing follows post-0.4.0d connection rules, not launch-week paths.
- FixedLegacy videos show auto-Destabilisation — those are pre-0.4.0e and do not reflect current rules.
AFFECTED CONTENT
Affected content
| Content | Type | Trigger | Action | Status |
|---|---|---|---|---|
| Atziri Temple guide | Guide | 0.4.0d/e connection + Destabilisation changes | Rewrite connection and retry sections; remove auto-Destabilisation. | Queued |
| Atziri boss page | Boss | Arena access rules | Update access to post-0.4.0d rules. | Reviewing |
| Orb of Sacrifice item page | Item | Temple crafting | Document Vaal-corruption workflow. | Queued |
Historical video
Official Path of Exile 2
0.4.0 Fate of the Vaal — Temple build
What to watch for: Launch-week Temple showcase; note the auto-Destabilisation shown was removed in 0.4.0e.
Open source ↗QUESTIONS
FAQ
Why do old Temple videos show rooms destabilising by themselves?
That was 0.4.0 launch behaviour 0.4.0e removed automatic destabilisation rooms now warn before destabilising
Are Beacons and Energy still how the Temple works?
Yes the beacon energy room building loop is still the core temple mechanic in 0.5.4e only connectivity and destabilisation rules changed
Is Atziri still the final boss?
Yes atziri the red queen remains the temple s final boss only the arena access path changed after 0.4.0d
SOURCES
Sources and verification
Information is compiled from public web sources and in-game observations; some visuals are original editorial diagrams. External information and images remain the property of their authors or platforms; contact us for removal requests.

