URGENT: Sacrificial Chamber Logic Failure & Character-Bricking Bug (Global Community Feedback)

Dear Grinding Gear Games Support Team,

I am writing to report a critical, game-breaking bug in Path of Exile 2 (Fate of the Vaal League). I am a content creator on Bilibili . During a livestream of my Atziri Temple construction, I discovered that the Sacrificial Chamber had permanently disappeared from my room pool. After investigating this live with thousands of viewers and cross-referencing with global communities, I found that a massive number of players are suffering from this exact "character-bricking" issue.

1. Data Analysis of Player Loss
Community data shows that this is not a matter of "bad RNG," but a hard logical failure. Affected players have demonstrated extreme persistence in verifying this bug :

Refresh Attempts: Over 200–500+ failed attempts to spawn the room .

Energy Consumption: Players spent 500–1,000+ Energized Crystals without success .

Time Investment: Over 100+ full temple cycles completed (approx. 50–100 hours of gameplay) with zero room spawns .

Failed Recovery: All standard reset methods (killing the Architect/Atziri, resetting the temple grid) fail to fix the character's corrupted metadata .

2. Technical Analysis: Logic Failure
The bug appears to be rooted in two major system flaws :

State Machine Persistence Error: When a player sacrifices the Sacrificial Chamber itself, a "Race Condition" occurs. The physical entity is removed from the grid, but the control logic fails to reset the "In-Pool" flag. The RNG continues to treat the room as "already placed," permanently excluding it from the spawn list .

Decoupling of Items & Rooms: "Sacrifice" room cards (known as "砸卡" in the Chinese community) continue to drop because item drop tables do not check the actual temple state. This creates a frustrating "illusion of utility" where players receive tools for a target that has been permanently deleted .

3. Impact on High-Level Strategy & Economy
Broken "Roman Road" Tech: The Sacrificial Chamber is a vital "surgical tool" for the "Roman Road" or "Snake" layouts. Without it, players cannot optimize their chains, leading to a complete stagnation of endgame progression .

Economic Inequality: Tier 3 Sacrificial Chambers produce Vaal Cultivation Orbs (approx. 7.5 Divine Orbs) . This bug creates a massive, unfair wealth gap between affected and unaffected players, severely damaging the fairness of the league .

4. Massive Community Evidence (Links) This issue has been reported for over a month with zero official response. Below are the core discussion threads from the Chinese, Taiwan, and International communities:
International Community Discussions:
Forum Master Thread (9+ pages): https://www.pathofexile.com/forum/view-thread/3904508 .

Detailed Technical Report: https://www.pathofexile.com/forum/view-thread/3907783 .

Reddit Discussion: https://www.reddit.com/r/PathOfExile2/comments/1qfisay/ggg_can_the_sacrificial_chamber_bug_please_get/ .

Chinese Community Discussions (NGA & Tencent Forums):

Tencent Forum - "Sacrificial Room Not Refreshing": http://poe.game.qq.com/forum/view-thread/374395 .

Tencent Forum - "Vaal Temple Feedback": https://poe.game.qq.com/forum/view-thread/374386.

NGA Forum - "Major Malicious Bug: Sacrificial Room Disappearance": https://bbs.nga.cn/read.php?tid=46019205 .

NGA Forum - "Red Sacrifice Card Triggering Logic Deadlock": https://bbs.nga.cn/read.php?tid=46062219 .

Taiwan Official Forum - "Chamber Missing After Sacrifice": https://pathofexile.tw/forum/view-thread/291212 .

Request: As a content creator representing a significant portion of the Chinese community, I urge you to prioritize a hotfix for the room pool metadata logic. Players should not be forced to abandon their characters due to a systemic program error.

I look forward to your response so I can provide an update to my community.

Best regards,

A dedicated player who deeply loves Path of Exile 2.

Hope this gets attention or a response. Rerolled two times to start the temple anew, wont reroll another time because of this bug :(