Force client restarts MUST be reworked
Four guildies doing HAAT tonight for over an hour, then a forced client restart... all lost. An absolute joke.
Forum Discussion
While the design could be improved, cross versioning everything would be not only dangerous from a security standpoint, but compatibility standpoint. It would also require a lot of manual tolerance input that would have to be defined by the devs as to what versions a fix works with.
Not unheard of, but a bit pointless to me when the better fix would be separating out when the reset flag is interpreted and having chat basically run it's own versioning. Basically the bug sounds like it is tied to the new chat system specifically and significant architecture changes as some are stating would be careless and shortsighted. Not only that, there are only a few scenarios of what would amount to asynchronous execution of transactions, mainly chat, so fixing those would likely be a lot easier and better then overengineering the architecture. This is also blind conjecture on my side based on the limited knowledge I have of their setup, so take it for what it is....
You can be irritated, the QA team has clearly missed some issues, but I wouldn't go so far as to try and tell them what design changes they should make to their architecture with only minimal knowledge of their codebase and operations (I write software for a living too and disagree with your ideas).
Not unheard of, but a bit pointless to me when the better fix would be separating out when the reset flag is interpreted and having chat basically run it's own versioning. Basically the bug sounds like it is tied to the new chat system specifically and significant architecture changes as some are stating would be careless and shortsighted. Not only that, there are only a few scenarios of what would amount to asynchronous execution of transactions, mainly chat, so fixing those would likely be a lot easier and better then overengineering the architecture. This is also blind conjecture on my side based on the limited knowledge I have of their setup, so take it for what it is....
You can be irritated, the QA team has clearly missed some issues, but I wouldn't go so far as to try and tell them what design changes they should make to their architecture with only minimal knowledge of their codebase and operations (I write software for a living too and disagree with your ideas).
