Dodgy map closing
It’s hard to say because the map that gets chosen for you also takes into account if a guild member or friend is on one of the newer maps. However if this newer map is also less populated than it makes sense that it gets shut down even though you were just moved to it because of a guild member. This is just another possibility where the server may be working correctly but with unintended consequences.
There is more to this than that. On Monday, A few of us were mapping Mount Maelstrom on some alternate characters. We received the notice to leave the map I think 4 separate times… To clarify: The notice popped up, we ignored it (because we had just accepted to ‘volunteer’ not too long before), after a little while, it goes away, then pops up all over again, just like it’s the first time. Same thing, we choose later, see the little symbol in the lower right, after a while, it vanishes. Little while later, pops up, once again stating in 59mins 59 seconds this map will be closed, etc..
Not to mention I’ve moved a map before, only to have it tell me I have to move not even 30 seconds after having previously ‘volunteered’. I had it do this 3 times almost a week ago.
Both of these situations as well as the op’s are not working as intended.
If it is going to close a map, it should not be moving other people to that map unless it no longer intends to close it, upon which it should not up and decide once again to close it just a few mins later. One change of mind I could understand, why create a new one if one already exists.. but to do this back and forth makes very little sense. Also, afaik, it is still not taking into account friends when it puts you on a map (and if it was, the fact those in same guild also have each other on friends list should increase the ‘priority’ of them being together right?). I can definitely state that megaserver does not care to the extent is should whether you have guildies on a map or not, it puts you wherever it wants, nevermind that you may have 4 other guildies in a Lion’s Arch map. Additionally, I have seen 4 guildies end up in 4 different copies of the same map.. definitely not working correctly, worse when all in same party and that happens…)
(edited by Lunacy Solacio.6514)
It’s hard to say because the map that gets chosen for you also takes into account if a guild member or friend is on one of the newer maps. However if this newer map is also less populated than it makes sense that it gets shut down even though you were just moved to it because of a guild member. This is just another possibility where the server may be working correctly but with unintended consequences.
This would indeed be a somewhat plausible explanation for the dodgy behaviour, but as for my latest run-in with these problems I can exclude it as a possible explanation. I was the only member online of the guild I represented at that time and of my other guilds or friendlist none were in Harathi Hinterlands.
Also, no version of the system working as intended would make it seem likely that a volunteer never gets transferred onto a map with equal or more progress of the pre events – Harathi is especially good for observing this effect because of its long event chain – as would be expected if the new map was indeed more populated than the previous one to begin with, but always onto maps with little to no event progress at all. Either I am very unlucky and the system magically finds maps for me with people who are so extremely lazy that they rather watch the countdown ticking down than send even a single person to do pre events or these are new maps.
And if the system creates new maps or favours newly created but equally empty maps it is certainly doing the opposite of what it is supposed to do.
Yep that does sound like a bug. I guess I personally have been pretty lucky in not getting this bug.