Guild Wars 2

Askalion Hills (Darkhaven Borderlands) assault this evening… holy kitten. So epic. How long was that going for… 10 hours?

Can we please have a civil discussion this time instead of resorting to stone-age ad hominem to get our points across?

Thank you, and carry on.

I also am unable to complete this quest. Makes me really regret choosing the siege tanks story option.

The cutscene in which Tactician Beirne dies saving Crusader Deborah is also EXTREMELY sloppy. Camera pans to nonsensical angles and appears to be centered/focused on an invisible entity, and there is a delay of several seconds between when the subtitles are shown and when the audio for them is actually played.

This isn’t even the only problem with this mission.
The part where you control the lead tank and counterattack the risen assault using the pivoting turret (felt kinda lackluster, by the way; was hoping you could actually drive the tanks around heh. oh well) is also glitchy.
The camera will always do a complete 180-degree flip if you pivot the turret too far in one direction, which makes switching back and forth between the mobs on the left and right side of the battlefield a somewhat annoying task. Also, the turret will sometimes fire automatically when mobs come too close without activating any cooldowns, and will make subsequent shots fired feel clunky. If you have the turret rotated to the extreme left or right and then exit the tank, the position you must be standing in in order to re-enter it is thrown off significantly. The range on these tanks is also HUGELY overkill, and you only need to fill the gauge up to maybe 1/8th and it will shoot all the way to the far end of the battlefield where there aren’t even any mobs. What’s the point of that? One more thing: It took me at least fifteen minutes of mindlessly spamming the “Fire” button before I realized that the mobs were just going to keep spawning over and over and over again. Apparently all I had to do was
kill 6 giants, and nothing else mattered. If giants and giants alone are the objective, then at least have it be written in the quest tracker as such.
If I hadn’t looked it up on Google I probably would have been at it for a long, long time…

One brief play-through test, internal testing even, would have shown these glaringly obvious game-breaking and/or frustrating errors. How did this even make it through beta? I cannot understand how something so apparent could be overlooked. Wouldn’t the author of the quest dialogue or scripting want to at least give it a quick run to see it in action, to be sure that it was stitched together properly? Where’s the quality control?