Bug Report: Game-Breaking Bugs in Act 2 (Cruel Quest) and Act 3 (Rootredge Boss)

Bug Report: Game-Breaking Bugs in Act 2 (Cruel Quest) and Act 3 (Rootredge Boss)

Description:

Two significant and potentially linked bugs are halting progression in Act 2 and Act 3:

Act 3: Rootredge Boss encounter as you enter Act 3 cruel

Act 2 - Quest: "Ascent to Power"

Objective: "Search Traitor's Passage for more information on the Barya you found."

Issue: The quest does not progress regardless of the amount of time spent killing enemies or exploring Traitor’s Passage.

The objective remains incomplete, and no further information is granted, effectively blocking completion of the quest.

Act 3 - Rootredge Boss Encounter

Issue: Despite defeating the Rootredge boss multiple times (14 times total), the encounter does not grant the completion reward and remains greyed out.

This prevents quest progression, making this a second game-breaking issue.


Steps to Reproduce (Act 2):

Start the quest "Ascent to Power" in Act 2.
Enter Traitor’s Passage and attempt to complete the quest objective.
Observe that no quest progression occurs, and the objective remains stuck.


Steps to Reproduce (Act 3):

Engage and kill the Rootredge boss in Act 3.
Observe that the completion reward does not appear and the encounter remains greyed out.
Speak with relevant NPCs (e.g., treasure hunters in Ziggurat Encampment) and repeat the boss fight.
Observe that the issue persists.


Expected Behavior:

Act 2: Completing the quest objective in Traitor’s Passage should grant progression for "Ascent to Power."

Act 3: Defeating the Rootredge boss should trigger the completion reward and allow further quest progression.

Actual Behavior:

Act 2: The quest in Traitor’s Passage does not progress, leaving the objective permanently stuck.

Act 3: The Rootredge boss does not grant the completion reward, and the encounter remains greyed out even after multiple kills.

Impact:
These bugs are severely game-breaking:

Act 2 cannot be completed due to the broken quest objective.
Act 3 progression is blocked due to the Rootredge boss issue.
The potential linkage between the two bugs exacerbates the issue, as progression in one act may depend on the other.

Additional Information:

These issues persist across multiple attempts and areas, suggesting a systemic problem rather than isolated bugs.

Both bugs have halted gameplay progression entirely.

No available solution or hotfix has addressed these problems to date, creating a frustrating experience for players.

Urgency: Like as in NOW please or give some guidance as to what to do.

This is a critical, game-breaking issue affecting core progression in multiple acts and requires immediate attention from the development team.

TY,

I am here because Ive defeated Rootredge 3 times in Cruel difficulty and picked up all dropped items and I still do not get the completion reward.

ty im glad im not the only one.

Same, Glad to see I'm not the only one

Its more important to tweek loot drops to 20 levels below current level to drop than fix mechanics.

If this continues to be the trend where noting drops, have to rely on 3rd party sites for gear and currency and story line is not the priority to be fixed, this game will die with this comment.

Was hoping poe 2 would not be identical to poe1 , but alas, it is.

I've hit both of these issues as well in Act 2 Cruel and Act 3 Cruel (with patch 0.1.1b):

In case of the "Ascent to Power" quest, I at first thought that the quest might've gotten bugged because I managed to die at the same time as the boss, which seemed to reset the progress and I thought I just had to kill her again to progress/complete the quest, but that wasn't the case; seeing this bug report now, I guess the bugged quest state might be unrelated to my character's death after all. Also maybe worth noting is that Balbala does appear as defeated on the world map, it's just the quest that is stuck for me.

Regarding Rootredge, I saw that he didn't show as defeated on the world map after killing him the first time, so I reset the zone and was able to kill him again, but that didn't mark him as defeated either; so this seems bugged for me as well.