Darkshore bugged

That would do the trick, and I suspect is an easy enough fix.
It would also keep it from being grieved intentionally.
All of those players who are " hurry hurry hurry kill kill kill!" mentality can then either accept the task at hand, just stand around and moan, or go kill the enemy forces being deployed down the roads.
One guess at which of those three options they would choose?

2 Likes

LOL… I’d say it, but I don’t want to offend anyone. XD

1 Like

It is faster to just get through the enemies than it is to build the base, but Blizzard has it only scripted to build the base and send up catapults. In other words, do it as intended for now or be prepared for this crap.

It’s faster to build and move up the map simultaneously, but you’re relying on everyone participating as a team, which isn’t always going to happen.

1 Like

I did it with about 10 people who were 380 or above. You don’t really need many people, just geared people who know how to play their class. We found out the same bug when we attempted to bypass the slow base building phase.

1 Like

Exactly. And I feel like they sped up how much resources we get in Darkshore now. So it actually works really well if it’s done simultaneously.

But yeah… this means some equal participation from people. And that can be rare.

Thanks, I read this before doing it today.

The people I was with did not rush, getting the glaives and stuff built. I actively helped with that.

1 Like

Question, does anyone know why the commander’s haven’t switched off yet? Is that a bug too?

Me and the other folks in this thread I guess.

It’s not a bug! In this Scenario there are certain conditions that MUST be met to complete the Scenario. If you don’t complete the conditions in the correct order, you fail the Scenario just like a Quest. Let’s say you have a quest to kill Kobolds and you chose to ignore the parameters of the quest and kill Merlocs instead. You will not complete the Quest. In the parameters of the Darkshore scenario you MUST build the Tree of Ages, the Glavewors and build a glave thrower BEFORE you move on and destroy the two MK Robots. If your group chooses to ignore the parameters of the scenario then, just like a quest, you will fail the scenario. It’s NOT a bug, players need to understand the parameters of the scenario and complete it properly.

1 Like

World of Big Bugs :smiley:

Technically, it may not be a bug per se, but if the mechanics allow a hung state of the instance to occur, and it cannot be completed, then there’s a rationale to describe it as such. Not to mention the resources it ties up and that it is something that players can manipulate to grief other players.

1 Like

Arathi Warfront: RUSH RUSH RUSH Oh we need the demolishers to smash the gate.

Darkshore Warfront: RUSH RUSH RUSH, wait, why is it bugged? We didn’t build glaive throwers??? But we made it to the end wth?

Basically, an oversight by blizzard, and I am so surprised it has been a few days of people reporting on this game breaking bug and still radio silence from blizzard about the bug.

You solved it!
All they need to do is install a set of Biggus doors in front of those robots so they cannot be attacked until the doors get busted down by the glaives.

Or they could script it so that it can go from building glaive > capturing lordanel and clearing sea blockade > fight sira
To autocomplete the 2nd objective stated above if its done already when glaive is finally built.
Or, just make the building of glaive / upgrading of buildings optional. If players are good enough to zerg down the robots / ships, give them the pass to fight sira…

And this is hair splitting and if you keep it up you will go bald.

If I had a quest that I got to the end of and found I couldn’t complete it because I’d failed to pick up that flower along the way then I’d just go back and pick up that flower and do it right. But this is a GROUP scenario. Having any sort of mechanic that allows the group to proceed past doing a particular thing to the point that the whole thing bugs is ridiculously bad planning.

The same thing happened in beta to Arathi. That was fixed before it went live. Yet they could not manage to foresee this issue and fix it? That’s not mechanics, that just bad planning.

:australia:

2 Likes

My eyes, it hurts. :fire::fire:

Just give the stupid robots a shield the glaive throwers have to break. Heck make them recast it every minute so people have to protect the glaive throwers.