Kage Posted November 10, 2015 Share #1 Posted November 10, 2015 http://na.finalfantasyxiv.com/lodestone/news/detail/680a126077a5aff59f13bcfa164ec20b5e53f7ea We have confirmed the following issue is occurring. Please refrain from performing the following actions, and be sure to read the description of the issue carefully. [Details] If you summon your retainer while queued in the duty finder, get matched, and zone to the instance with your retainer still summoned, you will become unable to summon your retainer thereafter. [Temporary Solution] We are sorry, but ask that you take the following steps until this issue has been addressed. - If you have summoned your retainer while being matched in the duty finder, please return them before entering the instance. - Refrain from summoning your retainer while queued in the duty finder. The issue is being investigated and addressed, and we ask for your patience and understanding as we strive to resolve this promptly. We are also currently investigating ways to help those who have currently already become unable to summon their retainers. We apologize for any inconvenience this may cause. [Edited on Nov. 10, 2015 at 5:15 (PST)] Players affected by this issue will be able to summon their retainers again after this issue has been resolved, so we ask that you please wait until this issue has been resolved. Link to comment
Kage Posted November 10, 2015 Author Share #2 Posted November 10, 2015 [Known Issue] - An issue wherein the client may crash during the boss fight in “Sohm Al”. (Mac Version only) [Known Issue] ・An issue wherein players may be unable to progress "The Sunken Temple of Qarn (Hard)". Link to comment
Kage Posted November 11, 2015 Author Share #3 Posted November 11, 2015 As of this post, none of these issues have been stated to have been resolved. Link to comment
Kage Posted November 11, 2015 Author Share #4 Posted November 11, 2015 Investigation and Handling of Known Issues Occurring After Patch 3.1 (Nov. 11) We sincerely apologize for several urgent issues that have been occurring since Patch 3.1 went live, such as becoming unable to summon retainers and issues with “The Diadem”. We would like to provide an update on the current situation regarding the investigation and handling of these urgent issues. [issues to be addressed in an emergency maintenance scheduled for Nov. 12, 2015] ・An issue wherein you will be unable to summon your retainer if you had queued and entered a duty with your retainer still summoned. * For players currently unable to summon their retainer, you will become able to summon them again after this fix is implemented. * For all players, please follow the preventative measures below until this issue has been addressed: - Refrain from summoning your retainer when queueing in the duty finder. - If you have already summoned your retainer when you get matched in the duty finder, please dismiss your retainer before entering the instance. ・A rare issue in “The Diadem” wherein the time limit may expire almost immediately upon entering. ・An issue in “The Sunken Temple of Qarn (Hard)” wherein players may be unable to progress. ・An issue wherein characters designated as a housemate may not be able to teleport to the house properly. ・An issue wherein field servers may crash under certain conditions. ・An issue with the Vanu Vanu Beast Tribe Quests wherein, when a player's reputation with the Vanu Vanu ranks up and additional bonus quests become available to the player, quests that have already been completed and cannot be accepted again on the same day become selected. ○Detailed Explanation Players are able to accept up to three Vanu Vanu Beast Tribe per day. When your reputation with the Vanu Vanu tribe ranks up, you will be able to accept additional daily quests beyond that three-per-day restriction as a bonus for ranking up. However, there is an issue wherein previously completed quests are included in the bonus quest candidate pool, and if one of the previously completed quests is selected by the system to be a bonus quest, it will not appear for the player. When this occurs, the number of quests that can be accepted per day will be reduced. To address this issue, we are making changes to the Vanu Vanu Beast Tribe Quests system so that only newly added quests will candidates for being bonus quests. With this, all players who have ranked up on the same day will be able to accept the same number of quests. Please note that bonus quests do not appear for players whose reputation with the Vanu Vanu is at ranks 7 and 8. * The 6 issues above are planned to be addressed in an emergency maintenance on Nov. 12, 2015. The specific time of this emergency maintenance will be mentioned at a later time. [issues Being Investigated] ・An issue in “The Diadem” wherein members of a pre-formed party may be unable to enter properly. * If this issue occurs, please attempt to re-enter the instance. * As a temporary countermeasure, please use your Company Workshop’s Flight Control Panel to change the next airship exploratory mission time from 20min to 5min on the ship which was used to enter “The Diadem”. This will be addressed in the Nov. 12, 2015 Emergency Maintenance. ・An issue in “The Diadem” wherein party leaders may not be able to enter properly when entering as an alliance. * Until this issue is resolved, we ask that you consider not entering as an alliance. ・An issue wherein instance servers may crash. ・An issue wherein the game client may crash during a boss fight in “Sohm Al”. (Mac Version only) * The dev team has already discovered what is causing these issues. Once we have verified that there are no problems with the fixes, we will implement them accordingly. We would like to sincerely apologize for all of the inconveniences that these issues are causing, and we thank you for your continued patience and understanding. Link to comment
Kage Posted November 12, 2015 Author Share #5 Posted November 12, 2015 Nov. 11, 2015 11:00 p.m. to Nov. 12, 2015 3:00 a.m. (PST) EMERGENCY MAINTENANCE WITH HOTFIXES We will be performing emergency maintenance on all Worlds at the time below in order to accompany Patch 3.1 Hotfixes. During this period, FINAL FANTASY XIV will be unavailable. * The World Transfer Service will be suspended 15 minutes before maintenance begins, and will be unavailable until maintenance has ended. We apologize for any inconvenience this may cause and thank you for your understanding. [Date & Time] Nov. 11, 2015 11:00 p.m. to Nov. 12, 2015 3:00 a.m. (PST) * Completion time is subject to change. [Affected Worlds] All Worlds Link to comment
Kage Posted November 12, 2015 Author Share #6 Posted November 12, 2015 Update to the investigations! http://na.finalfantasyxiv.com/lodestone/news/detail/996bf5ef4b4f2ac8668638554d819c846522e5f3 We sincerely apologize for several urgent issues that have been occurring since Patch 3.1 went live, such as becoming unable to summon retainers and issues with “The Diadem”. We would like to provide an update on the current situation regarding the investigation and handling of these urgent issues. [issues to be addressed in an emergency maintenance scheduled for Nov. 12, 2015] ・An issue wherein you will be unable to summon your retainer if you had queued and entered a duty with your retainer still summoned. * For players currently unable to summon their retainer, you will become able to summon them again after this fix is implemented. * For all players, please follow the preventative measures below until this issue has been addressed: - Refrain from summoning your retainer when queueing in the duty finder. - If you have already summoned your retainer when you get matched in the duty finder, please dismiss your retainer before entering the instance. ・A rare issue in “The Diadem” wherein the time limit may expire almost immediately upon entering. ・An issue in “The Sunken Temple of Qarn (Hard)” wherein players may be unable to progress. ・An issue wherein characters designated as a housemate may not be able to teleport to the house properly. ・An issue wherein field servers may crash under certain conditions. ・An issue with the Vanu Vanu Beast Tribe Quests wherein, when a player's reputation with the Vanu Vanu ranks up and additional bonus quests become available to the player, quests that have already been completed but cannot be accepted again on the same day are offered. ○Detailed Explanation Players are able to accept up to three Vanu Vanu Beast Tribe per day. When your reputation with the Vanu Vanu tribe ranks up, you will be able to accept additional daily quests beyond that three-per-day restriction as a bonus for ranking up. However, there is an issue wherein previously completed quests are included in the bonus quest candidate pool, and if one of the previously completed quests is selected by the system to be a bonus quest, it will not appear for the player. When this occurs, the number of quests that can be accepted per day will be reduced. To address this issue, we are making changes to the Vanu Vanu Beast Tribe Quests system so that only newly added quests will candidates for being bonus quests. With this, all players who have ranked up on the same day will be able to accept the same number of quests. Please note that bonus quests do not appear for players whose reputation with the Vanu Vanu is at ranks 7 and 8. * The 6 issues above are planned to be addressed in an emergency maintenance on Nov. 12, 2015. The specific time of this emergency maintenance will be mentioned at a later time. [update: Nov. 12, 2015 4:15 a.m. (PST)] The above six issues were addressed in the Emergency Maintenance which occurred from Nov. 11, 2015 11:00 p.m. to Nov. 12, 2015 1:45 a.m. (PST). We apologize for any inconvenience caused. [issue Partially Resolved] ・An issue in “The Diadem” wherein members of a pre-formed party may be unable to enter properly. [update: Nov. 12, 2015 4:15 a.m. (PST)] The above issue was addressed in the Emergency Maintenance which occurred from Nov. 11, 2015 11:00 p.m. to Nov. 12, 2015 1:45 a.m. (PST), but regarding the separate issue in which only certain party members cannot enter properly, it has been confirmed and is still under continued investigation. * As a temporary countermeasure, the time the next airship exploratory mission will be available for the ship which was used to enter “The Diadem” from your Company Workshop’s Flight Control Panel has been changed from 20min to 5min. [issues Being Investigated] ・An issue in “The Diadem” wherein party leaders may not be able to enter properly when entering as an alliance. * Until this issue is resolved, we ask that you consider not entering as an alliance. ・An issue wherein instance servers may crash. ・An issue wherein the game client may crash during a boss fight in “Sohm Al”. (Mac Version only) * The dev team has already discovered what is causing these issues. Once we have verified that there are no problems with the fixes, we will implement them accordingly. We would like to sincerely apologize for all of the inconveniences that these issues are causing, and we thank you for your continued patience and understanding. Link to comment
Kage Posted November 12, 2015 Author Share #7 Posted November 12, 2015 FINAL FANTASY XIV Hotfixes (Nov. 12, 2015) The following issues have been addressed. An issue in “The Diadem” wherein all members of a pre-formed party may be unable to enter properly. *Regarding the separate issue in which only certain party members cannot enter properly, it has been confirmed and is still under continued investigation. * As a temporary countermeasure, the time the next airship exploratory mission will be available for the ship which was used to enter “The Diadem” from your Company Workshop’s Flight Control Panel has been changed from 20min to 5min. An issue wherein you will be unable to summon your retainer if you queue and enter a duty with your retainer still summoned. * For players who were unable to summon their retainer, this fix allows you to summon them again. *There was also a related issue in which the purchase would fail when trying to purchase items that were put up for sale in the marketplace by the retainer who was unable to be summoned, but this issue has also been fixed. A rare issue in “The Diadem” wherein the time limit may expire almost immediately upon entering. An issue in “The Sunken Temple of Qarn (Hard)” wherein players may be unable to progress. An issue wherein characters designated as a housemate may not be able to teleport to the house properly. An issue wherein field servers may crash under certain conditions. An issue with the Vanu Vanu Beast Tribe Quests wherein, when a player's reputation with the Vanu Vanu ranks up and additional bonus quests become available to the player, quests that have already been completed and cannot be accepted again on the same day become selected. * To address this issue, we have made changes to the Vanu Vanu Beast Tribe Quests system so that only newly added quests will be candidates for bonus quests. With this, all players who have ranked up on the same day will be able to accept the same number of quests. Link to comment
Warren Castille Posted November 12, 2015 Share #8 Posted November 12, 2015 Unlisted bug in A4, where you can push Manipulator around with Water and potentially Blank. Doesn't work in Savage. Link to comment
Kage Posted November 17, 2015 Author Share #9 Posted November 17, 2015 FINAL FANTASY XIV Hotfixes (Nov. 16, 2015) ■The rate at which the Limit Break Gauge fills has been reverted to pre-Patch 3.1 values. ■The following issues have been fixed: ・An issue in "The Void Ark" during the Cetus battle wherein the damage dealt by Cetus's "Hydroburst" was incorrect. ・An issue in "The Void Ark" during the Irminsul/Sawtooth battle wherein Sawtooth would use "Shockwave Stomp" even after Irminsul had been defeated. ・An issue in "The Void Ark" during the Cuchulainn battle wherein the "Vulnerability Down" status would not wear off. ・An issue in "Pharos Sirius (Hard)" during the 8th Order Patriarch Be Gu battle wherein Corrupted Gels would not use "Corrupture". ・An issue in "Pharos Sirius (Hard)" during the 8th Order Patriarch Be Gu battle wherein players would lose control of their characters. ・An issue in "Alexander - The Burden of the Father" wherein the boss "The Manipulator" could be affected by knockback. ・An issue in "The Diadem" wherein the barrier around the entrance would not disappear, preventing the duty from commencing. ・An issue in "The Diadem" wherein certain monsters could not fight back under certain conditions. ・An issue in "The Diadem" wherein aetherial turbulences could not be targeted while unmounted. ・An issue when entering "The Diadem" wherein members of a pre-formed party would be unable to enter properly. ・An issue when entering "The Diadem" from company workshop's flight control panel wherein party leaders of a pre-formed alliance would be unable to enter properly. ・An issue during the battle in the main quest "As Goes Light, So Goes Darkness" wherein players could be attacked by untargetable NPCs. ・An issue during the quest "I'd Rather Be Cannon Fodder" wherein players would obtain a nameless item. ・An issue with the Idyllshire NPC "Splendors Vendor" wherein the amount of materials needed to exchange for the following items in "Tradecraft Items" was incorrect: Purified Coke (HQ) / Raziqcoat (HQ) Dryad Sap (HQ) / Moonbeam Silk (HQ) / Odorless Animal Fat (HQ) ・An issue wherein the stats on "Void Ark Belt of Aiming" were incorrect. ・An issue wherein instance servers may crash under certain conditions. Link to comment
Kage Posted November 24, 2015 Author Share #10 Posted November 24, 2015 All Worlds Maintenance Nov 24 In order to accompany Patch 3.1 HotFixes, we will be performing maintenance on all Worlds at the time below. During this period, FINAL FANTASY XIV will be unavailable. *With the implementation of these HotFixes, when a high-ranking player with a certain amount of Rank Points (RP) or more wins a match in the Lord of Verminion tournament, the minimum amount of points gained will be raised from “1” to “30”. This adjustment will be applied after these HotFixes are implemented, so there may be a large difference between the amount of points gained from matches before and after it is applied. Please be careful when participating in the tournament. The schedule of the tournaments is managed by the server, and we must cancel the tournaments after the next one for an extended period of time in order to change the schedule. We ask for your understanding with regards to this matter. * The World Transfer Service will be suspended 15 minutes before the maintenance, and will be unavailable until maintenance has ended. * Reservations for Ceremonies of Eternal Bonding cannot be made from the time maintenance ends until Nov. 27, 2015 2:00 a.m. (PST). We apologize for the inconvenience due to the long time frame, and thank you for your understanding. [Date & Time] Nov. 24, 2015 9:00 p.m. to Nov. 25, 2015 2:00 a.m. (PST) * Completion time is subject to change. [Affected Worlds] All Worlds Note! Maintenance starts ~2 hours earlier than usual. Link to comment
Kage Posted November 30, 2015 Author Share #11 Posted November 30, 2015 All Worlds Maintenance Nov 30 We will be performing maintenance on all Worlds at the time below in order to accompany Patch 3.1 Hotfixes. During this period, FINAL FANTASY XIV will be unavailable. * The World Transfer Service will be suspended 15 minutes before the maintenance, and will be unavailable until maintenance has ended. * Reservations for Ceremonies of Eternal Bonding cannot be made from the time maintenance ends until Dec. 4, 2015 1:00 a.m. (PST). We apologize for any inconvenience this may cause and thank you for your understanding. [Date & Time] Nov. 30, 2015 9:00 p.m. to Dec. 1, 2015 2:00 a.m. (PST) * Completion time is subject to change. [Affected Worlds] All Worlds Something to expect from this. Changes to Duty Finder algorithm Greetings, Thank you for the continued feedback regarding the matching speed of the Duty Roulette since Patch 3.1. I wanted to share an update regarding the issue wherein the queue time for Duty Roulette: Expert tends to be very long during peak hours. This led us to investigate the type of content players are queueing for and the roles they’ve selected when queueing. Our investigation has shown the reason that the queue times have increased during peak hours is because of two measures that were implemented in Patch 3.1. Since a large variety of content that utilizes the instance servers was implemented in Patch 3.1, the server load placed on the server when characters are transferred to an instance has spiked. Therefore, to prevent cases where the instance or World areas could crash, we have placed a limit on the number of character transfers that take place per minute. However, as time has passed since the release of Patch 3.1 and we have confirmed that the servers remain quite stable, we will remove this restriction today. It will not require a hotfix or maintenance to remove this restriction. We will continue to monitor the server load over the weekend, and if no problems arise, we will not reinstate these restrictions. Another measure that was implemented in Patch 3.1 would prioritize the queue for players who are queueing for new content specifically over queueing via the Duty Roulette. We have taken a look at the data and confirmed that more players are queueing for Duty Roulette: Expert over simply selecting Saint Mocianne's Arboretum and Pharos Sirius (Hard) so we will adjust the algorithm during the hotfix planned for Tuesday of next week. After the adjustment, whether the player queues for specific content or the Duty Roulette, they will be handled equally. Once these changes take place, the issue wherein queue time are longer during peak hours should be addressed. With that said, we will continue to monitor server data and make adjustments as needed. Link to comment
Kage Posted December 1, 2015 Author Share #12 Posted December 1, 2015 FINAL FANTASY XIV Hotfixes (Nov. 30, 2015) ■The wait time to re-enter “The Diadem” has been reduced from 120 minutes to 45 minutes. * We will continue to monitor player feedback regarding "The Diadem" and make further adjustments as necessary. ■Adjustments have been made to the Duty Finder algorithm where queues will be based upon queue order regardless of being queued for specific content or for a roulette. ■The shortcut buttons (XYAB/□△×◯) used in combination with the LB/L1 buttons on the gamepad/controller for Lord of Verminion have been fixed to the following button settings, regardless of the player’s button configuration. LB(L1)+X(□): Execute Action LB(L1)+Y(△): Select all minions that are the same type as the minion currently selected LB(L1)+A(×): Select all friendly minions that are the same type as the minion currently selected LB(L1)+B(◯): Select all friendly minions that are near the minion currently selected * There is currently an issue with the tutorial and play guide wherein the button texts are incorrect. ■The following issues have been fixed: • An issue in “The Void Ark” during the Echidna fight wherein the amount of damage displayed for “Demonic Descent” was not displaying correctly. • An issue with the Lord of Verminion Challenge “Stage 1: Tutorial” wherein the player was unable to progress when under certain conditions. • An issue with the Lord of Verminion Challenge “Stage 6: Off the Deepcroft” wherein a channeling line was displayed between certain minions summoned on the player’s side and the boss minion. • An issue with the Lord of Verminion Challenge “Stage 23: The Binding Coil” wherein certain minions would not perform actions properly. • An issue with the quest “The Greatest Story Never Told” wherein the player would lose control of their character while progressing through the quest. • An issue in the Gold Saucer wherein failing the GATE “Vase Off” would count towards the number of GATEs participated for the Challenge Log. • An issue with the Grand Company NPC “OIC Quartermaster” and the housing area NPC “Resident Caretaker” wherein under certain conditions purchases were not being processed properly when purchasing items with Company Credits. • An issue with the Vanu Vanu Beast Tribe Quest “A Bone to Pick” wherein certain texts were appearing incorrectly. Link to comment
Kage Posted December 3, 2015 Author Share #13 Posted December 3, 2015 Duty Finder - Duty Roulette Queues by Zhexos Once more we'd like to thank everyone for their continued feedback regarding Duty Finder matching speeds. We've been reading comments from players pointing out there may be specific issues that haven't been addressed. Using this information, and the player matching data itself, the development team investigated the issue. As a result, they were able to determine that there may be cases where the matching queue for the Duty Roulette halts under specific conditions. The conditions are as follows: When a pre-made party queues for a Duty Roulette, and their party consists of three or fewer members, there is a possibility where that group will be matched with another pre-made group that also consists of three or fewer members under certain conditions. This in turn causes an unusual party setup to be made which results in all queues behind this halting. Once the above issue occurs, all queues created after this, whether they be solo or in a pre-formed party, will be matched into a queue that is suspended which results in these long queue times. The queue that was suspended will resume under certain conditions; however, it can take a long time until this happens, causing congestion in Duty Roulette matching. Additionally, this situation has a high possibility of occurring during peak hours. Because of this, individuals may think that the queue speed fluctuates depending on the time of day that they're queueing. This issue only occurs when queueing for Duty Roulettes, and doesn't affect the Duty Finder's normal matching system. We were able to address this issue on our end, and we're currently working to implement a hotfix by the end of the week. However, we must make sure that it's properly tested, therefore we would like some additional time to do checks. We apologize for the inconvenience this and other related issues have been causing players. Additionally, we have received feedback from players requesting that we revert the Duty Roulette matching system to a pre-Patch 3.1 setup. However, the individual content matching that content in Patch 3.1 utilizes was built on top of the new matching system. Therefore, reverting the system will greatly affect these, as well as require even more time for investigation. So we're carefully addressing the issue and putting our efforts into optimizing the current system. The previous algorithm used a system where it first selected content and then looked for participants, whereas the new algorithm will first form a party as quickly as possible and then select the content. This new system was developed to provide a much quicker matching experience for everyone. We are aware that there have been issues, especially inconveniencing those trying to utilize the Duty Roulette; however, based on data we've been investigating, we can confirm the matching speed outside of the Duty Roulette is faster than that before Patch 3.1. Once more, we sincerely apologize for the inconvenience this has caused, and would appreciate your understanding as we work to address this issue. Link to comment
Kage Posted December 4, 2015 Author Share #14 Posted December 4, 2015 http://na.finalfantasyxiv.com/lodestone/news/detail/83d43a994749dc05a633bc0cc20144aa65978fc5 We would like to provide an update regarding the issue of extremely slow matching process when queuing for the Duty Roulette. During yesterday's investigation, we were able to determine that there are cases in which the matching queue for the Duty Roulette halts under specific conditions. We were able to address the cause of the issue, and after a large-scale inspection, verified that the system is working properly. However, during the pattern verification that continued afterwards, we also confirmed that another issue (with a different cause) is occurring even after the fix, wherein, under certain conditions, match times become increasingly slower over time for solo players queued in the Duty Finder. We are continuing to investigate, address, and verify the issue is fixed, but in order to make certain that the issue is thoroughly addressed, we may require until the beginning of next week. We will post further details on the forums at a later time. Since this issue affecting Duty Roulettes in the current open Worlds occurs when a pre-formed party queues for the Duty Roulette, we ask that you please queue in as a solo player or in a 4-player (8-player) party during this weekend, especially at peak times. This will keep the Duty Finder Roulette running smoothly, without congestion. We sincerely apologize for the inconvenience, and thank you for your patience and understanding. Link to comment
Kage Posted December 4, 2015 Author Share #15 Posted December 4, 2015 please queue in as a solo player or in a 4-player (8-player) party during this weekend, especially at peak times. Link to comment
Warren Castille Posted December 4, 2015 Share #16 Posted December 4, 2015 "Please troll us." God damn, SE, the fucking STATE of your servers right now. Link to comment
Lydia Lightfoot Posted December 4, 2015 Share #17 Posted December 4, 2015 This isn't surprising. They'll probably just remove the function for being able to queue for something other than solo and full group. It fits with their agenda of removing the MM from MMO by forcing players into numerous solo duties over the course of their questing, rather than making those duties scale by party size and allowing players to complete them in a duo, trio, or light party if those players prefer to do their questing with friends. Link to comment
Melkire Posted December 4, 2015 Share #18 Posted December 4, 2015 Yyyyyeaaaaah, think they might've goofed with this announcement. Usually for issues of this magnitude, developers will just state, "We've identified the cause and we're working on a solution, please stay tuned" and leave it at that. Prevents malicious users from deliberately exploiting and/or impacting the game in a harmful fashion. ...good to know though, I suppose? EDIT: That said, I don't see a conspiracy here to cull "massively multiplayer," just a genuine, honest-to-God issue with... dun dun dunnnn... their infrastructure. Link to comment
Caspar Posted December 4, 2015 Share #19 Posted December 4, 2015 I just read from all this "squaresoft please give our team money so we can improve our server infrastructure and hire some more programmers." ;_; Link to comment
Teadrinker Posted December 5, 2015 Share #20 Posted December 5, 2015 I just read from all this "squaresoft please give our team money so we can improve our server infrastructure and hire some more programmers." ;_; From the small team they've got the amount of issues that DON'T make it live is pretty damn amazing. These guys have to be working themselves to the bone. Link to comment
Warren Castille Posted December 5, 2015 Share #21 Posted December 5, 2015 I just read from all this "squaresoft please give our team money so we can improve our server infrastructure and hire some more programmers." ;_; From the small team they've got the amount of issues that DON'T make it live is pretty damn amazing. These guys have to be working themselves to the bone. On the one hand, my hat off to them. On the other hand, you don't get to brag about having five million accounts and then complain you have no staff. You're either successful or you aren't. I am but a humble caveman lawyer, who doesn't understand how to do server infrastructure. Link to comment
Ryanti Posted December 5, 2015 Share #22 Posted December 5, 2015 I just read from all this "squaresoft please give our team money so we can improve our server infrastructure and hire some more programmers." ;_; From the small team they've got the amount of issues that DON'T make it live is pretty damn amazing. These guys have to be working themselves to the bone. They probably are. IIRC Yoshi had a little moment in one of the recent Live Letters in which he made a passive aggressive comment about being understaffed that caught a lot of people's attention. There's been a lot of rumor about that recently. I'm starting to believe a lot of XIV's revenue is not going back into XIV. I don't understand why Square isn't re-investing back into the game. XI wrapped up all new content, how about putting some of them on XIV's staff? On the one hand, my hat off to them. On the other hand, you don't get to brag about having five million accounts and then complain you have no staff. You're either successful or you aren't. It's not so much Yoshi being a hypocrit as much as it is the Marketing Department trying to do their job. If I was working in that department I'd definitely be trying to emphasize the game's success and mask the failures. Trailers and such are marketing tools after all. Link to comment
Warren Castille Posted December 5, 2015 Share #23 Posted December 5, 2015 I didn't mean to imply hypocrisy; I believe both statements. I'm just frustrated that SE has a hit on their hands (maybe?) and are letting it languish on shitty servers. Link to comment
Ryanti Posted December 5, 2015 Share #24 Posted December 5, 2015 I didn't mean to imply hypocrisy; I believe both statements. I'm just frustrated that SE has a hit on their hands (maybe?) and are letting it languish on shitty servers. It really makes me frown when I realize that this MMO has gone from an inspiring Cinderella story of redemption to a game in which the dev team has lost their way in regard to their own audience in the matter of a single delay and a single patch. The populace of XIV have shifted to such a pessimistic stance since 3.0 got stale, especially since 3.1. Who can blame them? I'm starting to feel it. To be fair they made some design mistakes, not just technical ones. It's starting to feel more and more like Square Enix five years ago to me. This technical crap on top of an already disappointed fanbase is not good. Not good at all. I don't want to say that the fanbase is abandoned the game, but XIV has been bleeding subs for months. 3.2 Needs to fix a lot of this shit or else it's going to continue. Link to comment
Warren Castille Posted December 5, 2015 Share #25 Posted December 5, 2015 I didn't mean to imply hypocrisy; I believe both statements. I'm just frustrated that SE has a hit on their hands (maybe?) and are letting it languish on shitty servers. It really makes me frown when I realize that this MMO has gone from an inspiring Cinderella story of redemption to a game in which the dev team has lost their way in regard to their own audience in the matter of a single delay and a single patch. The populace of XIV have shifted to such a pessimistic stance since 3.0 got stale, especially since 3.1. Who can blame them? I'm starting to feel it. To be fair they made some design mistakes, not just technical ones. It's starting to feel more and more like Square Enix five years ago to me. This technical crap on top of an already disappointed fanbase is not good. Not good at all. I don't want to say that the fanbase is abandoned the game, but XIV has been bleeding subs for months. 3.2 Needs to fix a lot of this shit or else it's going to continue. I don't think they know how to hold their fans right now. The casual content is okay, but making it the focus is a mistake. Conversely, there's not enough people digging into raid content to make it more than it is. So what now? More Lords of Verminion, an aside that can be experience entirely by a level 15 character? More Alex divides, which don't really lend to one another? Making an MMO appeal to wide groups is an unenviable task, but they're doing what they can. Me? I just want the fucking roulette queues to work. Link to comment
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now