Bug: EWP ports to spawn

Just wanna mention the bug of pressing and porting to the ewp, but the loading screen takes so long that it will port everyone to the spawn back. Make it please like that:If somebody pressed on the EWP , then they get ported there EVEN if its already gone cuz of the stupid long loading screen

@Jayden Reese.9542 said:That's not a bug. By the time it registers if you had a long loading screen the ewp is gone so it sends you to spawn. The bug I know of seems to be players link it but it doesn't show up on every ones map

well for us it counts as a bug if we port to the waypoint but wont get ported there afterwards. Earlier there were no problems with those long loading screens.

@Virdo.1540 said:

@Jayden Reese.9542 said:That's not a bug. By the time it registers if you had a long loading screen the ewp is gone so it sends you to spawn. The bug I know of seems to be players link it but it doesn't show up on every ones map

It’s been an issue (or feature) for quite some time. The EWP lasts a certain amount of time. If you haven’t loaded in prior to it ending, you will default to that maps spawn for you.

Yeah this is a long standing issue that hasn't been worked on. The only thing they did a while back was to increase the duration that the ewp remains open but this solves nothing. Many suggestions have been made by people, the one I have mentioned is that whenever an ewp is pulled, it will automatically echo to /team chat like:@nickname has pulled Emergency Waypoint @Map_Location [waypoint_link]The reason for this is so that there is no precious seconds wasted trying to fumble in chat to shift-click spam the link as it will be auto and immediate.Secondly, there needs to be checks in place that flag the user has taken the ewp before the duration expired, and to transfer them and only put them back to spawn only when the ewp timer has actually expired or the structure has flipped. It's just plain wrong you can be on another map and it seemingly loads you into the ewp for 1-2s (you're actually there and the ewp hasn't expired yet) only to port you back to spawn.

It takes a very long time to waypoint usually nowadays, so much so that waypoints in WvW objectives are only useful if you're already in that map.I believe it's because there is a greater array of costume pieces than there used to be, and your client needs to load them up to display them.

• The simple and elegant solution to this would be to extend the timer on the waypoint up-time.
• The lazy solution would be to do nothing.
• The Arenanet solution would be to replace the whole guild upgrade system with something super-complicated.

Guess which one will happen (I'll give you a clue, it's the second one).

Just to point out, the same thing happens if you WP from another map to a normal WP that then gets contested while you're loading in, it's no different.

Contested waypoints are different.If it happens to an contested waypoint in pve & wvw , then its understandable

if it happens due to long loading screens , then not

@Virdo.1540 said:Contested waypoints are different.If it happens to an contested waypoint in pve & wvw , then its understandable

if it happens due to long loading screens , then not

No, it's the exact same. If you port from another map when the WP is open, then you'll go to that WP. If the WP gets contested whilst you're loading into the map then you kicked to spawn.

@Virdo.1540 said:Contested waypoints are different.If it happens to an contested waypoint in pve & wvw , then its understandable

if it happens due to long loading screens , then not

You may not like the answer, which is understandable, But it defines the issue as expected gameplay, not a bug.

But if you wish, you are always welcome to post it in the ‘bug’ subsection of the forum.

I'd be fine with them removing ewp, would solve a couple problems including this one.

@Justine.6351 said:I'd be fine with them removing ewp, would solve a couple problems including this one.

Right, we don't want anyone coming along and interrupting the train.

@Blockhead Magee.3092 said:

@Justine.6351 said:I'd be fine with them removing ewp, would solve a couple problems including this one.

Heaven forbid they have to stand on a waypoint spamming [AoE on self] until it drops. .. Taking EWP is suicidal!

@Fish.2769 said:

@"Virdo.1540" said:Contested waypoints are different.If it happens to an contested waypoint in pve & wvw , then its understandable

if it happens due to long loading screens , then not

if been able to use an OPEN and still active waypoint ,then it should just be accepted as "ported there" ,even if its contested or gone.

It should go all from the point from being able to port there or not

@Blockhead Magee.3092 said:

@Justine.6351 said:I'd be fine with them removing ewp, would solve a couple problems including this one.

Right we don't want the karma train having to break up to defend different maps rather than just steam rolling enemy maps with the safety net EWP defending their own bl.

@DemonSeed.3528 said:the one I have mentioned is that whenever an ewp is pulled, it will automatically echo to /team chat like:@nickname has pulled Emergency Waypoint @Map_Location [waypoint_link]

I like the QoL idea. +1

@Zikory.6871 said:

@DemonSeed.3528 said:the one I have mentioned is that whenever an ewp is pulled, it will automatically echo to /team chat like:@nickname has pulled Emergency Waypoint @Map_Location [waypoint_link]

They had posted the idea in the past and still +1 one as well, it would be a good change and help point trolls pulling them for the otherside.

I fully agree. If player used the link in time then he/she should always be moved to that point (even if loading takes 3 days)

I think the EWP should have unlimited duration but be destructible, so that a coordinated effort still makes it last about just as long, which keeps it from becoming too powerful from an extended duration as EWP is already a very useful tool.

@Virdo.1540 said:

@Fish.2769 said:

@Virdo.1540 said:Contested waypoints are different.If it happens to an contested waypoint in pve & wvw , then its understandable

if it happens due to long loading screens , then not

And you don't see any issues with that idea...?

@Fish.2769 said:

@Virdo.1540 said:

@Fish.2769 said:

@Virdo.1540 said:Contested waypoints are different.If it happens to an contested waypoint in pve & wvw , then its understandable

if it happens due to long loading screens , then not

except faking loading screens into hour long things to recap keeps etc, not really

Rerolls a Perma-Stealth Deadeye Don't mind me...

@Fish.2769 said:Rerolls a Perma-Stealth Deadeye Don't mind me...

a waypoint isnt needed there

@Virdo.1540 said:

@Fish.2769 said:

Rerolls a Perma-Stealth Deadeye

Don't mind me...

You've either missed my point or are attempting to troll... I really can't tell. :/

@Fish.2769 said:

@Virdo.1540 said:

@Fish.2769 said:

Rerolls a Perma-Stealth Deadeye

Don't mind me...

missing ur point probably, but cant do anything for u if u play the silent game

Imagine you have an t3 keep defended with your zerg against an enemy zerg. You see an thief that managed to hide somewhere inside the lord room (for example the desert keeps). It is permanently invisible, cleanse off reveals (and reveal traps) and continue to be permanent stealth until their zerg is ready again.

^ From your post about perma-stealth Thieves. So nice attempt but i'm hit you with a solid, nope.