Launchbuddy 1.8.4 Concepts Collection:

Main feature: Alternative to argument (-email -password) login.

#1 Local.dat swapping:

Gw2 stores the last used login credentials (if remembered) in a file called Local.dat.
Swaping these files between each account eliminates the need to type in login credentials, however each client still needs one/two mouseclicks (Login,Startgame, only 1 if Autologin).

Pros:
- Very TOS friendly solution as no Memory has to be read/written
- Account data security is no longer needed for Launchbuddy

Cons:
- One account correpsons to one Local.dat file. Local.dat files usually grow in size after regular usage and therefore (30MB range). So allready 10 accs can take up 300MB or more
- Local.dat isn't only used for Login credentials, this file contains gamesettings like gamevolume, game resolution, pvp server bookmarks,... Therefore changing a setting must be done
on each account individualy!
- The past has shown that game updates have the potential to update the Local.dat file. Therefore after a game update each account would have to create the Locasl.dat file all over again.
- Requiers user input for launch


#2 Local.dat Manipulation:

For basic description please refer to #1.
This concept takles some of the problems of version #1. When launching this method actually won't swap the local.dat at all. It will refer to the account specific local.dat pick what makes up the login credentials and pastes
it in the currently used Local.dat.

Pros:
- Very TOS friendly solution as no Memory has to be read/written
- Account data security is no longer needed for Launchbuddy
- Basic Gamesettings are now synched over all accounts
- Less risk of crashes after a game update.

Cons:
- More complex to code than swapping local.dat
- No official ArenaNet statement about manipulation of game setting files
- Requiers user input for launch


#3 Memory Manipulation

Reading the gw2 client memory and writing memory to the specific user controls to achieve automated login.

Pros:
- Very fast launching experience
- All settings carry over after an game update

Cons:
- Grayzone in the TOS
- Pointer offsets can change when the launcher itself gets updated (good pattern scanning required)

#4 Input Simulation

The windows api supports basic control interaction with a few very simple commands. This could be used to either enter account credentials on each account startup in an automated way.
This also could be used in junction with conecept #1, to achieve an automated Local.dat file creation.

Pros:
- Current workflow for clients can stay the same
- Completly indepentend from game updates

Cons:
- Bound to crashes if the user manipulates the client while launching
- Grayzone in the TOS