What problem is this feature trying to solve?
I'm currently trying to use this as part of a msbuild script for modding a game, and am using -qr for authentication due to how difficult it is to get user input for msbuild.
I would like to not have to login each time I build. It appears that once you have logged in with -qr you can use that same login token again, but you must specify a different command. This doesn't really work for me, as theres no way to tell if the authentication that depot downloader has is valid or not, which would tell me if I need to run it with -qr or with -username.
Trying to run it with both currently results in -qr can not be used with -username.
How would you like it to be solved?
The easiest solution I see here is allowing specifying both -username and -qr, which will try log in with the specified username and cached authentication first and only if that fails will it show a qr code to scan and sign in with.
Have you considered any alternative solutions
Another solution is to have -qr -remember-password save username as well and use that to log in (and only if that fails send a qr code). This would be nice as it means I wouldn't need to store the username myself.
Additional Information
I am using -remember-password in all commands said above, just have not specified it in most to shorten them.
What problem is this feature trying to solve?
I'm currently trying to use this as part of a msbuild script for modding a game, and am using
-qrfor authentication due to how difficult it is to get user input for msbuild.I would like to not have to login each time I build. It appears that once you have logged in with
-qryou can use that same login token again, but you must specify a different command. This doesn't really work for me, as theres no way to tell if the authentication that depot downloader has is valid or not, which would tell me if I need to run it with-qror with-username.Trying to run it with both currently results in
-qr can not be used with -username.How would you like it to be solved?
The easiest solution I see here is allowing specifying both
-usernameand-qr, which will try log in with the specified username and cached authentication first and only if that fails will it show a qr code to scan and sign in with.Have you considered any alternative solutions
Another solution is to have
-qr -remember-passwordsave username as well and use that to log in (and only if that fails send a qr code). This would be nice as it means I wouldn't need to store the username myself.Additional Information
I am using
-remember-passwordin all commands said above, just have not specified it in most to shorten them.