User:Relyk/bug tracker
From Guild Wars 2 Wiki
Jump to navigationJump to search
Tracks the most recently added bugs.
Date | Bug | Description |
---|---|---|
21 November 2024 (22:11) | Janthir | While in Mistlock Sanctuary, a map title of Thunderhead Peaks can be seen in the waters west of Mount Balrior. |
20 November 2024 (11:11) | Guide to Kurzick Combat Stances | * Can be purchased multiple time despite having no use or effect after the first purchase.
|
19 November 2024 (19:11) | Trial and Error | * Achievement will not be earned if killed too quickly, make sure the dialogue that happens at 75% and 50% fully plays out before bringing it to 1% (after "Exactly what I wanted to hear!".
|
19 November 2024 (08:11) | Against the Wall | The instance may disconnect during the final dialogue, forcing you to restart the battle at the 50% checkpoint. |
19 November 2024 (07:11) | Finding Balance | The instance likes to disconnect from the server while talking with the Charr Prisoner, forcing you to restart the chapter completely. Talking to him first seems to help prevent this. Progress towards The Dead Do Tell Tales will be retained as long as you complete the conversations. |
16 November 2024 (13:11) | Spiritcrush | Spiritcrush currently shows the damage line twice in the tooltip. |
11 November 2024 (10:11) | Free Action | Only grants Swiftness after using Three Round Burst or Sniper's Cover. |
07 November 2024 (17:11) | Transform Fading | The transformation doesn't get removed once Transform Fading expires. |
02 November 2024 (23:11) | Guardian Angel Pedestal Chair | The holographic extra life icon will not show on newly joining players who entered the map after the user mounts their chair. |
29 October 2024 (23:10) | Tales of the Lowland Wisps | * As of November 19, 2024 game update, step 5 is currently bugged, the wisp stops after a while, making it impossible to complete; no workaround has been found yet. Main forum post about the bug can be found here. The first reported occurrence of this bug was on October 10, 2024. ArenaNet is aware of the bug and is working on it.
|