Arch Linux User Repository

I have since gotten a functional build. I can package it properly, login with a Microsoft account, access Modrinth integration, and access the modpacks I have installed. CurseForge support is still lacking. Due to this, you will face a bunch of RSPC error messages, but the launcher will function. For now, the launcher defaults to CurseForge, but I have discussed with the developer for the launcher to remember the platform you last used. This would mean that you do not get these CurseForge-related error messages, unless you switch back to CurseForge on purpose. The only issue preventing me from pushing this new build is that I am trying to figure out a versioning scheme. I want to mirror the developer's versioning as best as possible, but I have yet to find a way to automatically generate these version numbers.

Great info @BlazingBlast

First thing that comes to mind is patching requests to support the existing public API, but honestly at that point it might be more trouble than it is worth.

Nonetheless I'm looking forward to seeing what you come up with in the future!

what makes GDLauncher-Carbon different from PrismLauncher?

GDLauncher has a special type of API key that allows it to access content that CurseForge developers marked as 'not for 3rd party services.' PrismLauncher does not have such a key, which is why it needs to download certain mods via a pop-up browser. Sharing of this key is forbidden by the license, and because of the openness of the AUR, we cannot distribute the package with this key. CurseForge integration is possible in the binary version, but unless you have your own key, we cannot make it work in the source version. Once I get this version working, I will look into how PrismLauncher does this, and maybe get it working as it does there.

@BlazingBlast That's interesting. I wonder what makes GDLauncher-Carbon different from PrismLauncher where CurseForge integration works

Does lack of Modrinth mean no support for installing mods/modpacks?

I am quite sure that I can get Modrinth working, but not CurseForge. This means that you cannot browse, upgrade and install mod(pack)s from CurseForge directly from the launcher. You can still use the CurseForge website, and import the .zip file you can download there into the launcher. You can, of course, still launch (modded) Minecraft instances, and create them. I am unsure if the launcher allows you to import mods into your instance from their .jar file, instead of only from CurseForge and Modrinth directly.

Good riddance @BlazingBlast!

Does lack of Modrinth mean no support for installing mods/modpacks?

I have had a conversation with the developer. I now have enough information to make a build without error telemetry, no CurseForge, and probably no Modrinth support. I will work on getting that building soon.

received code 404 Not Found from https://binaries.prisma.sh/all_commits/d6e67a83f971b175a593ccc12e15c4a757f93ffe/debian-openssl-3.4.x/query-engine.gz

This can be mitigated by spoofing your OpenSSL version. You can do so by adding the following file (with execution permissions) named openssl to your PATH while building.

# !/bin/bash
echo "OpenSSL 3.0.0 9 Apr 2024 (Library: OpenSSL 3.0.0 9 Apr 2024)"

The query engine simply does not exist for the OpenSSL version that Arch Linux uses.

Considering that gdlauncher-carbon in its current form requires an API key for local builds, I've opted to submit a request here in the hopes of seeing this changed in the future:

https://github.com/gorilla-devs/GDLauncher-Carbon/issues/388

@huantian You're right, and I completely agree with your naming idea for transparency (e.g. gdlauncher-legacy(-bin,-git) / gdlauncher-carbon-bin)

Since as it stands, you cannot build gdlauncher-carbon locally without API keys.

Please, pin information about this to save others from wasting time

1) Here's what the GDLauncher-Carbon/README.md says:

To be able to develop on GDLauncher Carbon locally, you will need to request an API key to api-keys@gdlauncher.com. Please include your github username and a short description of what you are planning to do with the API key.

2) And if you try to build the project you'll encounter this:

Downloading https://binaries.prisma.sh/all_commits/d6e67a83f971b175a593ccc12e15c4a757f93ffe/debian-openssl-3.4.x/query-engine.gz to /home/user/game/.cache/prisma/binaries/cli/4.8.0/d6e67a83f971b175a593ccc12e15c4a757f93ffe/prisma-query-engine-debian-openssl-3.4.x

thread 'main' panicked at /home/user/game/.cargo/git/checkouts/prisma-client-rust-fa967aa5ad0ec391/f71ad91/cli/src/binaries/mod.rs:145:9:

received code 404 Not Found from https://binaries.prisma.sh/all_commits/d6e67a83f971b175a593ccc12e15c4a757f93ffe/debian-openssl-3.4.x/query-engine.gz

"This object does not exist or is not publicly accessible at this URL. Check the URL of the object that you're looking for or contact the owner to enable Public access."

Edit: the last bit was unrelated to API key in README but the issue still remains, see below:

Please show your support and follow the discussion in:

https://github.com/gorilla-devs/GDLauncher-Carbon/issues/388