-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Curseforge custom modpacks #3240
Labels
Comments
As stated in the docs, TYPE=CURSEFORGE is no longer actively supported. Switch to AUTO_CURSEFORGE. |
How to make custom modpack that are not published work? Here are the logs
|
Please review https://docker-minecraft-server.readthedocs.io/en/latest/types-and-platforms/mod-platforms/auto-curseforge/#unpublished-modpacks specifically the bolded text. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the problem
When attempting to set up a Minecraft server with a custom modpack, the process fails at multiple steps due to missing or corrupt files.
The modpack ZIP file does not include the necessary start script or forge jar files required to initialize the server.
This prevents the server from being started directly after unzipping.
Solution : Put it manually in the zip file
Missing forge server file
Same as above, it can't find the server file in libraries/**/forge-1.20.1-47.3.22-server.jar
Corrupt server file
Error: Invalid or corrupt jarfile forge-1.20.1-47.3.22-server.jar
Container definition
Container logs
The text was updated successfully, but these errors were encountered: