Package Details: minecraft-launcher 2.1.1349-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
Submitter: shoghicp
Maintainer: petr
Last Packager: petr
Votes: 45
Popularity: 5.888029
First Submitted: 2017-01-18 14:17
Last Updated: 2018-07-26 20:25

Latest Comments

1 2 3 4 Next › Last »

mattsturgeon commented on 2018-07-27 09:14

Interesting, I always assumed MC was only java 8 compatible, but LegacyLauncher could well be the problem. Worth noting that forge plan on transitioning to a new modlauncher system with 1.13 (and anyone who wants to be forge-compatible will likely have to follow suit) so that may limit the issue to legacy versions and pre-1.13 mods.

jpegxguy commented on 2018-07-26 22:04

@erkexzcx I'm pretty sure both the game and the launcher work fine under jre (version 10), as is my setup. A problem arises in the LegacyLauncher when trying to start stuff like OptiFine though.

ask6155 commented on 2018-07-25 09:26

@jpegxguy It is recommended to run Minecraft with Java 8.

erkexzcx commented on 2018-07-15 22:29

Updated https://wiki.archlinux.org/index.php/Minecraft - Minecraft client (game) works fine even with java version 10, but the actual launcher starts only with java version 8.

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).