[List] Dungeon & Dungeon Related bugs

#1 - March 3, 2014, 9:03 a.m.
Blizzard Post

Hey guys. I’d like to start a little community initiative which we can easily show to Danicia when she gathers feedback and such to bring back to developers. Please post your bugs and issues here, and i will update this post. I’ll start:

  1. Dungeon runes are soulbound on acquire, even ones that drop from the forge
  2. Twilight Arbor dungeon light mantle clips badly with long hair
  3. LFG merge button will destroy an instance, if someone from outside the party clicks it.
  4. SE explorable mode. Mainly effects path 3. Floor is missing which breaks patrol route of one group of dredge. Also forces the group to go a longer route to reach the first boss.
  5. All dungeons. Spiders and other mobs which start off as green and/or drop down from the roof when approached are all visible from instance start now. Examples are TA spiders and malrona in malronas cave. The 6 archers in TA forward path. All spiders in arah.
  6. Arah and COE broken waypoints
  7. Volcanic fractal. Still has a broken camera on the final boss fight.
  8. The crystal bug in CoE where a player gets crystalized by Subject Alpha, his team breaks the crystal, but the player remains paralyzed for 15 secs or more anyway.
  9. The many exploits in Arah. Teleporting underwater. Becoming phase-shifted when not supposed to (“god mode”). Skipping Lupi. Etc.
  10. NPC’s bugging. NPC’s aggroing enemies when they’re not supposed to. NPC’s not following the right player. NPC’s being stupid in general.
  11. For AC path 3 the final boss can be killed. But no end reward is recieved. The daily bonus chest appears on boss kill. But the final cutscene doesnt trigger and the xp, 20 tokens and silver end reward doesnt appear. Essentially the path doesnt finish despite all objectives being complete and the daily bonus reward being received. Unconfirmed cause (possibly due to fast kill).
  12. AC P3, after the burrow event in the room with Grast, Tzark sometimes bugs and doesn’t start his sequence. The dungeon thus can’t be completed, as the hole doesn’t open for us to get to the endboss.
  13. Arah P4, the NPC that transforms into the risen avatar of Lyssa bugs out more than often and doesn’t start her sequence, leading to the boss not appearing. The dungeon can’t be completed under this conditon.
  14. CM Path 1, Frost can still be exploited, in pure safety.
  15. Arah Path 1, Ancient Ooze can still be exploited, in pure safety.
  16. AC Path 2, occasionally the Charr NPC (who’s name I do not know) will not trigger the trap event and follow a random player. The Ascalonian Captain does not spawn.
  17. COE paths 1/2/3, players are still able to fight Subject Alpha before a path has been selected.
  18. SE p3 – first boss can be exploited
  19. Arah path 2: occasionally Belka does not activate, forcing a restart of the instance.
  20. arah p3 – Wraithlord Mage Crusher can be exploited
  21. AC P1 has trouble with Hodgins before the ‘scepter hunt’. He occasionally requires members to WP back to center to reset him and trigger the ‘scepter hunt’.
  22. Cof path 2 when Maggie doesn’t start his dialogue when people find the rock
  23. When your weapon swap is on cooldown and you enter a cutscene, your weapon swap will bug and you will not be able to swap weapons until you have done so manually by opening the hero window and pressing the arrows.
  24. Sometimes when you swap in a skill that you also have in your underwater skills, it will have the same cooldown as one of the skills already on your bar. (e.g. my Banner of Discipline is on 100 seconds cooldown, I swap in Signet of Fury and it is now also on 100 seconds cooldown.)
  25. AC p2: Detha can bug at the first event with the spike traps (not sure how).
  26. Arah p3: the NPC can bug and not trigger the cutscene before the ritual starts (not talking about her dying next to the chicken cage). She will be standing in the middle of the Altar with the chicken in her hand but not trigger the cutscene and she will start following nearby players when you get to her.
  27. HoTW p1: You can safespot the boss on the stairs (not sure what he is called).
  28. CM p1: I’m not sure if it’s a bug, but the NPC will often not come to you when you spam interact on one of the items you have to destroy as the first objective of the path. I have once been spamming interact for ~30 seconds and she still didn’t come.
  29. SE p3: The conversation between the champion and silver dredge (before the destroyer) will often not trigger and they will become agressive right away.

Let me know of anything else. Also, if you are reading this, Danicia, could you let me/us know which numbers you have noted and taken back (or refuse to take back to devs, if that’s the case) so we can stop talking about them?

Devs: if you need more information on an exploit please post a request for a PM. We do not want to post specifics on the public forum.

Thank you all!

#48 - March 3, 2014, 3:56 p.m.
Blizzard Post

Howdy all,

Lilith asked me to take a look at the thread to see if I had any guidance and whatnot. Obviously, I cannot confirm or speculate on anything in the post. What I can do, is hopefully help direct the discussions.

Bugs – The best thing to do when you know something is bugged is to put it in the Bug Forum, following this format: https://forum-en.guildwars2.com/forum/support/bugs/Please-Read-How-To-Bugging-Best-Practices

When the bugs are reported, we can direct QA to the threads in question. They may or may not respond to these reports, but it does ensure they’re put into the bug tracker system.

Regarding exploits, the best thing to do is write it up and email [email protected] for any you wish to report. These are also logged.

Now, in regards to people exploiting bugs or systems, it’s best to report them in-game or submit a ticket to Support for review.

#53 - March 3, 2014, 5:05 p.m.
Blizzard Post

Indeed! Doable I say!

Also, I think it is a good thing to have this list. Many new people might not know the process, so keeping a running list is helpful. Maybe a “reported by…” next to each item, with a link, so people know it has been reported and by whom.