Making yet another post about this because of lazy devs

Quote:

---

Originally Posted by KageTokage

I'd like to hope they'll address most/all of the PvP bugs as well as some glaring balance issues (WHM's LB should not charge so quickly, nor should its CC be unremovable) in the coming patch for ultimate's release.

If not, then I don't have much faith that PvP is going to be a good experience in the long term.

---

I would rather they base LB regeneration on the amount of times you land any attacks & damage you received. Because as of now I can literally braindead a frontline battle by just hanging on the back of the ranks only running forward to drop a misery, throw out complementary morph to get free kills/assist, throw out Cure IIs on those who needed it, and dash forward for a surprise LB+Misery for easy kills.

Speaking of bugs though, WHMs also have bug in their own kits, namingly their Cure II. :rolleyes:

Quote:

---

Originally Posted by KizuyaKatogami

Well clearly being nice and patient doesnt help either if we ask the healer mains and hrothgar players lmao.Those of which have been waiting for 6 and 3 years respectfully for their changes. And look what they get.

---

Being civil doesn't instantly translate to being nice and patient. It's very easy to report a bug and voice your concern, disappointment, or disapproval without coming off as rude.

I like what they did for 6.1, this is the first time in years I was excited and it didn't disappoint too much. Let's hope the developers learn their lessons from the past and we can benefit from that.

I also hope Blizzard gets their shit together so WoW becomes a viable competitor again.

Can someone tell me how to replicate the bug the OP mentioned? I just did frontlines almost a dozen times as BRD and didn't see anything out of place.

Edit: Also the crystal moving is not a bug, that's just what happens when you leave the crystal unattended for too long on a lane.

I don't think "lazy" means what you think it does...

I would call the XIV devs "painfully out of touch" more then anything else.

They only seem to readily zero in on specific issues while others can go unaddressed for months/years unless someone brings it up to them directly...and sometimes even if they do given that they still don't seem to grasp some of the weird ping/delay related issues in combat people have been complaining about from the beginning.

I don't think that's necessarily their fault, though, as it's on their teams to be communicating issues to them properly but that's obviously not happening with some of them.

Quote:

---

Originally Posted by Packetdancer

The root cause isn't a bug, per se, but the fact that the process was not fault-tolerant is, at least in my opinion. It's an understandable one to make, given that data replication is often handled by some underlying database system and not by the game's own code directly. Still, the code surrounding it should probably have required an acknowledgment of data transferred successfully, and add things to a retry queue if it failed to get said acknowledgment, and I do think the lack there qualifies as a bug.

---

Bestest part about working with databases or servers as a systems engineer, attempting to bring things up to administration. Nothing brings happiness quite like identifying potential handshaking issue with simple fix only to be informed about deadlines. You then check your notes and ohhhh right, I brought this to your attention three weeks ago and was told it would be addressed. Now I get to spend time fixing it on live deployment.. fan fricken tastic also with upper management breathing down my spine.

Became so feist inducing I spent inordinate amount of effort just self hosting everything. Fricken costly too.. fiber, hardware, heat dissipation not cheap. I may give dev team much of the feist at the times but I truly feel for whoever has been tasked with resolving this because I have been there and it stinks.

Quote:

---

Originally Posted by MiaShino

I may give dev team much of the feist at the times but I truly feel for whoever has been tasked with resolving this because I have been there and it stinks.

---

Every time I have changed jobs in my life, it's been so as to try something new; there have only been a few times it was just as much to get away from the previous job as to try a new one. But my first job out of high school was as a database administrator, and that one I definitely was leaving in part to not be doing it anymore; I honestly don't think you could pay me enough to do that again.

So, you have my abject sympathy... and I definitely can also imagine the myriad possible database-related scenarios that could give rise to an issue like the placards not receiving their data.