Fix the bug that actually matters?

[TaleraRistain]

I dunno. Might have to give them a knock for not mentioning this anywhere but JP so far. I don't see anything on NA Lodestone yet. I can absolutely empathize with them if a bug may take some time to fix. Sometimes they can require some digging and testing to replicate.

[AmiableApkallu]

I dunno. Might have to give them a knock for not mentioning this anywhere but JP so far. I don't see anything on NA Lodestone yet. I can absolutely empathize with them if a bug may take some time to fix. Sometimes they can require some digging and testing to replicate.

English post went up a minute after yours. I'm guessing it took some paper pushing to get it translated.

https://forum.square-enix.com/ffxiv/...4-%28Jun.-6%29

Lodestone, for good measure: https://na.finalfantasyxiv.com/lodes...795431fe815efe

[TaleraRistain]

English post went up a minute after yours. I'm guessing it took some paper pushing to get it translated.

https://forum.square-enix.com/ffxiv/...4-%28Jun.-6%29

Lodestone, for good measure: https://na.finalfantasyxiv.com/lodes...795431fe815efe

Glad they acknowledged it. Still going to give them the knock for not making sure to release these simultaneously. They needed to hold the JP announcement until everything was ready. IIRC they did this with the NA DC issues recently, too. They told JP before the DCs that were actually affected.

I'm pretty forgiving on most of these since I work in software development but I'm a stickler for notifying users appropriately and I give them an F here. They need to do better on this.

[AmiableApkallu]

Glad they acknowledged it. Still going to give them the knock for not making sure to release these simultaneously. They needed to hold the JP announcement until everything was ready. IIRC they did this with the NA DC issues recently, too. They told JP before the DCs that were actually affected.

I'm pretty forgiving on most of these since I work in software development but I'm a stickler for notifying users appropriately and I give them an F here. They need to do better on this.

I work in software development, too, so I'll bite: What's the point in insisting on synchronized announcements here? No one's put at any sort of real advantage or disadvantage based on hearing the news a couple hours sooner or later (we're past the world-first clears). There's nothing for the players to do but wait for the fix to rollout. If it weren't for the modern Internet reducing everyone's patience to zero, we wouldn't even be talking about this.

Give them a knock for not acknowledging the bug earlier than they did. :P

[TaleraRistain]

I work in software development, too, so I'll bite: What's the point in insisting on synchronized announcements here? No one's put at any sort of real advantage or disadvantage based on hearing the news a couple hours sooner or later (we're past the world-first clears). There's nothing for the players to do but wait for the fix to rollout. If it weren't for the modern Internet reducing everyone's patience to zero, we wouldn't even be talking about this.

Give them a knock for not acknowledging the bug earlier than they did. :P

It gives the side that hears about it later the impression that they don't matter as much. I work for a laboratory with both NA and international locations and when our customer-facing application is down we make sure the announcement is created, translated by our team into our available languages, and then posted for all our customers to see at once. It's just a courtesy thing but courtesy is still important if you want to look good to your customers. If you're just on the development side then it may not be something you touch but I'm both development and customer interaction so it's definitely something on my radar.

I don't give them as much of a knock for not acknowledging the bug sooner because they were probably still in the investigation and replicate phase. I've certainly run into bugs that took longer than others to identify as a bug.

[SannaR]

Glad they acknowledged it. Still going to give them the knock for not making sure to release these simultaneously. They needed to hold the JP announcement until everything was ready. IIRC they did this with the NA DC issues recently, too. They told JP before the DCs that were actually affected.

I'm pretty forgiving on most of these since I work in software development but I'm a stickler for notifying users appropriately and I give them an F here. They need to do better on this.

They never release lodestone stuff simultaneously. Jp is almost always posted way in advance than the other languages. I'm not sure you'd call this bug game breaking as it's not an exploit, doesn't crash one's game or like the Sir Lakshmi trial waiting room bug doesn't allow people to move their character due to them sitting or sleeping on parts of the room that changed after you finished the trial. Does it suck that a fight mechanic is currently not applying itself properly? Sure, but the fight has been proven to be beatable despite the bug being active. Heck it's probably less severe than the winning number is Zero or the other 1st housing lottery bug.