EVE Information Portal

World of Tank launcher - 36Mb memory footprint, disappears completely afterwards.
Fast, no nonsense.

CCP Eve launcher - 124MB memory footprint + 7MB bootstrap, becomes an undead at 107MB after you manually kill it.
It is also slow and feels laggy.

Need I say more?
The fact that you need to run a bootstrap program to get the launcher working is what we call an over-engineered solution that will be prone to breaking.
In other words, your launcher has will have so many process weak spots that you can pretty much throw robustness out of the window.

This solution may be fine for some cases. The main advantage of using multiple installs/junctions etc. is to maintain independent settings on a per-client basis, not per-account.

For example, I have a main install and a junction of that install. The main install is setup to run with high graphics settings, the junction at minimal. This allows me to quickly and easily choose the level of graphical fidelity I wish to use for that client according to my needs at that particular time, which usually depends on the number of accounts and duration of their use.

Please detail how I would be able to perform such a choice of multiple sets of client settings for each account under the new/proposed single sign-on with cloud settings.

In addition, how would cloud settings affect the use of clients on multiple computers? Exchange the junction client in my example above with a client on a laptop which barely runs Eve even at minimal settings.

I'm sure this would be possible to do.
Saying anything else would at this point merely be speculation.

You can do exactly the same thing now, except instead of having the junction point to the launcher, just have it point directly to exefile.exe. If there's an update the client will say incompatible protocol, so you'll have to run the launcher to update, but after that you can use the exefile.

no need for ssoToken ?

Why the hell would you patch the launcher in such a way that it wiped out all the account settings that I had? I really don't want to go through all my accounts resetting everything back the way I want it.

All for a stupid change to the launcher? Who do you have working in QA? Monkeys?

Major regression. When we say we want to switch characters without having to log in again, we were generally envisioning the "Log Off" button returning us to the character select screen, not this SSO BS which makes it take EVEN LONGER to switch characters on the same account, much less F-ing over any sort of multi-boxing setup.

Your best move here is to rewind the launcher to what you had.

•Any given program, when running, is obsolete.
•Any given program costs more and takes longer each time it is run.
•If a program is useful, it will have to be changed.
•If a program is useless, it will have to be documented.
•Any given program will expand to fill all the available memory.
•The value of a program is inversely proportional to the weight of its output.
•Program complexity grows until it exceeds the capability of the programmer who must maintain it.
•Every non trivial program has at least one bug
Corollary 1 - A sufficient condition for program triviality is that it have no bugs.
Corollary 2 - At least one bug will be observed after the author leaves the organization.
•Bugs will appear in one part of a working program when another 'unrelated' part is modified.
•The subtlest bugs cause the greatest damage and problems.
Corollary - A subtle bug will modify storage thereby masquerading as some other problem.
•Lulled into Security Law
A 'debugged' program that crashes will wipe out source files on storage devices when there is the least available backup.
•A hardware failure will cause system software to crash, and the customer engineer will blame the programmer.
•A system software crash will cause hardware to act strangely and the programmers will blame the customer engineer.
•Undetectable errors are infinite in variety, in contrast to detectable errors, which by definition are limited.
•Adding manpower to a late software project makes it later.
•Make it possible for programmers to write programs in English, and you will find that programmers can not write in English.
•The documented interfaces between standard software modules will have undocumented quirks.
•The probability of a hardware failure disappearing is inversely proportional to the distance between the computer and the customer engineer.
•A working program is one that has only unobserved bugs.
•No matter how many resources you have, it is never enough.
•Any cool program always requires more memory than you have.
•When you finally buy enough memory, you will not have enough disk space.
•Disks are always full. It is futile to try to get more disk space. Data expands to fill any void.
•If a program actually fits in memory and has enough disk space, it is guaranteed to crash.
•If such a program has not crashed yet, it is waiting for a critical moment before it crashes.
•No matter how good of a deal you get on computer components, the price will always drop immediately after the purchase.
•All components become obsolete.
•The speed with which components become obsolete is directly proportional to the price of the component.
•Software bugs are impossible to detect by anybody except the end user.
•The maintenance engineer will never have seen a model quite like yours before.
•It is axiomatic that any spares required will have just been discontinued and will be no longer in stock.
•Any VDU, from the cheapest to the most expensive, will protect a twenty cent fuse by blowing first.
•Any manufacturer making his warranties dependent upon the device being earthed will only supply power cabling with two wires.
•If a circuit requires n components, then there will be only n - 1 components in locally-held stocks.
•A failure in a device will never appear until it has passed final inspection.
•Adding manpower to a late software project makes it later.
•A program generator creates programs that are more buggy than the program generator.
•All Constants are Variables.
•Profanity is one language all computer users know.
Sent by Jeff Webb
•The number of bugs always exceeds the number of lines found in a program.
Sent by Yaron Budowski
•The most ominous words for those using computers: Â "Daddy, what does 'Now formatting Drive C mean'?"
Sent by Yael Dragwyla
•When putting something into memory, always remember where you put it.
Sent by Paul Pigott
•Every non-trivial program contains at least one bug.
•Every non-trivial program can be simplified by at least one line of code.
The conclusion of the last two laws: Every non trivial program can be simplified to one line of code, and it will contain a bug.
Sent by Brandon Aiken
•An expert is someone brought in at the last minute to share the blame.
Sent by Bassey Essien.
•Debugging is at least twice as hard as writing the program in the first place.
So if your code is as clever as you can possibly make it, then by definition you're not smart enough to debug it.
Sent by Brian Kernighan\
for any given software, the moment you manage to master it, a new version appears.
Sent by Bahaman.
The new version always manages to change the one feature you need most.
•Patches - don't.

Focus fire on that super star destroyer!
Oh wait it's just a thread.

I'm honestly surprised that you launched the new launcher when all the launcher threads for the test server still had so many bugs. I expected this to launch after Odyssey because of all the problems TBH. And I kinda wish you did.