Package Details: minecraft-launcher 1:1.0.1221-3

Git Clone URL: https://aur.archlinux.org/minecraft-launcher.git (read-only, click to copy)
Package Base: minecraft-launcher
Description: Official Minecraft Launcher
Upstream URL: https://mojang.com/
Keywords: game minecraft
Licenses: custom
Conflicts: minecraft-launcher-beta
Provides: minecraft-launcher-beta
Submitter: shoghicp
Maintainer: pschichtel
Last Packager: pschichtel
Votes: 1098
Popularity: 4.12
First Submitted: 2017-01-18 14:17 (UTC)
Last Updated: 2024-06-17 22:10 (UTC)

Pinned Comments

petr commented on 2021-10-08 09:04 (UTC)

The package version is the version of the launcher bootstrap - the part that actually downloads and updates the launcher.

That means the version number of the actual launcher (2.x.xxx) is different from the version here (9xx+) on a fundamental level, and should not be compared.

The package is outdated only when the bootstrap version you get here is different from the bootstrap version you would get from minecraft.net when using the raw tarball.

Latest Comments

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 52 Next › Last »

ywecur commented on 2019-08-12 00:06 (UTC)

I'm getting this error when trying to launch:

terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_M_construct null not valid Aborted (core dumped)

jpegxguy commented on 2019-08-11 18:48 (UTC)

@mattsturgeon if the problem is that users will choose the wrong version when asked (even on arch, sure), make the change in minecraft-launcher-beta only

jpegxguy commented on 2019-08-11 18:46 (UTC)

@mattsturgeon Okay so the reason is that we're worried users who want mods won't know to choose jre8 when pacman will ASKS them about the version they want to install when they downlaod this package? And Arch users, at that? I doubt it.

My point is that with the change to >= from = the package manager would ask you what version upwards of 8 you want. You choose 8. Done. Why do we force this version? LegacyLauncher is not needed for vanilla and is indeed "hacky code to launch old mc versions". Now, mods do use it. So choose jre8 upon install. Where's the negative?

cjmick commented on 2019-08-04 05:24 (UTC)

@rezystor, nope not working for me :( bummer

rezystor commented on 2019-08-03 19:08 (UTC)

If your game crashes, try installing java8-openjfx, for me it fixed problem with lwjgl.so

mattsturgeon commented on 2019-08-02 18:20 (UTC)

I don't understand why it can't be "greater than OR equal"

Legacy launcher requires java "less than or equal to 8" (and also greater than or equal to the minimum compatible version, iirc 5?).

Since version 1.12 Minecraft require 8 as a minimum.

So since 8 is a minimum for Minecraft and a maximum for legacy launcher, it is the only fully compatible version of java right now. Newer versions break legacy launcher, older versions don't support Minecraft.

Even when modlauncher (legacy launcher's replacement in forge 1.13) becomes more commonplace, they'll still be a big proportion of mods using legacy launcher, and mods for older mc versions will likely always use legacy launcher (and always require java=8)

DarkWav commented on 2019-06-26 15:33 (UTC)

Version 2.1.5410-1 is working alright, thanks a lot.

DarkWav commented on 2019-06-25 12:57 (UTC) (edited on 2019-06-25 13:17 (UTC) by DarkWav)

The version 2.1.5236-1 for me just crashes with a memory access error. I got no Idea why, but it just won't run at all for me. Fresh install on a VM, no luck, same error.

jpegxguy commented on 2019-06-17 04:14 (UTC)

So the only reason for not making it java-runtime>=8 is because users might not actually have jre 8 installed and wonder why mods dont work? I don't like to have an extra version of java just because LegacyLauncher is old and unsupported. I don't understand why it can't be "greater than OR equal". Currently, it is only "equal".

Besides, arch will prompt for a choice of the java version to install, when installing minecraft-launcher for the first time, while having no Java installed.