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
"Vampire_X;c-1570571" wrote:
Some easy tactics would also make other exploit holes too ;)
Its one of those if it was that essy it would be done... muliple popular games have similar systems.
Security and game part add layers to the ways client and server react.
True. But such security holes can be closed. If a security hole is discovered in https://blablabla/api/v14/do_whatever and it cannot be corrected, just make that particular endpoint throw an error (HTTP 500, for example), and make https://blablabla/api/v15/do_whatever perform correctly. That doesn't mean that every other message for v14 has to be automatically thrown to the garbage can. That way, you can send the "restart order" to clients, which can then store it in a variable, try to contact the server to send their pending information (or, if in a battle, wait until the battle is over), and _then_ restart.
In this particular case, the hotfix was for some TB bug. Absolutely nothing to do with raids. In fact, if someone is doing a raid, then they can't be doing TB battles.
But hey, we already know that nothing will be done regarding this issue. Like _so many other issues_, it is just easier to let it fall into oblivion, until the next one comes along.
