Final Fantasy XIV adds afk kick feature; Amdapor Keep speed run no longer available

Final Fantasy XIV: A Realm Reborn

The very long maintenance that Square Enix had this week for Final Fantasy XIV fixed a lot of things in the game that surely makes the experience a lot better.

Since the launch of Final Fantasy XIV, one of the problems everyone was having is that they could’t log in due to the servers they’re were playing was always full. The reasoning behind the congestion of many servers in the game is due to the people not logging out since they know it will be impossible to get in. To relieve the congestion and to allow more people to play the game, Square Enix added an afk (Away From Keyboard) kick feature that boots out players who have been idle for 30 minutes. Did the new feature help? Absolutely, it opens up server slots where people rarely encounter the Server is Always Full error message.

In addition to the afk kick feature, Square Enix also implemented some fixes and exploits to make the game fair to everyone. For those who are already fifty, I’m sure everyone is spoiled by now due to the fact that they can speed-run the Amdapor Keep dungeon. Well, Square Enix found that exploit and patched it up to make sure the next time the players group run the dungeon, you will now have to fight all the mobs before proceeding to the boss chamber. Yes, it’s slightly disappointing but it seems Square Enix surely likes everyone to spend their time grinding for gears and items in the game the hard way.

Here are the list of issues being address in the newest patch release this week:

-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 canceled 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.