Fix the bug that actually matters?

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.

Quote:

---

Originally Posted by Atelier-Bagur

Well at least it looks like they're hotfixing the bug this week after all.

Jump of the gun I guess with OP?

---

I mean they did stay silent on it instead of saying hey we aware of it and are working on a solution. And now that they do have one, we had to look in the JP side to even know about it.

Quote:

---

Originally Posted by Delis

I mean they did stay silent on it instead of saying hey we aware of it and are working on a solution. And now that they do have one, we had to look in the JP side to even know about it.

---

Dont worry Atelier is just a known shill for this company and is always ready to defend them at all cost, nothing new with him really, and yeah there is nothing on EU/NA as of yet, it's just on JP.

Quote:

---

Originally Posted by AmiableApkallu

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

---

There we go

Quote:

---

Originally Posted by 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.

---

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

Quote:

---

Originally Posted by AmiableApkallu

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.

Quote:

---

Originally Posted by TaleraRistain

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

Am I the only one who feels like this is another issue in the line of they test under perfect conditions and are never accounting for latency or heavy traffic?

Quote:

---

Originally Posted by AmiableApkallu

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.

Quote:

---

Originally Posted by Saraide

Am I the only one who feels like this is another issue in the line of they test under perfect conditions and are never accounting for latency or heavy traffic?

---

It works for JP so it must not be an issue! /s

I’m constantly reminded of Yoshi P having the audacity to say “we tested mch on high ping (110ms) and could not recreate the issues”

In that regard, the developers are wildly out of touch.

Quote:

---

Originally Posted by Saraide

Am I the only one who feels like this is another issue in the line of they test under perfect conditions and are never accounting for latency or heavy traffic?

---

I'll be curious what the findings they give us are on that. It can be difficult to replicate those conditions since you're testing in an environment that is often very no-touchie in regards to the live systems so you don't break something. So that means those connections aren't on, jobs aren't running, data isn't always passing between endpoint to endpoint, etc.