Sabotage! Quest not working

Support Bug Report
1

I am trying to complete the Sabotage! quest. It is letting me accept it. When I get to the Artillery Shell Sabotage, I can do that part. The artillery shell moves upward but the alarm doesn’t come on like it used to and it tells me “This whole place is going to blow. Get to the exit!” When I exit it does not go to the cut scene nor does it let me finish the quest. Nothing happens when I leave the building. I have done everything from logging out, restarting computer, abandoning the quest and starting it again. It still doesn’t work.

17 Likes
2

Exact same thing is happening to me and it’s the last quest I need for loremaster. Pls help

3 Likes
3

I am currently tryng to complete Sabotage! quest also and I am having the same exact issue. I do hope Blizz is able to fix this.

1 Like
4

also having this exact issue

1 Like
5

Same here.

1 Like
6

I am also experiencing this issue.

1 Like
7

Same issue here.

1 Like
8

Same issue here.

9

My wife is having the same bug. Sabotaged the shells got credit but the Get Out part does not trigger.

10

Mine is also doing the same thing. I can accept, sabotage the shell but no timer, and no quest completion once I exit the facility.

11

Same here. I armed the shell ran out and nothing

1 Like
12

I have the same issue. Blizzard doesn’t have a timeline for a fix. I interacted with three different GMs, and they can’t or won’t do anything in the game to address this. I have read that you can complete the Southern Barrens on an Alliance toon if you are not willing to wait for your achievement.

1 Like
13

I need this quest but is buggeddddd

14

Same with me, blizzard please fix it.

1 Like
15

I interacted with three different GMs, and they can’t or won’t do anything in the game to address this.

Yeah they haven’t even included this in the Known Bugs section yet

1 Like
16

This remains broken. Blizzard does not care, obviously due to their lack of response to this issue.

17

has anyone done this successfully?

18

I’m having the same issue nearly a month later :frowning:

19

Yepp. Same here. Lot of time and work on that achivment that is a no show.

20

Just went ahead and did the achievement on an Alliance character instead of waiting who knows how long for them to fix it.

1 Like