Package Details: multimc5 0.6.16-3

Git Clone URL: https://aur.archlinux.org/multimc5.git (read-only, click to copy)
Package Base: multimc5
Description: Minecraft launcher with ability to manage multiple instances.
Upstream URL: https://multimc.org/
Keywords: launcher minecraft
Licenses: Apache
Conflicts: multimc
Provides: multimc
Submitter: vorpalblade
Maintainer: None
Last Packager: g3tchoo
Votes: 128
Popularity: 0.026896
First Submitted: 2015-06-06 11:37 (UTC)
Last Updated: 2023-02-06 06:15 (UTC)

Dependencies (9)

Required by (1)

Sources (8)

Pinned Comments

g3tchoo commented on 2023-02-06 04:26 (UTC) (edited on 2023-02-06 04:45 (UTC) by g3tchoo)

multimc is no longer using stable releases, which obsoletes this package (see this commit)

please consider switching to prismlauncher for continued support. you can find a migration guide here

edit: multimc-git was previously recommended, but has not been updated for more than a year and does not build off develop currently, so it has been removed. multimc-bin may also not be viable for the same reasons as this package, so the only alternative i am comfortable recommending is prismlauncher.

g3tchoo commented on 2021-12-18 18:53 (UTC) (edited on 2021-12-18 18:53 (UTC) by g3tchoo)

Leaving this as a permanent disclaimer:

It is illegal to redistribute any binaries created with this script because of the upstream project's licensing.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 20 Next › Last »

ImperatorStorm commented on 2021-09-23 23:34 (UTC) (edited on 2021-09-23 23:35 (UTC) by ImperatorStorm)

why use modern-java.patch, breaking compat with java versions <8 which are useful for alphas and betas, over setting JAVA_HOME via env variable to /usr/lib/jvm/java-8-openjdk(e.g. JAVA_HOME=/usr/lib/jvm/java-8-openjdk cmake ...) and adding java-8-openjdk as a makedepends?

vriska commented on 2021-09-23 14:06 (UTC)

I ran into this issue as a NixOS developer. It's important to note that MultiMC only requires a client ID, and not a client secret. The documentation explicitly states that the client ID can be public, and the Terms of Service explicitly states that it's confidential. I opened an issue about this, but haven't received a response: https://github.com/MicrosoftDocs/azure-docs/issues/80905

database64128 commented on 2021-09-22 15:37 (UTC)

The author is now threatening that any "unofficial" builds are "a trademark infringement" and "illegal". https://github.com/MultiMC/MultiMC5/issues/4087#issuecomment-925005124

sgorblex commented on 2021-09-22 12:15 (UTC)

Thank you @jotoho for your explanation. Of course, as @xiretza pointed out, it would be nice to be able to compile the package with ms login support, but I see why this isn't viable. Nor I can think of ways to use a unique secret and compiling, if not by providing at least part of a binary. I guess we'll add it to the list of things we blame Microsoft for.

xiretza commented on 2021-09-22 06:15 (UTC)

A -bin package can never supercede a package that builds from source just by virtue of existing. Especially for anyone that doesn't need Microsoft integration, building from source is obviously the better choice than using some binary off the internet that presumably even contains binary blobs to obfuscate secrets.

database64128 commented on 2021-09-21 17:40 (UTC)

There's a patch that adds the MSA client ID: https://github.com/AOSC-Dev/aosc-os-abbs/pull/3445