Closed scheibo closed 4 years ago
A new desktop client needs to be deployed ASAP but I've been putting it off... Signing is annoyingly hard and new deployments all require signing these days, if you don't want to teach your users how to turn off checking for signed executables.
A new desktop client needs to be deployed ASAP
Is the 'white out' a KI already that the new client would fix? And does the new desktop client have better support for debugging issues?
Is it reliably reproducible? If so, you can test yourself by grabbing the latest version of NW.js and following the desktop client build readme: https://github.com/Zarel/Pokemon-Showdown-Client/tree/master/desktop
The old desktop client is pretty easy to debug: Just turn on the toolbar in package.json
, Chrome's debugging tools are the gear icon on the toolbar. Newer versions of NW.js should work similarly, but make sure to grab the debug builds.
New desktop client was deployed a monthish ago.
Sadly, opening devtools on it is a lot harder, but can be done with /debug nw
.
I got a ticket from a Windows 10 user who experienced some issues with the desktop client (ie. standalone, not the browser). A summary:
My best theory is that the desktop client (perhaps erroneously) figured they were disconnected, and by the time they noticed the client not responding and restarted the 60s disconnect timeout had passed, which was ruled as potentially plausible by the user (my other theory was maybe their opponent didnt feel like waiting and just left the battle, but the user lost ELO so presumably that wasn't the case). I don't know enough to be able to say that was actually what happened (does the battle get removed from active battles in that scenario? I would have thought that unless the 15 minute inactivity period had passed and expired the battle it would still be there?)
Anyway, several issues/questions here: