A version update was performed on FINAL FANTASY XIV: A Realm Reborn at the following time.

* Clients will update automatically upon launch after the date and time below.

[Date & Time]
Sep. 12, 2013 around 02:15 (GMT)

[Affected Service]
FINAL FANTASY XIV: A Realm Reborn

[Update Details]
The following features have been implemented:

- An auto-logout feature has been introduced wherein characters that are inactive for 30 minutes will be automatically logged out of the game.

The following adjustments and countermeasures have been implemented:

- Changes have been made to the behaviour and mechanics of the enemies found within the “The Wanderer’s Palace” and “Amdapor Keep” dungeons to counteract instances of players running through the dungeon without engaging enemies on the way to bosses.

As advancing through dungeons without defeating enemies is not an intended strategy, we plan to continue making further changes in the future to discourage this type of behaviour.

- In instance dungeon “The Wanderer's Palace” and “Amdapor Keep”, we have increased the amount of Allagan Coins that can be obtained from a treasure chest.

- Reduced the amount of gil required for repair fees and materia removal as follows:

Equipment levels 1-10: 10 gil -> No Change
Equipment levels 11-20: 50 gil -> 30 gil
Equipment levels 21-30: 100 gil -> 60 gil
Equipment levels 31-40: 210 gil -> 120 gil
Equipment levels 41-40: 500 gil -> 200 gil

- Reduced the price of Dark Matter as follows:

Dark Matter G1: 5 gil -> 4 gil
Dark Matter G2: 30 gil -> 12 gil
Dark Matter G3: 70 gil -> 24 gil
Dark Matter G4: 150 gil -> 48 gil
Dark Matter G5: 350 gil -> 80 gil


A temporary countermeasure has been implemented for the following issue:

- For the issue wherein the “Manor Sentries” found within the Haukke Manor dungeon could become stuck and prevent players from progressing through the instanced dungeon, we have changed the original location of “Manor Sentries” to the second floor.

The following issues have been addressed:

- The server would crash under certain conditions during instanced dungeons.
- Characters would sometimes get stuck in the “Binding Coil of Bahamut” dungeon after the party was wiped out.
- Bomb Boulders would sometimes fail to appear in “The Navel (Hard)” battle.
- Certain monsters would sometimes get stuck in the “Amdapor Keep” dungeon.
- The option to return to Home Point would not display when completing a primal battle while being KO’d.
- The entry point for the “The Thousand Maws of Toto-Rak” dungeon was shown in the field in the “Stinging Back” guildhest.
- The “Steel Reign” FATE would sometimes fail to appear.
- Completing the “Behold Now Behemoth” FATE would sometimes cause the server to crash.
- If the player was disconnected during the “Lady of the Vortex” instanced battle, the Duty List, Journal, and Journal Map may display incorrectly.
- The “Notorious Biggs” quest could sometimes be progressed without completing the instanced battle.
- There were occasions where it was impossible to target the snowman in the “Speak Softly to Me” quest.
- The cutscene was cancelled if the player was attacked during the “Lord of Crags” cutscene.
- If a player logged out while being bound by duty within an instance, and logged back in after conclusion of the instance, the free company chat would not work.
- Mog Letters were not sent properly in some instances.
- Certain conditions would sometimes cause the server to crash while interacting with the free company “Company Chest”.
- The “Reach” gauge was sometimes not selectable when in a new, unknown gathering point.
- In some instances, the specified items to collect were incorrect in the “A Relic Reborn” quest.
- In some instances, the specified enemies to defeat were incorrect in the “A Relic Reborn” quest.



The following are details regarding the maintenance operation that occurred on Sep. 12, 2013 from 0:00 to 7:55 (GMT).

[Countermeasures to Relieve Heavy Server Stress on Duty Finder] This maintenance implemented countermeasures to further relieve heavy server stress on the Duty Finder and instance-related Worlds.

With this measure, group matching is now split among the following three groups for the selection process.

- Japan data centre
- Group 1
Aegis/Atomos/Carbuncle/Garuda/Gungnir/Kujata/Ramuh/Tonberry/Typhon/Unicorn

- Group 2
Alexander/Bahamut/Durandal/Fenrir/Ifrit/Ridill/Tiamat/Ultima/Valefor/Yojimbo/Zeromus

- Group 3
Anima/Chocobo/Hades/Ixion/Mandragora/Masamune/Pandaemonium/Titan/Asura/Belias

- North American/European data centre
- Group 1
Adamantoise/Balmung/Cerberus/Coeurl/Faerie/Goblin/Midgardsormr/Odin/Sargatanas/Siren

- Group 2
Behemoth/Diabolos/Excalibur/Famfrit/Lamia/Leviathan/Lich/Shiva/Ultros/Brynhildr

- Group 3
Cactuar/Exodus/Gilgamesh/Hyperion/Malboro/Moogle/Phoenix/Ragnarok/Mateus/Zalera

*Groupings are determined by balancing levels, number of people, class/jobs, and adjusted so as to help provide a smooth matching process.

[Increased Number of Instance Worlds]
The Duty Finder and quest instance battles are handled internally in their own separate Worlds. In addition to the above measure of easing server load by splitting the selection pool amongst the above groups, we have also increased the number of instance-related Worlds on which battles occur.

This measure allows the facilitation of more instances, decreasing cases in which players must wait for an instance to become open after they have already been matched by the Duty Finder or the quest instance battle has been initiated.

[Addition of New Worlds]
We have implemented the addition of the following Worlds.

- Japan data centre
Unicorn/Yojimbo/Asura/Belias/Zeromus

- North American/European data center
Mateus/Brynhildr/Zalera

Please note that upon first opening of the new Worlds, we predict a concentrated influx of characters in the low-level zones of said Worlds. Therefore until characters have evened out and dispersed into the various zones, please be aware we will be implementing Character Creation and login restrictions.

In addition, as a result of splitting the group matching for the Duty Finder into 3 groups, we are now able to expand our services easier. We will continue to monitor concurrent logins and the increase of new players in each World and if needed, periodically add new Worlds starting from October.

We will announce details regarding this at a later time.

[Implementation of Auto-Logout]
Because there are so many users attempting to login even when the maximum allowed number of concurrent logins has already been reached (in other words when login restrictions are in place) we have now implemented an auto-logout feature. In an attempt to provide as many users as possible a chance to login, characters that appear to be inactive for thirty minutes will be automatically logged out of the game.

[Login Restrictions Directly After Maintenance] In the time period just after maintenance has completed, we predict a rush of characters logging in simultaneously. In order to prevent any technical difficulties due to this login rush, we will be temporarily placing severe login restrictions. These login restrictions may occur frequently lasting from a few minutes to ten minutes; however, restrictions will be lifted in a gradual manner as login status is carefully monitored. We ask for your patience and understanding in this matter.