Fostik wrote:The thing is, 20 of 20 people here were using custom clients, with custom features improving PvP experience and UI, but not optimized and tested enough the way default client features are.
I'm not a fan of vanilla client, but it's resilience granted and taken under responsibility of devs. I'm most certainly sure that all the crashes were caused by some features of custom clients.
Not to blame custom clients and all, I think that it shouldn't be a mandatory to use them in the first place for PvP. Considering how really fucked up you are by showing up on fight using vanilla client, action must be taken to leverage that gap.
Honestly most of those crashes are JVM crashes and not client crashes (we fixed those, like after 1 fight where they happened). Every single custom client is crashing from time to time in big fights (i had no crashes outside of that) and the only "crashlog" you get is java telling you to get fucked. Can it be a common mistake done by custom client devs? Sure. But that did not happen in previous world, it used to happen back in w11 i think? And iirc it had to be fixed by loftar bcs of the nvidia crashes, so while it might damn well be custom client fault it might happen on vanilla client too, too bad no fighter is actually running vanilla during fights to test it, and the crashes are not even very consistent, some ppl get a ton of them, some ppl get like 1 or 2, some ppl get none.
But yeah for some reason big fights make clients go crazy and no crash KO is a rule held by a string because ppl will inevitably start accusing each other of faking the crashes when they crash in a bad spot, then again if the rule isn't upheld fights will become a funny Russian roulette (you crash you die kind of deal) and tbh fuck that shit, i'd rather just bonk hermits all day and never actually pvp if that's the case lol.