Guild Wars 2: Mega Server

Hello everybody, Geek Generation here.

Initially, Anet said that the Mega Server system would be implemented only in the starter maps and would be fully rolled out in December. But it appears that most of the maps already are in Mega Server build. It truly is good news for new players since it increases the population in the player’s map by a significant amount. Maps no longer appear like dead zones which tend to happen in games that has moved on to end game content.

However, the Mega Server system poses a problem for guilds doing guild missions. Before i talk about the problems, i have to talk about the cap (the maximum amount of players allowed on a map) system in Guild Wars 2. The cap system is divided into soft cap and hard cap with the former being a lower number than the later. When soft cap is reached, only players who are party members with a player that’s already in the map can join it. When the hard cap is reached, a player can only join a map only if an existing player in the map leaves.

This soft cap allowance creates a unique work-around for large numbers of people who need to be in the same map, namely guilds doing guild missions. Guilds would have to form taxi parties to ferry guild members into the same map when the soft cap limit has managed to cut the guild in half. Which needless to say, is utterly immersion breaking.

In the guild mission that my guild was doing, the map was already hosting players from several other guilds. The first few members from the guild entering the map pushed the map population into soft cap limit causing the entire guild to be split into two instances of the map. The end result was alot of the ferrying of guild members via taxi parties.

Here i propose a possible solution to this splitting of the guild doing guild missions.

In the guild missions screen, the ui (user interface) should have a button to allow guild members to join once the guild mission is started. All members who joined would have the same priorities, as if they were all in a party, for the map-instance allocation system. This would prevent the soft cap causing guild members to end up in different instances of the same map.

In addition to that, if there were such a “join mission” system in place, the map-instance allocation system would have advance information on the amount of players, as a guild, coming in for guild missions. This would then allow the system to place the incoming guild into a a wholly new instance if the incoming guild was large enough to breach the soft cap and hit the hard cap of the existing instances.

Ok so much for now. Hope Anet takes this suggestion into consideration. Geek Generation out.


Posted on 21 April, 2014, in Gaming, Guild Wars 2, MMORPG and tagged , , , . Bookmark the permalink. Leave a comment.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: