Guild Wars 2

So, I ran the dungeon with my guild last night and it was going pretty smooth. Got to the room with the last boss in a relatively short amount of time. We’re doing the generator event where the floor gets electrified, and the whole party wipes, which isn’t a concern or surprise. Except, when we make our trek back into the room, none of the mobs would spawn, so there was no way to complete the rest of the event.

We tried everything to get the mobs to spawn. Wiped ourselves again, left and came back, checked every nook and cranny, but nothing worked. We even sat there for a full 5mins+ killing one of the generators manually to see if that might spawn the mobs, but to no avail.

These kinds of bugs have no place in production. Where’s the QA in this game? It ended up being a waste of over an hour before we finally gave up and exited completely.

Anyone else run into this bug yet?

It’s not possible to make content completely bug. People need to report bugs so Anet can try to fix it. With a better description of exactly what your party did to cause the bug.

There is no reason to be mad about a bug.

Onshidesigns.1069:

It’s not possible to make content completely bug. People need to report bugs so Anet can try to fix it. With a better description of exactly what your party did to cause the bug.

There is no reason to be mad about a bug.

I’m a developer, and I completely disagree. Yes, all software has bugs, but you are a failure if your software reaches production and there is an app-breaking bug in it. I couldn’t care less about some of the invisible clipping issues that dungeon has, or some of the poor AI pathing, etc… But I have a problem when I can’t complete the content because of it.

We literally died, waypointed, and re-entered the room. If we were blinking through walls, or sword-leaping over obstacles I can understand, but playing normally should never cause you to not complete the content. Period.

Dresden.1736:

Onshidesigns.1069:

It’s not possible to make content completely bug. People need to report bugs so Anet can try to fix it. With a better description of exactly what your party did to cause the bug.

There is no reason to be mad about a bug.

I’m a developer, and I completely disagree. Yes, all software has bugs, but you are a failure if your software reaches production and there is an app-breaking bug in it. I couldn’t care less about some of the invisible clipping issues that dungeon has, or some of the poor AI pathing, etc… But I have a problem when I can’t complete the content because of it.

We literally died, waypointed, and re-entered the room. If we were blinking through walls, or sword-leaping over obstacles I can understand, but playing normally should never cause you to not complete the content. Period.

Well, sometimes it’s really easy to QA on a small scale but once it reaches full scale, it becomes open to more bugs as sometimes they couldn’t have tested it. Just take the food buff in the Dragon Ball arena for example. They didn’t think of it. It’s only in full scale that they noticed their mistake.

You CAN’T have a game be full bug-proof. You can QA to reduce the amount of bugs, but it’s pretty impossible for a MMO (not talking about single player games) to not have bugs on Day 1. Though they are quick to fix important bugs.

GoddessOfTheWinds.2937:

Well, sometimes it’s really easy to QA on a small scale but once it reaches full scale, it becomes open to more bugs as sometimes they couldn’t have tested it. Just take the food buff in the Dragon Ball arena for example. They didn’t think of it. It’s only in full scale that they noticed their mistake.

You CAN’T have a game be full bug-proof. You can QA to reduce the amount of bugs, but it’s pretty impossible for a MMO (not talking about single player games) to not have bugs on Day 1. Though they are quick to fix important bugs.

It is this kind of complacency and excuse making which perpetuates these bugs. This is not status-quo. Several major MMOs have development servers where players are invited to join and test new content prior to production rollout. There, players report the bad glitches and exploits and developers patch them out before it goes live. It is a tried and true QA process which is extremely effective and efficient. Even at my own place of work we use a UAT environment specifically for that purpose.

How is this app-breaking?

How is this a glitch?

Please don’t false advertise.

On a more constructive note, was there anything unusual about your encounter before this event occurred? For example: Did a member enter, pull agro and run out of agro range of the NPC’s in question.

Eddy.7924:

How is this a glitch?

Please don’t false advertise.

On a more constructive note, was there anything unusual about your encounter before this event occurred? For example: Did a member enter, pull agro and run out of agro range of the NPC’s in question.

How is it not a glitch? Please don’t make stupid assertions. And for the record, this was posted on the TA board, and a mod moved it here.

The Dungeon was impassable because the mobs stopped spawning. The mobs are supposed to infinitely spawn as killing them is the only way to unlock the last boss. The fact they stopped spawning is the glitch and the fact it was then impassible makes it game-breaking. It’s really quite plain. Apparently you haven’t bothered with the new dungeon yet, which makes me wonder why you would even attempt to speak on it before trying to belittle the problem.

You enter the final boss’s chamber, and there are 6 or 8 power generators you have to destroy. The only way to destroy them is by luring the infinitely spawning mobs to the location of a generator and kill the mobs. The mobs explode on death and take out the generator. Without the mobs, there is no way to progress. Once you enter the room, there is no way to disengage as the door locks behind you and there’s no way out besides party wipe.

I’ve played the path several times, and party wiping is extremely common on that part. Been in groups have have wiped 10+ times trying to get it done. This last run, however, we wiped once and it glitched.