As of right now, it says there are seven American districts available for Lion's Arch. AD4 was crowded, but when I showed up in AD2... it was empty. Right now, as in this exact time, there are less than ten people in AD2.
Is there any reason why this district barely has people and yet the other ones have more?
Also, if you're reading this, go take a look. I can easily say it wont be like this tomorrow, but if you want to go to Lion's Arch for a moment of tranquility, go check it out.
Lion's Arch AD2 Is Empty?
1 pages • Page 1
K
Quote:
|
Originally Posted by Aera
Woa definitely worth making a thread for! Go to Korean district 1 of Great Temple of Balthazar, completely empty! WHOAAAA
|
A
Quote:
|
Originally Posted by Antheus
|
D
I
E
I was in the game when I read your post and mapped to LA out of curiosity. I ended up in District 4 which was pretty crowded. Then I went to D2 and, you're right, it was practically empty. And no lag!
Inger is right. That's pretty much what it looks like in International and if you want to see it really empty go to Asian.
Inger is right. That's pretty much what it looks like in International and if you want to see it really empty go to Asian.
Well, outpost districts are just shared instances. If there are zero players in a certain outpost then that outpost doesn't actually exist - the first district is only created when somebody enters that outpost (you can observe this in an outpost where NPCs carry random equipment - if you are the only player in that outpost and zone out and in again the equipment changes since it's destroyed when you leave and recreated when you return).
Second, while it is a trivial task from a load balancing point of view to add new districts as necessary, removing them when not needed any more is much more complicated if you cannot forcibly 'compress' the player distribution by moving people away from sparsely populated districts before deletion. GW schedules the deletion of a district by certain criteria and once a district has been flagged for deletion you can't enter that district other than by specifically selecting it as your destination.
It is quite possible that the district in question was scheduled for deletion and thus all the traffic was getting directed to other districts. These kind of issues are also apparent in major cities during festivities when the volatility of the player population is particularly large.
Second, while it is a trivial task from a load balancing point of view to add new districts as necessary, removing them when not needed any more is much more complicated if you cannot forcibly 'compress' the player distribution by moving people away from sparsely populated districts before deletion. GW schedules the deletion of a district by certain criteria and once a district has been flagged for deletion you can't enter that district other than by specifically selecting it as your destination.
It is quite possible that the district in question was scheduled for deletion and thus all the traffic was getting directed to other districts. These kind of issues are also apparent in major cities during festivities when the volatility of the player population is particularly large.
U



