Guild Wars 2

The orb protectors still spawn in enemy color when keeps been taken. Which means they destroy the alter.

This happened to us Fortaspenwood in dragonbrands borderland at Etheron hills.

Also had to kill protectors long after we capped a Garrison last night.

Having constant crossed swords on EK due to the bugged guards at inner gate was annoying enough. Having bugged guards in lord room of EK and Garrison is gamebreakingly stupid. I’ve been seeing lots more reset orbs in my matchup recently and it’s definitely because NPCs are breaking the altar and causing the orb to reset when no one grabs it in time.

This isn’t some complex problem to solve like culling. This more looks like some inattentive programmer put the wrong values in an array when they were hardcoding out guard properties. Why the hell isn’t this fixed already?

zastari.1730:

Having constant crossed swords on EK due to the bugged guards at inner gate was annoying enough. Having bugged guards in lord room of EK and Garrison is gamebreakingly stupid. I’ve been seeing lots more reset orbs in my matchup recently and it’s definitely because NPCs are breaking the altar and causing the orb to reset when no one grabs it in time.

This isn’t some complex problem to solve like culling. This more looks like some inattentive programmer put the wrong values in an array when they were hardcoding out guard properties. Why the hell isn’t this fixed already?

If that is a serious question, i’ll give you a serious answer

http://en.wikipedia.org/wiki/Scrum_

My guess is that arenanet are working in 2 week sprints.

BlackRabbit.1259:

zastari.1730:

Having constant crossed swords on EK due to the bugged guards at inner gate was annoying enough. Having bugged guards in lord room of EK and Garrison is gamebreakingly stupid. I’ve been seeing lots more reset orbs in my matchup recently and it’s definitely because NPCs are breaking the altar and causing the orb to reset when no one grabs it in time.

This isn’t some complex problem to solve like culling. This more looks like some inattentive programmer put the wrong values in an array when they were hardcoding out guard properties. Why the hell isn’t this fixed already?

If that is a serious question, i’ll give you a serious answer

http://en.wikipedia.org/wiki/Scrum_

My guess is that arenanet are working in 2 week sprints.

With Scrum you’re still able to fix issues on live branches.