-
Notifications
You must be signed in to change notification settings - Fork 22
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
[Feature Request] CurseForge Server Pack #125
Comments
#92 was a duplicate of #64, which is different - it's about specifying the working environment of a specific mod (mostly). Modpacks differ in that sense, as they are intended for both client- and server-side environments. However, you can also provide a "simplified" version of your modpack for the server, stripped down from client-side-only mods (which is not strictly necessary, since client-side mods should simply remain inactive on a dedicated server, but it may save some storage and traffic in the case of large modpacks). It turns out the CurseForge Upload API has yet another, sigh, undocumented parameter - |
I'm afraid that i haven't been able to find any other projects that supports server packs than the one i already linked. Their solution basically just require you to specify paths for the main file and the server pack separately. Not sure how you would be able to automatically detect whether a file is a server pack or not, as they don't usually include any metadata files. ¯_(ツ)_/¯ |
By "projects" I meant modpacks published on CurseForge that make use of server packs :) |
Oh duh, of course! xD |
Thanks! Welp, you weren't kidding when you said that they don't contain any standardized metadata. I guess we can automatically mark a modpack that's being uploaded as a secondary file as a server pack then? Is there any reason to publish a modpack as an additional file beyond that? |
Maybe to provide optional configs? Other than that, not really. Though the only pack i know to do this is RLCraft, so it is quite a niche use case. |
Description
Sorry in advance if this is a duplicate of #92!
I would love to use this project to automate the publishing of one of my modpacks, but from what i can see, it isn't possible at the moment to mark additional files as a Server Pack. Is this perhaps something that could be looked into?
Alternative Solutions
I tried this upload-curseforge-modpack-action, which actually did the trick for me. But it has other pitfalls and is not nearly as versatile as mc-publish.
Risks
I don't see why this would have any risk. From my understanding it should a simple toggle in the API that is available when uploading additional files to modpacks.
Other Information
No response
The text was updated successfully, but these errors were encountered: