Guild Wars 2

Is this a common thing now or just a way to force people to go do a map again,

There was a bunch of us in TD building the map up to T4 etc, some of us where fighting the Chak Driver, it was about 40% health and WHAM the map loading screen comes up, and then suddenly we are on a different instance of the map, Participation was reset to 0% and may level was reset to level 0,

This is not the first time this has happened, why do you take away the rewards of people have spent the last hour building the map up,

This is not the first time ive seen this, but first time I thought it was maybe my connection, but this time it was only certain people that got the boot, this happened right after a bunch of commanders spawned into the map, is the mega server kicking random people from a map to allow squads to hot join?

As I understand it, the map closing warning comes up but goes away when new people are ferried on. However once the warning comes up, the map closes in an hour no matter what, so you have a full map of people that all get the boot.

There was no warning though, we where on the map from the failed TD Meta and started rebuilding it, I know that DS resets, but afaik this does not happen with Tangled Depths.

It is a very common thing. Explanation time!

Maps have certain sets of circumstances that will cause them to “close”. When a map gets flagged for closing, that shard has a one hour timer before the entire map is deleted and you get forcibly moved into a new instance. There are two circumstances which cause it to close:

#1: Low population. This is a strange one, since it isn’t always truly low pop. What happens is, a bunch of people will start taxing others in to join the instance. But, this taxi doesn’t truly count as players entering the map, so this doesn’t change the “low pop” flag. This is quite troublesome with meta events (and triple trouble, interestingly), because these maps tend to form via taxis. Even if you zone in without joining someone else’s instance, the map is still flagged to close and you don’t personally count enough to change that, so you’ll suddenly find that everyone gets scattered among other instances with no warning.

#2: ? circumstances. This might be a bug, or it might be intentional, but this is what I refer to as a “high pop closure”. While the above gets closed when there’s not enough people, there are instances when a map will get flagged (not closed, but flagged) while there is a sizeable population. Currently I think this is a bug: Guild instances will be flagged to close if they are too high population, in order to spread people out and get everyone “in”. If this program isn’t being applied correctly, then each time a map caps, it gets flagged to close to force players into less populated instances.

The whole system is really wonky at the moment. Anet really needs to fix it.