Guild Wars 2

I’ve heard that guesting to another server gives a good chance you’ll end up in a megaserver instance different from the one you’re in now.

I’ve also heard that there’s no longer a limit to the number of times you can guest per day.

If true, you can use these to:

• Get into another instance if the event you’re doing is bugged.
• QD champ train: with Spider gone, the wait at boar is longer than ever. Instead of waiting: after you kill the last boss before boar, guest to another server and map to where their champ train is at. Rinse and repeat. You’ll be killing equal or more bosses this way (equal if there’s only a single QD instance).

guesting won’t help you get into another instance. Just reload the map for that.

Secondly, if you want to test if there is still a guesting limi, log out and guest twice, then try to guest to a 3rd server.

Chances are there’s already multiple servers on your instance, are you going to aks in map everytimg before guesting to make sure you don’t pick one of them? o0

Guesting to another server doesnt gurantuee you’ll be on that instance, it’s supposed to increase you chance of being with others from that server, thats all.

Guesting after the patch

Guesting no longer gives players direct access to the desired server.

However, when there are multiple instances of a map in existence, guesting now becomes an input parameter to bias the megaserver algorithm, resulting in a random chance of accessing one of the multiple instances of the desired map. If there is only one instance of the map, guesting’s bias is rendered useless.

For example, by guesting to Jade Quarry, a player literally tells the megaserver algorithm that he/she wants to load into an instance where currently, the majority of players in that instance are of the Jade quarry allegiance. If there are multiple instances of that map, the result could be the player in the instance with the most players of the Jade Quarry allegiance that is not full.

Of course, there are other input parameters such as party members, and/or guild representation that take priority over guesting bias. So, leave the party before you attempt using the guesting bias.

A useful tool to tell which instance you are in is to simply type /ip in the chat to get the ip address.

About guesting pass limit

A guesting pass is registered as “used” when the player loads into the instance that has the corresponding alias name.

For example, if a player guests to Jade Quarry and he/she loads into a static instance of the alias name Jade Quarry, the guesting pass is registered as being used. However, if he/she loads into a dynamic instance such as an overflow or megaserver instance, the guesting pass is not registered because dynamic instances have no alias names.

Since after the patch, all instances are no longer static (i.e. with an alias name) but are dynamic (i.e. without an alias name), the guesting passes will never get registered as being used, resulting in seemly unlimit number of uses.

Guesting has no more reason to be. What Anet needs to add is the brilliant thing they had in GW1 where you could select your overflow.

The new zerg fest is game-breaking in a lot of cases.

Taygus.4571:

guesting won’t help you get into another instance.

This is incorrect as it is one of the criteria of determining the shard to put you on.