I have noticed that launcher doesn’t automatically update the client binary when it stays online, but only when it’s started. Based on short log reading, it doesn’t seem to even check if the client would need updating.
I’m not sure if this was designed change or not, but it was really handy that EVE was updated when I returned to home (as I have the launcher open all the time on my gaming VM).
Now, when I start doing EVE stuff I always start the client and get message “incompatible build” after patch days.
It should check every 15 minutes, however it can get stuck if something fails during the check. I’ve not been able to reproduce the issue so I’m not exactly sure what causes this to happen.
I can testify to this happening and will work on a reproduction scenario, how ever this is obviously hard to do since it revolves around the client being patched.
I leave the launcher, not the client, running almost 24/7 and seemingly after every (let’s be realistic it’s probably not every and i just dont notice when it works) patch I’m required to relaunch the launcher to kick-off the patching process.
What got my attention was part Refresh already in progress. I have no idea if only one server is updated at a time, but if that is the case, then stuck Sisi progress would mean that Tq won’t be updated.
It appears that there is only one started refresh cycle after first javascriptReady and after second and so on it’s always Refresh already in progress.