mojira.dev
MCL-16

Error downloading launcher files

When I start the launcher and downloaded the files, it tells me the following error:

Client> HELLO FROM WRAPPER
Client> Exception in thread "main" joptsimple.UnrecognizedOptionException: 'username' is not a recognized option
Client> at joptsimple.OptionException.unrecognizedOption(OptionException.java:89)
Client> at joptsimple.OptionParser.handleLongOptionToken(OptionParser.java:445)
Client> at joptsimple.OptionParserState$2.handleArgument(OptionParserState.java:54)
Client> at joptsimple.OptionParser.parse(OptionParser.java:385)
Client> at net.minecraft.launchwrapper.Launch.launch(Launch.java:31)
Client> at net.minecraft.launchwrapper.Launch.main(Launch.java:17)

Comments 5

This should only happen on 1.5.1, it shouldn't happen on any other version.

Which version did you try to play?

The version I try to play is snapshot 13w17a

13w17a is working fine here, as are the other snapshots. However, the 1.5.1 and 1.5.2 releases give me an error similar to this one (which is why I'm doing it as a comment here rather than another report) that keeps them from launching:

Getting syncinfo for selected version
Queueing library & version downloads
Download job 'Version & Libraries' started (8 threads, 1 files)
Finished downloading C:\Users\Roy\AppData\Roaming\.minecraft\versions\1.5.2\1.5.2.jar for job 'Version & Libraries': Used own copy as it matched etag
Job 'Version & Libraries' finished successfully
Launching game
Launching!
Running: "C:\Program Files (x86)\Java\jre7\bin\java" -Xmx1G -Djava.library.path=C:\Users\Roy\AppData\Roaming\.minecraft\versions\1.5.2\1.5.2-natives -cp C:\Users\Roy\AppData\Roaming\.minecraft\libraries\net\minecraft\launchwrapper\1.0\launchwrapper-1.0.jar;C:\Users\Roy\AppData\Roaming\.minecraft\libraries\net\sf\jopt-simple\jopt-simple\4.4\jopt-simple-4.4.jar;C:\Users\Roy\AppData\Roaming\.minecraft\libraries\org\ow2\asm\asm-all\4.1\asm-all-4.1.jar;C:\Users\Roy\AppData\Roaming\.minecraft\libraries\org\lwjgl\lwjgl\lwjgl\2.9.0\lwjgl-2.9.0.jar;C:\Users\Roy\AppData\Roaming\.minecraft\libraries\org\lwjgl\lwjgl\lwjgl_util\2.9.0\lwjgl_util-2.9.0.jar;C:\Users\Roy\AppData\Roaming\.minecraft\libraries\net\java\jinput\jinput\2.0.5\jinput-2.0.5.jar;C:\Users\Roy\AppData\Roaming\.minecraft\libraries\net\java\jutils\jutils\1.0.0\jutils-1.0.0.jar;C:\Users\Roy\AppData\Roaming\.minecraft\versions\1.5.2\1.5.2.jar net.minecraft.launchwrapper.Launch TripleFactorial -3787839933695824791 --workDir C:\Users\Roy\AppData\Roaming\.minecraft


YOU CAN CLOSE THIS LAUNCHER IF THE GAME STARTED OK ----


YOU CAN CLOSE THIS LAUNCHER IF THE GAME STARTED OK ----


YOU CAN CLOSE THIS LAUNCHER IF THE GAME STARTED OK ----


(We'll do this automatically later ;D) ----
Client> HELLO FROM WRAPPER
Client> Exception in thread "main" joptsimple.UnrecognizedOptionException: '3' is not a recognized option
Client> at joptsimple.OptionException.unrecognizedOption(OptionException.java:89)
Client> at joptsimple.OptionParser.validateOptionCharacters(OptionParser.java:538)
Client> at joptsimple.OptionParser.handleShortOptionCluster(OptionParser.java:463)
Client> at joptsimple.OptionParser.handleShortOptionToken(OptionParser.java:458)
Client> at joptsimple.OptionParserState$2.handleArgument(OptionParserState.java:56)
Client> at joptsimple.OptionParser.parse(OptionParser.java:385)
Client> at net.minecraft.launchwrapper.Launch.launch(Launch.java:31)
Client> at net.minecraft.launchwrapper.Launch.main(Launch.java:17)
Game ended with bad state (exit code 1)

As I said, I get this in 1.5.1 and 1.5.2, but all the snapshots start fine.

EDIT: They seem to be working now. Just had to close and reopen the launcher after their initial installations.

Excellent, marking this one as invalid now then 🙂

Let us know if it ever happens again.

Actually, after trying it again several times it seems to be rather erratic/chance-based. Can't state any real probability of it happening, but I've received unrecognized options of numbers 1-5 and 8 so far. The erraticness is at least consistent within the app, as in if it makes the error once it'll keep doing so – with the same number – until you close & reopen it and when it goes through it's fine for as long as it's active.

Still doesn't seem to apply to snapshots, though. They'll work with enough restarts or some luck, but it can get a little annoying at times.

Federico Pacheco

(Unassigned)

Unconfirmed

Retrieved