Package Details: feedthebeast-classic 1.5.1-3

Git Clone URL: https://aur.archlinux.org/feedthebeast-classic.git (read-only, click to copy)
Package Base: feedthebeast-classic
Description: Feed The Beast offers many different styles of Minecraft modpacks to the community, catering to all tastes.
Upstream URL: https://feed-the-beast.com/
Licenses: Apache
Submitter: Nayla
Maintainer: Nayla
Last Packager: Nayla
Votes: 46
Popularity: 0.000000
First Submitted: 2020-10-16 12:06 (UTC)
Last Updated: 2020-11-26 15:56 (UTC)

Dependencies (6)

Required by (0)

Sources (2)

Pinned Comments

alissonlauffer commented on 2020-04-09 03:53 (UTC) (edited on 2020-04-27 08:03 (UTC) by alissonlauffer)

Hello guys, I know you are waiting for the new FTB update, but for now packaging it is not possible, since the launcher cannot be installed in places that the user does not have write permission (E.g: /usr/share/feedthebeast or /opt/feedthebeast). Check this and this. For now use the classic launcher or install the new one using the official installer at https://feed-the-beast.com.

Also: When packaging the launcher is possible again, I will create another package for the classic/legacy version (for those who prefer to use it).

Latest Comments

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

shaybox commented on 2020-06-01 22:13 (UTC) (edited on 2020-06-01 22:14 (UTC) by shaybox)

I am aware you can't directly rename, I suggest making a new package feedthebeast-legacy, submitting a merge request, update local git origin, push all the existing commits, then re-making the feedthebeast package and commiting the new files, I shortened it by saying rename. This assures people that have the legacy launcher installed don't suddenly get the new launcher installed, it also keeps the legacy comments, bug reports, and commits with the legacy package, essentially just a rename, but in a roundabout way thanks to the limitation of not having an explicit rename request.

alissonlauffer commented on 2020-05-10 06:16 (UTC)

I would suggest making a request to rename this to feedthebeast-legacy and once that's gone through making a new package with this name

Packages can't be just renamed. I would have to create a new package named feedthebeast-legacy and then push the current code to it.

But for now, packaging the new launcher is not possible. We have to wait upstream until they implement the ability to install the app globally. Once they implement it, I will create the feedthebeast-legacy package and update this one to the latest version.

shaybox commented on 2020-05-04 13:51 (UTC) (edited on 2020-05-04 13:52 (UTC) by shaybox)

The new launcher is out https://www.feed-the-beast.com/
I would suggest making a request to rename this to feedthebeast-legacy and once that's gone through making a new package with this name

jamezrin commented on 2020-04-17 19:54 (UTC)

FTB legacy has been updated to 1.5.1

alissonlauffer commented on 2020-04-09 03:53 (UTC) (edited on 2020-04-27 08:03 (UTC) by alissonlauffer)

Hello guys, I know you are waiting for the new FTB update, but for now packaging it is not possible, since the launcher cannot be installed in places that the user does not have write permission (E.g: /usr/share/feedthebeast or /opt/feedthebeast). Check this and this. For now use the classic launcher or install the new one using the official installer at https://feed-the-beast.com.

Also: When packaging the launcher is possible again, I will create another package for the classic/legacy version (for those who prefer to use it).

disastro commented on 2020-01-17 00:05 (UTC)

Looking smooth now, appreciate the credit. Reading back it seems I might have sounded a bit rude but I just tend to be straight, sorry. Now the wait for feedthebeast... 2.0.0? begins :)

alissonlauffer commented on 2020-01-16 23:48 (UTC)

Ok, done.

disastro commented on 2020-01-16 23:15 (UTC) (edited on 2020-01-16 23:45 (UTC) by disastro)

Old maintainers usually stay as contributors especially since you didn't change the package at all. EDIT: I see you didn't start the trend of removing contributors in this package though.

url isn't https, java-runtime depend should probably be java-runtime=8 instead. desktop file has no reason to list the launcher as an AudioVideo application.

LD_LIBRARY_PATH isn't needed in the script as far as I know. And you should be forcing Java 8 with export PATH="/usr/lib/jvm/java-8-openjdk/jre/bin/:$PATH"

Farewell commented on 2019-11-15 11:02 (UTC) (edited on 2019-11-15 11:24 (UTC) by Farewell)

the url to download the launcher is down, new url is : https://dist.creeper.host/FTB2/launcher/FTB_Launcher.jar

Checksum of the launcher as of today : 47d6ce99fc052d12b587beaa11b94441336b8190525b30a9e45ee4622d2d6b50

<deleted-account> commented on 2019-07-29 20:20 (UTC)

The launcher fails to load the authlib on Java 12 and Minecraft performs like crap on anything other than Java 8. I'm not saying it should hard depend on JRE 8, but the launch script should be updated to add the Java 8 JRE to $PATH before launching the game. The minecraft package here on the AUR uses the same method. That way it will always use that version if it is installed even if Java 12 is set as the default for the system.

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