doot doot

I fixed it in the latest build. Actually, I don't think this issue is visible in any of the tester builds, as I believe I fixed it in the first version containing the memory slider; I could be wrong, though, as this bug has plagued me for a long time. (It ended up being a bug within AngularJS itself)

Expected behavior for this build:

Really, this should be handled by better versioning -- ex: SemVer

Does this happen on any platform besides Debian 8 (mate)?

Interesting response to not having a connection.
Adding an offline-only mode and have the launcher intelligently fallback to it should resolve this issue.

@lancake:
"This ticket should apply to removing entries that are completely identical (path, version, and build all match), not just differing in the version that the launcher displays in the build-select dropdown."

'-Djava.net.preferIPv4Stack=true' is already present and passed to the jvm.

@SmilingDemon: This should be fixed with one of the latest commits; I'm unsure, however, as we have been unable to reproduce the bug on any system or vm. You can test it when the build server is working again ~

The -server option passed to the jvm is strangely not listed in your screenshot, but is present in the code.

On ubuntu(12,14)x64, [browse] does not update the install directory path.
Also: [continue]'s glow overlays [browse] and interferes with click events.

Note: this change currently only has one visible effect: the visibility of the steam account linking section of the launcher options.

What errors get thrown in ubuntu 14.04 x64? Is it trying to launch the game before downloading it? Are there any missing files/dependencies, ex ~/dep/java/jre1.7.0_80/bin/java?
I've so far been unable to reproduce the behavior.

I believe fixing T779 and T739 resolved this issue in v0.0.4; can anyone else verify?

If anyone experiences this when upgrading to the new launcher version, please comment with your OS flavor and architecture, launcher versions (from and to), and any relevant settings files. Thanks!

Assuming this is resolved ~
The missing win32 java dependency will be addressed with the next launcher release. If you are still having issues, please create another ticket!

I cannot duplicate this behavior in x64. Has the new launcher version resolved the issue?

Fixing T739 resolved this issue as well.
Details: the startup version check updated the selectedVersion value, thereby triggering an unwated checksum scan due to the behavior described in that ticket.

Apart from win32 missing bundled java, is this still an issue?

Removed the file check when changing the branch dropdown, and added a note above the [UPDATE] button that informs the user that clicking it will overwrite any installed mods.

Changing the selected version in the dropdown no longer triggers an immediate update, instead requiring you to manually click one of the update buttons (either in the build options window or the large orange [UPDATE] button in the lower corner of the launcher)

Increased default max-memory value for x64 from 1gb to 1.5gb
commit: 01e791ccd7e62034e7f4a9208eb4e2bd96320c78