Jump to content
  • Sign Up

Portal Spiker


Recommended Posts

The Maw meta has an achievement for 100 portal spikes which is part of a chain of achievements to get a title. However, the portal spiking no longer appears if one person uses a skyscale to take down the portal before a demolitionist even arrives. It makes both achievements and the title nearly impossible to achieve in this era

  • Like 1
  • Sad 1
Link to comment
Share on other sites

You mean the Realm-Portal Spiker?

You can still accompany a Demolitionist and do it the old fashioned way. I solo'd and duo'd (found assistance via map chat) the whole thing in a couple of days. You don't have to succeed in the meta, you just need to get a couple of spikes in per run. If you are good at it, you can get up to seven per run.

  • Like 1
  • Sad 1
Link to comment
Share on other sites

1 hour ago, Ashantara.8731 said:

You mean the Realm-Portal Spiker?

You can still accompany a Demolitionist and do it the old fashioned way. I solo'd and duo'd (found assistance via map chat) the whole thing in a couple of days. You don't have to succeed in the meta, you just need to get a couple of spikes in per run. If you are good at it, you can get up to seven per run.

You can't if the demolionists no longer get there. The portal can be destroyed by a skyscale fireball and generates the realm portal boss long beofre the demolitionist even gets down the path. So you can try escorting the Demo, but it's usually too late.

So technically it can be done, so long as no one uses mount siege on the portal and skips the event straight to the final legendary boss. Yes you can ask nicely for people not to do it, but it doesn't always work that way. And it's not their fault - the portal just needs to be invulnerable until the demo gets there and ideally only harmed by the spikes, not by other siege types (might not be possible if they are both classified as siege)

  • Like 1
  • Sad 3
Link to comment
Share on other sites

In theory this could happen but Maws is not a popular meta and is often unattended or has an empty overflow. Just last week I joined an LFG that was specifically for portal spikes and that went smoothly, nobody griefed. So maybe you need to join or create one of those.

The problem with making the suggested change is that the demolitionists often bug out and stall the meta and siege is the only workaround for that. Making the portals dependent on escort completion can still result in no portal spikes and on top of that, the meta fails. Anet could fix those bugs first, but they haven't done so since 2017. Maybe this will give them a reason to do so, but realistically I would not be counting on that to happen, and otherwise removing the siege loophole will make things worse overall.

  • Like 1
Link to comment
Share on other sites

Just now, Leablo.2651 said:

In theory this could happen but Maws is not a popular meta and is often unattended or has an empty overflow. Just last week I joined an LFG that was specifically for portal spikes and that went smoothly, nobody griefed. So maybe you need to join or create one of those.

The problem with making the suggested change is that the demolitionists often bug out and stall the meta and siege is the only workaround for that. Making the portals dependent on escort completion can still result in no portal spikes and on top of that, the meta fails. Anet could fix those bugs first, but they haven't done so since 2017. Maybe this will give them a reason to do so, but realistically I would not be counting on that to happen, and otherwise removing the siege loophole will make things worse overall.

Yes, these are workarounds and I get all that you said, but I already tried leading one earlier with a small group and one person just skyscaled the portals even when asked not to.

I don't really blame the player because they're entitled to do this. Which means the content has an issue which needs fixing. If the escorts are bugging out, well that needs fixing too. Or perhaps the Portal Spiker needs changing to "complete Maw 100 times". 

This is why I am posting in the bug forum - to report it as an issue to be looked at. if there are further bugs since 2017 to be fixed still, then those can be added to this as well. I don't realistically think they will even look at this issue, but I still want to report it as being even as a very minor problem. I can continue to try other workarounds in the meantime

 

  • Thanks 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...