EDIT: As of the July 28, 2020 update, the bug has been fixed!!
This is a collaborative report done on the infamous Chronomancer Chronophantasma Bug in Guild Wars 2, put together by Luxroy and myself. In this video we go over the cause of the bug, common in-game occurrences, options for mitigation, and other findings related to the phantasms affected. We hope you find something useful in all of this! Big, big, thank you to Sejsel and his GW2 Scratch Log Manager and EVTC Inspector Tool. Without it, none of this would be possible.
We learned a lot about this bug and how to possibly prevent it, but at the end of the day we hope to see a actual bug fix from Arenanet.
Part 1 - Introduction 00:00
Part 2 - How the Bug is Triggered 1:00
Part 3 - In-Game Example: Sword 5 → Ether → Sword 5 2:13
Part 4 - 30644 and 30702 4:28
Part 5 - In-Game Example: Opener 6:40
Part 6 - What We Know, What We Think We Know, and How We Figured It Out 9:22
Part 7 - Conclusion 13:57
Relevant Links:
GW2 Scratch Log Manager/EVTC Inspector Tool: https://gw2scratch.com/tools/manager
GW2 Scratch Discord: / discord
Lawitz's 41.1k Benchmark: • Power Chrono, Domi, Focus - 41147.
Mirror on Luxroy's Channel: • The Chronophantasma Bug : An In-Depth Look...
Luxroy: / @luxroylux
Corporate Panda: / @corporatepanda