In order to ease congestion, players who are inactive for 30 minutes will be automatically logged out. This feature has been updated in Patch 6.0 and has been enhanced from the previous version.
As we would like to give priority to those who would like to actively play the game, we apologise for the inconvenience, but we ask for you to log out when you are not actively playing.
When a World reaches the maximum number of players that can log in, it will result in a login queue for that particular World.
Even if the queue does not appear to be counting down, the queueing process is still functioning and will admit players in the order in which they queued. We apologise for the inconvenience, but ask that you patiently remain in the queue should you encounter wait times. Note that upon cancelling the queue, you will be moved to the back of the queue when reattempting to log in.
When a login queue is in place, players on the full version of the game will be prioritised for logging in. Free Trial characters will be able to log in after the login queue has been cleared. This allows us to prioritise our paying customers and will mean longer wait times for Free Trial users, but we would like to ask for your understanding on this matter.
There is a possibility that certain instanced content, such as duties required to progress through quests, may experience congestion. For instanced duties required to progress a quest, we have devised methods to stagger player traffic during main scenario progression, and have also implemented a queue system in case of congestion. Should congestion occur, your number in the queue will be displayed upon attempting to enter the instance. We ask that you patiently remain in the queue as players are admitted into the instance in the order that they joined the queue.
During the periods immediately after Endwalker’s Early Access and launch, areas added in Endwalker or visited during the Endwalker main scenario will be heavily trafficked. In order to allow more players to enter these areas, we will be implementing several instances of the same area.
Instanced areas will have their area names followed by their instance number at the end, such as Labyrinthos 1, Labyrinthos 2, Labyrinthos 3, and so on. While each of them share the same map, they will be treated as separate areas, and you will be moved to one of these instanced areas when moving to these destinations.
You may choose to enter a specific instance of an area either by traveling to your destination through an entrance from a neighbouring area or by interacting with an aetheryte in the area.
When moving to these areas via teleport or Return, an instance will be automatically selected. Players can confirm which instance they are currently in through a log message in the chat or by using the “/instance” text command.
Players in different instances of the same area can communicate with Tell messages as normal. However, there are some restrictions such as being unable to see each other’s character in the overworld.
Party members will generally be moved to the same instanced area when using teleport or Return. However, party members may be split between different instances if the destination instance has reached the player cap. As such, players may not always end up in the same instance, and may need to select their desired instance either by traveling through an entrance from a neighbouring area or by interacting with an aetheryte in their desired area.