ffxiv Known Issues and Status of Endwalker Release (Updated Dec. 9)

[Alhena 221]

Square Enix has updated the following post regarding known issues occurring since Endwalker's release. Recent additions to the post include a notice about sound-related issues and a problem with ninja's Hollow Nozuchi action.

Known Issues and Status of Endwalker Release (Source)

Hello, this is FINAL FANTASY XIV Producer & Director, Naoki Yoshida.

We are currently experiencing the highest level of server congestion we have ever encountered since the game officially commenced its service. Please read the separate announcements (https://sqex.to/QDFMi) (https://sqex.to/eUgyp) for our findings and responses to this issue.

We will be using this announcement to share information about issues that have so far been confirmed to have a high impact or are highly visible, and our responses to them. The situation is constantly evolving, so we will be updating this announcement periodically to keep players informed. (Any bugs already fixed have been deleted)

■The effects of Forked Raiju Ready and Fleeting Raiju Ready are cancelled with execution of Hollow Nozuchi (Added: Dec. 9 4:50 a.m. PST)

I’d like to report an issue about the two actions Forked Raiju and Fleeting Raiju, available for Ninja. We were making adjustments to each job after the Media Tour right up to the last minute before the expansion’s release, and while the execution status of the corresponding action is per the correct specifications (“cancelled with the use of a melee weaponskill”), Hollow Nozuchi should have been set not as a weaponskill but as an ability to match our specifications. However, this setting was unfortunately left out. It should have been correctly set as an ability. We deeply apologize for this.

Since a fix will be required for this on the client, we will implement it alongside fixes for other bugs in Patch 6.01.

Patch 6.01 will mainly address bugs, but please rest assured that we will continue to make adjustments to the actions of each job, not just Ninja, in Patch 6.05 and subsequent patches based on your feedback, starting with those that can be adjusted.

■Sound related issues (Added: Dec. 7 5:15 a.m. PST)

We have been receiving reports of sound related problems and feedback. We are planning to fix the sound driver in the next patch for some bugs that cause sound to be lost under certain setups, such as no audio playback during cutscenes. We will check the factors that cause these problems and address them individually, so we would appreciate your patience. We will also check for feedback such as "it's getting harder to hear" or "the sound doesn't feel right" individually, and if any adjustments are needed, we will fix them in the patch as well.

■ Automatic logout due to inactivity during ending credits (Added: Dec. 5 2:30 a.m. (PST)

We have received reports of players being automatically logged out during the ending credits of A Realm Reborn, Heavensward, Stormblood, or Shadowbringers due to 30 minutes of inactivity. Upon investigation, we discovered that the procedure for avoiding automatic logout was missing for these ending credits, for which I am truly sorry. As for the ending credits of Endwalker, this procedure is included and you will not be logged out for inactivity during its duration.

We apologize for the inconvenience, but when viewing the ending credits for A Realm Reborn, Heavensward, Stormblood, and Shadowbringers, we ask that you press a button on your controller, press a key on your keyboard, or click with your mouse. By doing so before 30 minutes pass, you will be able to reset the automatic logout timer. Please also note that simply moving your mouse cursor will not prevent automatic logout.

We are working on implementing a patch to address this issue as soon as possible and kindly ask for your patience.

■EXP from main scenario quests in Endwalker (Added: Dec. 5 2:30 a.m. (PST)

In an interview conducted before the release of Endwalker, I said you could reach the level cap for one job by playing the main scenario quest. However, we have been receiving feedback from players pointing out that the main quest scenario does not reward sufficient amount of EXP to reach the level cap. I deeply apologize for the carelessness of my statement and the confusion caused by it.

We have been balancing EXP gain by taking into account EXP obtained by completing main quest scenarios, completing duties from main quest scenarios, first time completion of duties, average rested bonus, and mapping the realm, so that level cap could be achieved by progressing through the main quest. However, our calculations were slightly off even with the considerations above.

The team test played the update several times over, but due to last minute adjustments made to various content, a small margin of error occurred. We apologize for the issue caused by this. In addition, because of my ambiguous statement that specifically mentioned by playing the main scenario quest, I think many players believe that level cap can be achieved through EXP rewarded through quests alone. Again, I deeply apologize for the confusion my statement caused.

Besides main scenario quests, additional EXP can be gained to reach level cap faster by completing aether current attunement quests and duty roulettes two to three times on top of the main scenario quests. The actual amount may vary slightly depending on your rested bonus, but we’d be grateful if you could consider doing this.

This is a balancing issue rather than a bug but was exacerbated by my own careless comment. Once again, I apologize for the confusion.

■Issues with dyeing paladin’s 5.0 job-specific gear

We are receiving reports that the color of the dye used is not reflected in the following paladin’s 5.0 job-specific gear when they are dyed.

・Idealized Chevalier's Cuirass
・Idealized Chevalier's Gauntlets
・Idealized Chevalier's Poleyns
・Idealized Chevalier's Sollerets

We apologize for the inconvenience this is causing.

Upon investigating the issue, we discovered that material data was inadvertently replaced for some gear during the fix to address caving and piercing issues when only the modeling should have been changed. This resulted in the dye color not being reflected in the graphics of the above gear. The color data for the dye itself is correctly registered, but the issue is preventing it from displaying.

We will address this by replacing the data for the affected gear in patch 6.01. While dyeing a piece of gear will register the color data on the gear, you will not be able to see it reflected in-game. Therefore, we ask players to refrain from dyeing the above pieces of gear until the issue is addressed in Patch 6.01.

We have seen cases where this issue does not occur with certain races and genders, but we would like to announce it nonetheless to prevent confusion.

■Movement issues with NPCs accompanying the player in certain quests

We are receiving reports that NPCs accompanying the player in certain quests introduced with Patch 6.0 are seen standing on water or floating in the air.

We have confirmed that this issue only occurs when an extremely large number of players are present in a single area, which causes the system to attempt to cull the number of NPCs in that area. The client will have to be patched to fix the root cause, so we kindly ask for more time to address this. If you encounter this issue, taking the steps below may likely resolve it. We apologize for the inconvenience and thank you for your understanding.

① Adjust the position of your character until the NPC loads properly.
② Stop the NPC from accompanying you by using the Aethernet or some other means of teleportation, and then have that NPC accompany you again.

We have confirmed that the affected NPC will acquire the correct coordinates and load back into the intended location once the high server load subsides. We apologize for any inconvenience this may be causing and thank you for your understanding.

We will continue to announce issues that have a high impact or are highly visible through this news.