Easier setup

[Saiv46]

• Executable should edit/update autoexec.cfg
• Automatic browser opening
• Steam authorization on first run
• Automatic MasterBase API key provisioning

[lili7h]

1. Not all TF2 installations make use of autoexec.cfg (for example, mastercomfig replaces it), and not all users want their configs in autoexec.cfg. Having the app automatically modify and append to config files is pleasant UX, but not always, and can opaquely lead to other issues. Its just easier if we dont do that
2. This is already a thing
3. I dont think this is a good idea, purely out of taking the decisions out of the hands of the user and passing steam auth through a client that doesn't need or use it.
4. With the implementation of TOS agreements and stuff, there needs to be manual steps in here that require user interaction

[megascatterbomb]

1 - We could certainly provide the option, however we'd have to be careful with managing existing configs (mastercomfig, etc). For the purposes of the beta, it's not a high priority task.

3 - Signing in with Steam does not give a user access to Steam API. it gives us a unique identifier that can be used to authenticate future web requests to our servers.

4 - We have a cleaner UX in the works for API key provisioning. Check MegaAntiCheat/MegaAntiCheat-UI#103

[MaxOhNoo]

Mastercomfig puts the autoexec in tf\cfg\overrides

[Bash-09]

Mastercomfig puts the autoexec in tf\cfg\overrides

I believe the point was more about how there is possibly a lot of special-casing that needs to be handled and it isn't always as simple as just "add it to the config".