or put another way, can auto update be fixed so it's generally unobtrusive and reliable? and to be able to handle a server being offline?
example from today
MC on main client is unresponsive to MCWS commands
logon to the box to check what it's doing and it's running but not doing anything
kill it and start it again
immediately launches the auto update
complete this and it fails to connect to the server
go to the server and find that has restarted and MC is not running
start MC and that gives the "failed to update because no one clicked ok" message
update that and now the client can reconnect
this is not so uncommon (if you leave auto update on)
1) MC client should not freeze when the server is offline
2) MC client should be able to start without a server being online
3) autoupdate needs to be able to operate without intervention for routine updates
4) autoupdate needs to only actually trigger when told to do so as opposed to on *any* restart (e.g. windows decides its time to reboot, MC has decided its time for an update and will do it whenever it restarts, combine the two and you have a recipe for problems)
IME the sum total of such issues is "turn off auto update everywhere because it's a nuisance" (which seems a bad outcome to me)