All guidelines are now here.
Public mod pack submissions should be PM'd to Watchful11
The message should briefly explain that you are submitting a public mod pack and a link to a download of a zip file containing the following. Make sure it is a zip file rather than a rar.
EDIT: please specify the forge version you want for 1.6 packs in both your initial submission as well as updates. This is temporary.
Permissions:
All mod packs are required to have complete permissions for each and every mod included. This includes api's such as CoFH core and immibis core. Permissions that have been given to the official FTB mod packs DO NOT COUNT towards a public modpack. Permissions found in the Central Mod Permissions page do count. There is nothing private about these modpacks, as such, the private modpack permissions spreadsheet and all permissions given that refer to private modpacks, do not apply.
To keep submissions consistent, this is the required format for the mods and permissions section. An example text file with a number of mods is included in the example zip available at the bottom of this post. Each mod should be listed separately like so,
Mod Name - Developer (permission)
Permission can be demonstrated 2 ways.
Permission note. If a mod is a submod of another mod by the same author, you do not need to credit them separately. For examples, the separate parts of WRCBE and the bibliocraft wood addons. Their permission is implicit in the parent mod. To be clear, this does not apply to submods by different authors.
Once your modpack has been approved, you may post a topic in the 3rd party modpack section advertising the pack.
To update your mod pack:
Respond to the PM conversation with the following.
After your update is live, we will respond to the pm saying so.
If you find a problem with the pack once it is on the launcher, you can submit a hotfix and we will try to get it up, but it is not guaranteed. Test your pack thoroughly before submitting. Old versions of the pack are available from the dropdown menu.
There are occasionally problems on our end. If I have not replied to the conversation saying your pack is up, we am working on fixing it. Wait at least 24 hours before asking for help. Watch this thread for status updates.
You can also request an update not be set to recommended. It will be accessable from the dropdown version list, but will not prompt users to update. This can be used to test packs before forcing users to update. Note, you can still only push once a week and should test the modpack locally with MultiMC before submitting.
A sample mod pack download can be found in the private server pack guidelines. Since the guidelines differ, some sections of the info file do not apply.
PUBLIC MODPACK GUIDELINES
THE FOLLOWING GUIDELINES SHOULD BE USED WHEN SUBMITTING PUBLIC MODPACKS
Read the Outline and intentions of 3rd party mod packs to make sure you are submitting the correct kind of pack.THE FOLLOWING GUIDELINES SHOULD BE USED WHEN SUBMITTING PUBLIC MODPACKS
Public mod pack submissions should be PM'd to Watchful11
The message should briefly explain that you are submitting a public mod pack and a link to a download of a zip file containing the following. Make sure it is a zip file rather than a rar.
- A clean MultiMC instance. This should be ONLY the "Instmods" folder and the "Minecraft" folder, which contains "Mods", "Coremods", "Config" and "libs, plus the appropriate mods, configs and libraries in said folders, unless other files are required to make the mod pack work. (Please include a short comment explaining any extra required files in the info text file) YOU SHOULD NOT INCLUDE ANY COPY OF THE MINECRAFT JAR.
- png splash image (size = 420x200 pixels)
png icon image (size = 42x42 pixels) - Text file containing the following information, thourough explanations of each item are included in the example download:
Mod pack name
Included mods and permissions(see permissions section below)
(optional)Pack Code, numbers and letters only
(optional)Permissions Page
(optional)Mod Pack Description
(optional)Minecraft Version (1.6 packs, see the top of the outlines post)
(optional)Pack Version
(optional)Pack Author
(optional)Semicolon space separated mod list
EDIT: please specify the forge version you want for 1.6 packs in both your initial submission as well as updates. This is temporary.
Permissions:
All mod packs are required to have complete permissions for each and every mod included. This includes api's such as CoFH core and immibis core. Permissions that have been given to the official FTB mod packs DO NOT COUNT towards a public modpack. Permissions found in the Central Mod Permissions page do count. There is nothing private about these modpacks, as such, the private modpack permissions spreadsheet and all permissions given that refer to private modpacks, do not apply.
To keep submissions consistent, this is the required format for the mods and permissions section. An example text file with a number of mods is included in the example zip available at the bottom of this post. Each mod should be listed separately like so,
Mod Name - Developer (permission)
Permission can be demonstrated 2 ways.
- You can have a direct link to a screenshot of the permission policy, screenshot of a private conversation or a specific forum post where permission is granted. This includes the FTB Central Mod Permissions page, you should link the appropriate post. You cannot link the Minecraft Forum topic, you must take a screenshot of the policy, upload it somewhere and link it.
- If your pack has a public page listing all mods and outlining permission for them, you can just list the mod names and authors in the text file and link the page in the Permissions Page section. Simply linking each mods page is not sufficient, you must copy the permissions policy to your page. I advise doing permissions in the text file instead of trying to build a page.
Permission note. If a mod is a submod of another mod by the same author, you do not need to credit them separately. For examples, the separate parts of WRCBE and the bibliocraft wood addons. Their permission is implicit in the parent mod. To be clear, this does not apply to submods by different authors.
Once your modpack has been approved, you may post a topic in the 3rd party modpack section advertising the pack.
To update your mod pack:
Respond to the PM conversation with the following.
- A link to the full pack download. Not just the changes, the full pack, just like when you submitted it.
- A note of any added mods. You don't have to specify the new permissions in the message, but you should note the names of the new mods.
- A note if you changed either of the pictures.
- A note if anything in the info file has changed other than the mods.
After your update is live, we will respond to the pm saying so.
If you find a problem with the pack once it is on the launcher, you can submit a hotfix and we will try to get it up, but it is not guaranteed. Test your pack thoroughly before submitting. Old versions of the pack are available from the dropdown menu.
There are occasionally problems on our end. If I have not replied to the conversation saying your pack is up, we am working on fixing it. Wait at least 24 hours before asking for help. Watch this thread for status updates.
You can also request an update not be set to recommended. It will be accessable from the dropdown version list, but will not prompt users to update. This can be used to test packs before forcing users to update. Note, you can still only push once a week and should test the modpack locally with MultiMC before submitting.
A sample mod pack download can be found in the private server pack guidelines. Since the guidelines differ, some sections of the info file do not apply.
Last edited:
