Jump to content
  • Sign Up

Unable to get achievement: Destroy Additional Pylons


Recommended Posts

This has come up before (and I'm sure it will come up again). I've concluded that none of us can be sure exactly what's necessary to trigger completion (there are contradictory reports) and that more than a few people have repeat trouble with it. So I'll share with you what I've done that has worked 100% of the time. I can't guarantee it will keep working all the time and it's probably overkill. There just haven't been any cases where people followed this and failed to earn the achievement.

In brief

  • Kill All the Things
  • Avoid using mounts to destroy the pylons (okay on the mobs and mostly only a problem when 2+ people in the instance)
  • Be sure to go back to make sure you didn't miss a location or a stray foe.

DetailsThe most important thing is:

Kill all the things.

At every pylon, there are a number of mobs, awakened and forged. Make them all dead; don't let any escape. It doesn't seem to matter if you kill them before or after the pylons are destroyed, so whatever is easier for you.

Next, try to avoid using mounts to destroy the pylons. This doesn't block everyone, but it might have blocked some of us. The theory is that the pylon dies too quickly and some sort of trigger doesn't register as being pulled. You probably can't completely avoid doing damage with mounts; just be cautious.

Finally, even when you're sure that you got all the pylons and all the foes, go back and double check. There's often a pesky forged that runs away like the coward Balthazar is and hides briefly. When you return, they'll have leashed back to the original spawn location and should be easy to spot.

Good luck and please let us know how it works out.

Link to comment
Share on other sites

  • 1 month later...

After failing to get the achievement, testing different things, then succeeding:I believe what you need to do is tag each pylon with a weapon at least one time yourself.

That means you cannot use your mount to destroy the pylons. I did not have to destroy everything when I was successful.

Link to comment
Share on other sites

  • 3 months later...

Still seems bugged to me. I killed all the things and didn't die. I did use mounts to deal initial damage on most of them, but finished each pylon with either my own weapon or the Char's blade. Guess I'll just have to try again with the next character I run through the story.

Link to comment
Share on other sites

  • 3 weeks later...

I've just completed the entire thing.

  1. I killed every creature in the instance, both forged and branded.
  2. I damaged enemies and pylons with mounts, but finished them all with Sohothin.
  3. I double-checked each area for enemies or pylons before moving on.
  4. The achievement never completed, and the icon on the taskbar disappeared as soon as the fight with Warbeast began.

All that, and still I didn't get the achievement. The most annoying part is that I've done this several times now hoping to get it, and this is a LONG instance. It's a drag repeatedly replaying the same content after each patch hoping the thing is fixed, only to find out that I still can't get the achievement. If it were a 10 minute instance, I wouldn't mind so much, but this thing takes ages to complete.

Link to comment
Share on other sites

@daimon.9876 said:I've just completed the entire thing.

  1. I killed every creature in the instance, both forged and branded.
  2. I damaged enemies and pylons with mounts, but finished them all with Sohothin.
  3. I double-checked each area for enemies or pylons before moving on.
  4. The achievement never completed, and the icon on the taskbar disappeared as soon as the fight with Warbeast began.

I just did it again, this time I only damaged one pylon (the final one) with a mount, all other damage was with Sohothin or my other skills. It finally completed. Perhaps this lends some credibility to the idea that it is mounts that interfere with completion?

Link to comment
Share on other sites

  • 1 month later...
  • 1 month later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...