They supposedly fixed it this morning in the emergency patch, yet it took my group of 4 an hour to queue in to a dungeon!

They need to patch the patch then cuz this mess is busted.

From all accounts I’ve seen, ZOS never actually took PS4 NA megaserver down, like they stated they wld be doing to deploy the dungeon finder fix. Not sure if this was the case for PC/XBox/EU. Hopefully someone from the company has some good clarification, cause this is all borked and the silence isn’t helping.

Same, we were in a group of 4 and It kept showing that someone was declining the ready check even tho no one was. It took us almost 30 mins to join a dungeon.

joekneegee2003ub17_ESO wrote: »

We have a balanced group of four and no one is declining the invite, but we all keep getting a "Someone declined Invite" notice and we can't que. We can't get the prizes if we can't get in the dungeon. We've been trying for about 45 minutes and we're all getting really frustrated.

Not that I have any expertise with the Dungeon Finder, but what I suggest is that the player characters in a "pre-made group" all gather at the same location, i.e., in the same zone and with each member in sight of each and every other member. Doing that insures that each and every player-character is simultaneously in the same "instance" of the game on the "megaserver".

Apparently the Dungeon Finder does not function reliably when one or more characters are not already in the same instance before the player who invites the others to the group issues the invitations.

Of course, it is possible for a player whose character is in a specific "instance" of the game to invite a player who is not in that same "instance" to join a group. It is also possible for a player character to "travel to" a player character that is in both a different location and also in a different "instance".

However, for the respective player characters to actually form a group or to otherwise be present at the "same location", obviously the "instantiation" of one of the two players must change to that of the other (i.e., when the respective player characters are not already in the same instance).

Changing the "instantiation" of one or more characters to the same instance is ordinarily routine and does not fail. Nonetheless, changing a character's instantiation with a game host running on a "megaserver" per se seems to have some systematic risks -- regardless of whether one or more flaws might exist that could be quite a challenge to find and correct.

So: if a player's character is not in the same instance as the one who issued the invitation, then either:

• that player might not receive the invitation; or
• their acceptance of the invitation might not be acknowedged by the game host; or
• their character might not be able to travel to the location of the one who issued the invitation (or to another player already in the group); or
• the player might not be able to see one or more other player's characters that are in the group after their character arrives at their location.

Among other possibilites (such as a game client crash), the above outcomes occur after either a necessary change in instantiation is not attempted, or matching the instantiation of the respective player characters fails.

Reporting the outcome of an invitation:

• If an invited player does not reply because they did not receive the invitation, then the game host will probably report to the player who issued the invitation that it was "declined".
• If the player's acceptance was received by the game host after the invitation's "time to live" expired, then the game host will also report that the invitation was "declined".
• If the player simply ignored the invitation, i.e., neither accepted nor declined it, then the game host will also report that it was "declined".

Programmers just don't have the time to make the effort to distinguish each of these situations from one another by writing appropriate messages to send to the player who issued the invitation.

The queue: In my experience, when Dungeon Finder organizes a group, it chooses from characters in the queue which are already in the same instance of the game. As one consequence, a player might be added to a group very quickly, but another player who is already waiting is passed-over. The one who must wait is, essentially, waiting for another player(s) who is in the same instance to use the Dungeon Finder to join a group that the Dungeon Finder will organize.

As far as I know, no player has any way to identify the specific "instance" of the game in which their character is currenlty instantiated. However, a player can see that their character is not in the same instance as another player's character after they have formed a group, when the only thing that one of them can see is the white marker above the head of the other character(s).