Guild Wars 2

Okay, so this is a something that is really annoying. According to the feature pack, every contestable waypoint should appear contested when you’re not on that map. Since the patch though, it has been somewhat of a gamble.

I’ll explain. Say I’m on Cursed Shore, and I want to waypoint to Malchor’s Leap. I look at the map and see that every contestable waypoint is contested as it should be, and this is the case for every person on the Cursed Shore instance that I’m on as well.

Now, say I leave Cursed Shore and then re-enter Cursed Shore again. This time, I end up on a different instance of Cursed Shore. I again want to waypoint to Malchor’s Leap, so I look at the map. This time, every single waypoint on the map appears uncontested.

This can lead to bad situations such as what happened to a friend of mine. I was in Cursed Shore at the temple of Grenth, and the priest of Grenth just spawned. I gave a heads up in guild chat that Grenth was up, and that friend tried to come into the instance with me. The waypoint at Grenth appeared uncontested, so she map-traveled there. When she got there, everything seemed fine, until suddenly, before she could even hit the priest, she was teleported to Meddler’s Waypoint, which is miles away. As a result, she missed the priest-event, and thus the event that would get her the trait-point.

On a related side-note, there’s an issue on Southsun Cove with Owain’s Refuge Waypoint. Most of the time when I want to go there, every waypoint in all of Southsun Cove appears uncontested, and I can just move there freely. However, on the off-chance that all contestable waypoints appear contested, why does Owain’s Refuge waypoint also appear contested? This waypoint could be contested way back during the Lost Shores living story update I believe, but has since then not been able to be contested anymore, so there is no reason to make this waypoint in particular appear contested to us.

Kisai Hikaru.1052:

On a related side-note, there’s an issue on Southsun Cove with Owain’s Refuge Waypoint. Most of the time when I want to go there, every waypoint in all of Southsun Cove appears uncontested, and I can just move there freely. However, on the off-chance that all contestable waypoints appear contested, why does Owain’s Refuge waypoint also appear contested? This waypoint could be contested way back during the Lost Shores living story update I believe, but has since then not been able to be contested anymore, so there is no reason to make this waypoint in particular appear contested to us.

Same happens with a few waypoints at Plains of Ashford. After patch around 95% of its waypoints appears as contestable but only around 90% or less gets really contestable (events can happen nearby and such). I have heard it’s due past releases where events would happen there and make it contestable. Thanks to the “working” search feature I can’t recall in what thread I heard about this.

shadow.6174:

Kisai Hikaru.1052:

On a related side-note, there’s an issue on Southsun Cove with Owain’s Refuge Waypoint. Most of the time when I want to go there, every waypoint in all of Southsun Cove appears uncontested, and I can just move there freely. However, on the off-chance that all contestable waypoints appear contested, why does Owain’s Refuge waypoint also appear contested? This waypoint could be contested way back during the Lost Shores living story update I believe, but has since then not been able to be contested anymore, so there is no reason to make this waypoint in particular appear contested to us.

Same happens with a few waypoints at Plains of Ashford. After patch around 95% of its waypoints appears as contestable but only around 90% or less gets really contestable (events can happen nearby and such). I have heard it’s due past releases where events would happen there and make it contestable. Thanks to the “working” search feature I can’t recall in what thread I heard about this.

That was covered in the blog post. https://www.guildwars2.com/en/news/the-megaserver-system-world-bosses-and-events/

I can pretty safely say that the idea that they’ve ‘disabled the reporting of waypoint status across different maps’ isn’t working.

If you think about Megaserver being just a glorified universal overflow system, it makes much more sense. What’s happening is that when you look at the world map and other zones, you’re seeing the current state of the waypoints in your current megaserver copy. When you actually waypoint, you may end up in a different copy.

This is why you’ll see some contestable waypoints uncontested, and will sometimes be able to waypoint there from out of map; or just the opposite – waypoint to a contestable waypoint, and be redirected elsewhere because you’ve arrived on a different copy.

At any rate, cross zone waypoint status is definitely not disabled currently, despite it being mentioned as such. I’ve experienced behavior exactly as you’ve mentioned, OP.

I suppose that would make a bit of sense why Owain’s Refuge waypoint could get contested, because of the ‘gather karka eggs’ event that happens there. I sure hope that this gets fixed soon though!

It’s not a mystery really.

First of all, any waypoint that could ever become contested can become contested while outside of the map, because they didn’t update the flags for those waypoints when they disabled the events.

Second, megaserver is still considering some cases as being in the same world for waypoints.
If you use the command /ip, you’ll get an IP and a number after it. That number is your current ‘district’, the copy of the map you are in. If another map has the same district number, you will be considered as being in the same world, and you’ll see its waypoint status.

So if you are in distrcit 0, you’ll see the district 0 waypoints. And if you travel to an uncontested waypoint in district 0, but its full, you’ll be sent to another district, then the waypoint is checked, and if it was contested, you’ll be kicked to another waypoint.

This would be solved by allowing players to use contested waypoints in PvE, at the cost of paying extra coin and going through a warning message telling you that you may be attacked on arrival.

MithranArkanere.8957:

That number is your current ‘district’, the copy of the map you are in. If another map has the same district number, you will be considered as being in the same world, and you’ll see its waypoint status.

Thanks for the info, I was wondering what that number stands for.

Also, another “side effect” of this with megaserver is pinpointing your party mate. Before last patch you could be able to see where they were (blue dot) in anywhere in world. Now you only can see it if you both are in the same map.