Description:
Allow for another instance of a client to launch if one is already open and a patch comes through.
Why is this a good idea?
Due to the recent volume of patches, and the disconnect issue on clients after MuhGuard was added (clients will randomly disconnect when swapping chars, sitting on char screen, or sometimes just in game) while other clients remain intact. However you cannot reopen that client if a new patch has come in. The patcher locks your ability to open a new client until you’ve patched. Except when you have 4 or 5 clients open and a single one disconnects, now you have to close ALL of them just to reopen the one that disconnected.
What risks or downsides does it have?
It’s entirely possible to just leave a disconnected client open for long periods of time and just never patch.. So maybe limit how many versions of the patch can be ignored or a flag that says “No, I ABSOLUTELY CAN’T run without this patch.”
Additional Info:
I get the need to keep things locked down during patches to avoid gameplay disruptions, but given the time spent actually opening clients, this is very frustrating. Especially when you cannot have multiple config profiles for each client (sound, effects, etc.). You have to open them all under one config, then modify the ones you want to modify. If one disconnects.. you have to do it all over.
This has not been how this has worked in the past. You’ve always been able to open another instance of the client using the previous version, pre-patch. This still had the re-configure the re-opened client issue, but it’s much less of a pain to do one than having to redo all of them. This new restriction is as recent as of the last version or so of the patcher/client.