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.
Search Criteria
Package Details: minecraft-launcher 1:1.0.1221-3
Package Actions
| 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) |
Dependencies (6)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR)
- libgpg-error (libgpg-error-gitAUR)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compatAUR)
- flite (flite1AUR) (optional) – narrator support
- org.freedesktop.secrets (keepassxc-gitAUR, gnome-keyring-gitAUR, pass-secrets-gitAUR, keepassxc-allow-aur-extension-originAUR, keepassxc-allow-aur-extension-origin-binAUR, pass-secret-service-binAUR, bitw-gitAUR, dssdAUR, gnome-keyring, keepassxc, kwallet, kwallet5) (optional) – persistent login support
Sources (3)
mattsturgeon commented on 2018-07-27 09:14 (UTC)
jpegxguy commented on 2018-07-26 22:04 (UTC)
@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.
rafasc commented on 2018-07-26 21:38 (UTC) (edited on 2018-07-26 21:39 (UTC) by rafasc)
@BombStrike I asked around on #archlinux-aur, and also based on what was said in this in this request https://lists.archlinux.org/pipermail/aur-requests/2018-June/024898.html, 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).
ask6155 commented on 2018-07-25 09:26 (UTC)
@jpegxguy It is recommended to run Minecraft with Java 8.
BombStrike commented on 2018-07-21 14:19 (UTC)
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.
rafasc commented on 2018-07-19 21:26 (UTC)
@BombStrike Minecraft website updated the launcher url.
erkexzcx commented on 2018-07-15 22:44 (UTC)
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.
erkexzcx commented on 2018-07-15 22:29 (UTC)
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 (UTC)
Why is java-runtime=8 required? why not >=8 ?
petr commented on 2018-07-06 16:15 (UTC)
The fix should be in. As long as you don't have something extra in the network doing caching, it should work.
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.