Originally Posted by
Nommers
I don't know why I feel compelled to defend them after a month of near-total radio silence, but I'm seeing this sentiment a lot and they did walk it back a bit.
I'm giving them the benefit of the doubt and assuming that they blamed old hardware because using an old CPU was the most reliable way they could trigger the bug in their test environment. Still not the best look to go with that excuse right after the bulk of the 2002 problem turned out to be on their end as well, but considering the majority of bug reports seem to have been sent in AFTER that post, they may genuinely not have known any better.
No matter how they go about it, though, intermittent posts by one community manager in one forum thread are not enough to make this right.
Like ClaraKitty said, I'd like to believe that they're staying quiet until they have a guaranteed fix ready to go - after all, the last time they said they fixed it they just made it worse. But at this point, outside of this thread and Soken's twitter, we've received no official assurances that this bug is being looked into at all, and I for one would feel a heck of a lot better if they said anything at all on Lodestone. I know the EN Community Team is away but even their twitter post said they had people still on board watching for problems. This seems like a problem to me. EDIT: I avoid social media like the plague myself, but is anyone making noise about this?