MCL-122Unable to use auto login
After updating my launcher-exe I am no longer able to use auto login.
With a clean .minecraft folder the command line
minecraft.exe <username> <password>
will leave both text fields empty. With
minecraft.exe -u=<username> -p=<password>
Both fields are filled with the correct values but no auto login follows. If I than click on the "login" button I got logged in and I am able to play the game.
I tryed this with both .exe and .jar from minecraft.net
File hashes:
minecraft.exe md5:b63ccb43f2779cbea5d8d3ce2e3d90fb size:263186
minecraft.jar md5:bb99785000fdb3ebadd61a4a347fa042 size:81938
An old minecraft.exe (hd5:0f1931e26c21219db1c90e90037f11f6 size:270142 downloaded ~2011-09-14) works fine.
Environment
Win7 pro, Java 1.7.0_09, x64
Attachments1
Created Issue:
Unable to use auto login
After updating my launcher-exe I am no longer able to use auto login.
With a clean .minecraft folder the command line
minecraft.exe <username> <password>
will leave both text fields empty. With
minecraft.exe -u=<username> -p=<password>
Both fields are filled with the correct values but no auto login follows. If I than click on the "login" button I got logged in and I am able to play the game.
I tryed this with both .exe and .jar from minecraft.net
File hashes:
minecraft.exe md5:b63ccb43f2779cbea5d8d3ce2e3d90fb size:263186
minecraft.jar md5:bb99785000fdb3ebadd61a4a347fa042 size:81938An old minecraft.exe (hd5:0f1931e26c21219db1c90e90037f11f6 size:270142 downloaded ~2011-09-14) works fine.
Environment
Win7 pro, Java 1.7.0_09, x64
- Unresolved
- Open
- Minecraft - Public
- Unconfirmed
Normal
- 1.4.4
MC-3110
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
Perhaps with a new update to the launcher Mojang has disabled auto login? Maybe the feature was too obscure and was removed. A lot of developers do this to save space in their codes, etc.
Shows that it won't autologin.
@Nerdyboy6057 That would it be! But I cannot change the code so easy, because i want to leave the hashes which protect the files.
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
This is still an issue with the launcher available on minecraft.net at time of this post.
The only launcher I have ever managed to 'auto-login' with was the one that accepted a username and password without prefixes. I realise it is most likely not related to them, but once the prefixes were added no launcher since has actually logged in automatically.
I have tried the multiple ways available by command-line and received many different results, none of them actually logged me into the game.
I can understand streamlining code, but I do not feel this is relevant here.
Many games that require login details will give the option of 'auto-login' and 'auto-play'. Therefore I feel that the auto login option should function when both username and password are passed to the launcher. Without it there is a pointlessly added user action: Click the 'Login' button.
We'll not change the old launcher, but this is planned for the future of the new launcher after we add authentication tokens that will handle this sortof validations.
This applies to the old launcher which is no longer being updated. According to Grum (see above) it is a planned feature for the new launcher.