-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Remove FTB modpack support #1040
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
f93d0fb to
4ff59de
Compare
4ff59de to
c7dc99d
Compare
We have been contacted by Feed the Beast to drop support for the FTB modpack browser from Prism Launcher. Signed-off-by: Sefa Eyeoglu <contact@scrumplex.net>
c7dc99d to
ff07714
Compare
DioEgizio
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rip FTB
This comment was marked as off-topic.
This comment was marked as off-topic.
txtsd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😕
This comment was marked as off-topic.
This comment was marked as off-topic.
|
And why you just don't ignore them? Their behaviour should not be supported by agreeing with their absurd requests. |
|
I do believe that they are the bigger entity here and have more power. Overwolf has Money, and wants the ad revenue. Even if it is for a worse launcher, any third party launcher has no choice but to do this. |
|
FTB bad😕 |
modrinth wipes |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
After feedback from some community members, I can add that there is more nuance to the story than I initially thought. On a legal basis, we probably don't have to follow the request of Slowpoke here, as there are no ToS, EULA or DRM we are breaking here. The API is publicly accessible and even has an official public documentation.[1] Apparently the API we were using was initially operated by CreeperHost as a general purpose modpack API, though it is unclear if that's still the case. I think if we didn't comply we would just end up being blocked by the API, and as we want to avoid drama where possible we thought we should just comply. In any case, here are reasons why dropping support for FTB is not as bad as it seems at first:
Some downsides of this change:
Of course, in an ideal world this didn't need to happen. |
Tbh they stopped publishing modpacks there since like 1.12 times. I also want to add that the ftb api is very buggy and highly unstable, it broke a lot of times, so removing even if we kept ftb they would break the API |
|
PrismLauncher/prismlauncher.org#262 blog post associated with this PR. |
|
rip ftb |
|
Didn't curseforge also ask you to remove their support? Why the double standards. |
Nope they haven’t if they wanted us to do that they would have revoked our api key |
Since they said that some launchers making profit off of them was the main reason for their disallowance, is it possible that you can try to get an exception? Since prism is no profit foss open source |
I can't say much but we are talking about this with them but can't say if it will come back soon cause it's a lot of legal stuff |
|
IMO: FTB has been in the toilet for a long while. Dropping support allows devs to focus on important features like the ones coming with the 7.0 release, which were a nice surprise for someone like me who doesn't read source code like the news. Keep up the amazing work! EDIT: After reading the talk chain I understand the reasoning from a monetary standpoint and have no objection to FTB trying to protect their IP. Whoever these 3rd/4th party 'devs' are stealing work to actively profit off of, I say this with the sincerest heart, F*** you. |
|
Super unfortunate but understandable that FTB needs to be seen protecting their IP if they want any ability to enforce their trademarks in the cases that really matter. That's how the trademark system works. Use it or lose it. Hopefully some alternative can be found to allow people to import FTB packs into Prism Launcher from, say, the FTB App once installed through there. Thanks for the blog post. It really helped with the transparency behind this decision as well as understanding where FTB is coming from on this issue. |
I think there was mention somewhere that later down the line it can be replaced by a simple pack importer. No different from importing a zip. it just can't tap into the Curseforge API. |
Using the curseforge api is fine it's just ftb didn't want launchers to list their packs inside the launchers |
PrismLauncher/PrismLauncher#1040 < PR that removed this feature Signed-off-by: Onako2 <79749977+Onako2@users.noreply.github.com>
|
so how much money did overwolf give to ftb? |
|
I suggest changing the line in the About-section of the webpage that says it is possible to |
Do they still actually do that? The last update to one of their modpacks on CF was in 2021, AFAICT, while many of their packs have received further updates on their own site. |
no, ftb modpacks on curseforge hasn't been updated for years |
|
FTB will probably be contacting you shortly regarding this stance as their policy has recently changed. |
Do you have any sources for that? Or just wait and hope for the best? |
We have been contacted by Feed the Beast to drop support for the FTB modpack browser from Prism Launcher.
Please keep discussions civil. This decision is not specifically targeted towards Prism Launcher.