Package Details: minecraft 2.1.13509-1

Git Clone URL: (read-only, click to copy)
Package Base: minecraft
Description: Minecraft Launcher
Upstream URL:
Keywords: game minecraft
Licenses: custom
Conflicts: minecraft-launcher, minecraft-launcher-beta
Provides: minecraft-launcher, minecraft-launcher-beta
Submitter: BombStrike
Maintainer: yurikoles (petr)
Last Packager: yurikoles
Votes: 645
Popularity: 1.40
First Submitted: 2010-08-05 16:24
Last Updated: 2020-04-04 16:51

Dependencies (12)

Required by (13)

Sources (1)

Pinned Comments

yurikoles commented on 2020-04-04 16:52

PRs are welcome here:

Latest Comments

1 2 3 4 5 6 ... Next › Last »

yurikoles commented on 2020-04-04 16:52

PRs are welcome here:

Bramken commented on 2020-03-28 11:45

For anyone who want to use this launcher, it work great up to the 1.14.3. But if you try to play in 1.14.4 or higher than that it wont work.

Feakster commented on 2020-02-16 12:51

I just tried running this on Manjaro ARM using openjdk-13, but the following error was generated:

[12:50:42 INFO]: Getting syncinfo for selected version
[12:50:42 INFO]: Queueing library & version downloads
[12:50:42 FATAL]: Unhandled exception in thread Thread[pool-2-thread-2,5,main] duplicate key: null
    at$ ~[Minecraft.jar:?]
    at$ ~[Minecraft.jar:?]
    at$ ~[Minecraft.jar:?]
    at$ ~[Minecraft.jar:?]
    at ~[Minecraft.jar:?]
    at ~[Minecraft.jar:?]
    at ~[Minecraft.jar:?]
    at ~[Minecraft.jar:?]
    at net.minecraft.launcher.updater.RemoteVersionList.getCompleteVersion( ~[launcher.jar:1.6.89-j]
    at net.minecraft.launcher.updater.MinecraftVersionManager.getLatestCompleteVersion( ~[launcher.jar:1.6.89-j]
    at net.minecraft.launcher.updater.MinecraftVersionManager.getLatestCompleteVersion( ~[launcher.jar:1.6.89-j]
    at ~[launcher.jar:1.6.89-j]
    at$ ~[launcher.jar:1.6.89-j]
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker( ~[?:?]
    at java.base/java.util.concurrent.ThreadPoolExecutor$ ~[?:?]
    at java.base/ [?:?]

Ketchup901 commented on 2019-09-19 15:42

Did this finally stop working? It can't download new versions of Minecraft, gets stuck on "Preparing..."

ShayBox commented on 2019-04-04 14:51

To respond to the pinned comment, the new launcher is stable, they also have a beta version of it, this is the "legacy" version they no longer recommend, so this should be renamed minecraft-legacy, while the official stable versions should be minecraft and minecraft-beta, to clear it up for anyone wondering why this is still the minecraft package.

z3ntu commented on 2019-03-18 16:09

This package should depend on gtk2 - as without gtk2 installed, the launcher won't start. See for basically the same issue for another package.

Beebo commented on 2018-11-14 00:42

Really wish Mojang would update their darn launcher to support the new JRE.

As for this package, the default behavior for most AUR helpers is to install the newest JRE greater-or-equal than jre8. While these higher JRE packages allow the launcher to work, they do not let you get in game.

So in other words, the game itself still requires a JRE no higher than 8 to work properly past the launcher. Just something to keep in mind.

Bernie_McGee commented on 2018-08-06 18:26

@rafasc It looks like for 1.13 you can still use the old launcher. I've been using it, blissfully unaware that they were planning on dropping support. This allows more time for a decision, I guess.

@BombStrike What about contacting petr about making minecraft-launcher the "meta package"? Then users using that package would be set, with it pulling in this package as a dependency. And this package could continue as the "official" package, as I feel of the two, "minecraft" is a better choice of package name.

rafasc commented on 2018-07-26 21:38

@BombStrike I asked around on #archlinux-aur, and also based on what was said in this in this request, seems that this package should be updated to the new launcher and the minecraft-launcher should merged as a duplicate.

AFAIK, the old launcher will not be able to launch new versions of the game starting with 1.13, and since the new one is able to launch older versions, there's no reason for the old launcher to exist as a package. (Besides the fact it simply being available on that url which will probably go down in the future).

BombStrike commented on 2018-07-21 14:19

So now that the other launcher has become the official one, here is how I could do things:

  • Empty this thing and only have a dependency to minecraft-launcher: making it pretty much a meta-package of sort, would (probably?) be the safest option
  • Copy the existing package: not a big fan of duplicating stuff
  • Submit a request to have minecraft-launcher renamed to minecraft, and this one to minecraft-legacy: will break people who had minecraft-launcher installed

Let me know what you guys think in the comments, I'll also be doing some research on my side to make sure the updates goes smoothly for you guys.