Results 27 comments of Abex

merged as b0eb6747c4e8886db5106d1bb97ed20b5bb53ffd

I've attempted a 3D login screen in the past and its not really viable for a multitude of reasons, mostly related to the mess that is region loading.

also 4) have the runner print the sha512 of the artifact immediately after it is built

imo this is a somewhat horrible idea since the client needs a restart to actually get the config

I don't think a warning makes it any less horrible

We can't really make the client poll, because 1) thats a lot of traffic and 2) it would cause the loading splash to open, take focus, and otherwise be obnoxious,...

"The button does not work" is the ux nightmare I am referring to. I don't see any way for the client to know about this change without either every client...

The client is the primary consumer of this config, so I don't get `the client isnt supposed to know about the change`. If we add a reload button, why not...

IMO the primary use of this would be providing a link (ie from runewatch's website or w/e) that lets you install their plugin easily, which would in many cases happen...