Results -9 to 0 of 1325

Dev. Posts

Threaded View

  1. #10
    Player
    Nommers's Avatar
    Join Date
    Dec 2021
    Posts
    63
    Character
    Naamah Qhemnu
    World
    Midgardsormr
    Main Class
    Black Mage Lv 90
    Quote Originally Posted by Baekho View Post
    Last official thing I heard was Soken confirming on Twitter that the fix is already 'in place' and will probably release before 6.1, but is currently still being tested on different configurations... Hopefully that means it won't be too long now


    https://twitter.com/SOKENsquareenix/...31647407362049
    This is great news, but this tweet is five days old. NOT EVERYONE CHECKS TWITTER AND THE FORUMS, SQUARE ENIX. At this point it's been over a month and a half since the bug was introduced, a month since it was made worse and introduced for people who didn't get it in the first round, almost two weeks since a community manager said anything, and there's still not been a single acknowledgement on Lodestone. If it doesn't make it into the Oceania DC update next week (and I'm not getting my hopes up), it will likely have taken AT LEAST two months to fix it. And not a peep on Lodestone, while fancy Panasonic head(neck?)phones and that Immerse crap gets advertised at us instead.

    I'm just baffled. I expect better from these devs. The only reason I'm not a furious ball of incandescent rage is that I've been playing other games. If they can't refund my wasted sub time, the least they can do is apologize.

    EDIT: I just want to clarify - I'm not angry about how long it's taking to fix the problem. I appreciate the logistical nightmare of trying to test this for all possible hardware configurations (although it really should have been taken care of BEFORE the launch of a major expansion). I'm mad about the total absence of official communication. There's just no excuse for the silence. And no, forum posts and tweets do not count.
    (9)
    Last edited by Nommers; 01-20-2022 at 11:34 AM.

Tags for this Thread