Package Details: minecraft-launcher 2.1.5965-1

Git Clone URL: https://aur.archlinux.org/minecraft-launcher.git (read-only)
Package Base: minecraft-launcher
Description: Official Minecraft Launcher
Upstream URL: https://mojang.com/
Keywords: game minecraft
Licenses: All Rights Reserved
Conflicts: minecraft-launcher-beta
Provides: minecraft-launcher-beta
Submitter: shoghicp
Maintainer: petr
Last Packager: petr
Votes: 112
Popularity: 14.155556
First Submitted: 2017-01-18 14:17
Last Updated: 2019-07-23 12:40

Pinned Comments

petr commented on 2018-12-20 09:56

The java version is ... problematic. The current version of the base game will work with any Java version. So will some of the very old game versions that do not use launchwrapper.

Java 8 is required for all legacy versions, and all modded versions of the game (except for some experimental builds of Forge for 1.13). It makes sense to require it, because easily, 99% of the various ways to play the game DO require it. Roughly half of the players play modded regularly.

Fixing the old and modded versions is a non-trivial (almost intractable) task. Fixing Java would require forking it and maintaining the fork. Java runtimes of different versions are installable side-by-side. The launcher needing 'a java 8 runtime' should not prevent you from installing and using a different one.

If you have any suggestions about how to improve this situation, I'm all ears. However, using Java 9+ by default would introduce major issues.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

jpegxguy commented on 2018-07-06 17:24

Why is java-runtime=8 required? why not >=8 ?

petr commented on 2018-07-06 16:15

The fix should be in. As long as you don't have something extra in the network doing caching, it should work.

petr commented on 2018-07-03 18:47

If you are rebuilding in the same directory, delete the file, it should redownload and have the correct checksum.

I'll put in some sort of fix as soon as I get back to a real machine with my SSH keys.

Tank116 commented on 2018-07-03 15:29

Also reporting in: Minecraft.tar.gz fails sha256 checksum in 2.1.1218-1 update

petr commented on 2018-06-30 19:35

As for the reusing of filenames, I put that on the TODO pile :)

mattsturgeon commented on 2018-06-30 19:28

I haven't attempted to reproduce yet, however it could be a caching issue (either on your end or smorky's).

petr commented on 2018-06-30 19:26

Hmm... it works for me? On multiple machines?

You'll have to provide more details about what's going wrong, because I just don't see it.

mattsturgeon commented on 2018-06-30 17:12

smorky: That's because when mojang update the snapshot, the link doesn't change. That means that the checksum is different so will fail integrity checks.

Ideally, mojang would provide versioned or datestamped links for the snapshots, but AFAIK they don't. Them updating the release build would also work, but iirc the latest release build doesn't even work anymore.

smorky commented on 2018-06-30 16:07

Minecraft.tar.gz fails sha256 checksum in 2.1.1218-1 update.

Wascar commented on 2018-05-18 15:44

Missing dependency issue : Permanently resolved