Take me to...

File Release Types and Additional Fields

Release: Syncs to the CurseForge App by Default. These are the files that will auto download when a user clicks the default download button on a project. You must have at least one of these files for the project to be available in the website and client.

Beta: Will sync to the CurseForge App provided the user chooses to receive Beta files. These files will also not appear in the sidebar for all games (except Minecraft).

Alpha: Will not sync to the CurseForge App unless the user chooses to receive alpha files. These files will also not appear in the sidebar for all games (except Minecraft).
New projects on CurseForge: A Release File or Beta must be uploaded and approved for the project to sync to the CurseForge App. Projects without approved Release/Beta or those that include Alpha files only will be available on the CurseForge website.

Note - File Type Can be edited at anytime from the Dashboard (Projects page>Files>hover over the file row>Edit file button(right part of the row). After changing the Release Type don't forget to scroll down and hit Submit!)




Additional Files.- These are files attached to another file. Usually these are server files for Minecraft modpacks and optional content for other games. Currently they are not supported in our client.  To upload additional files you would select the file you wish to attach them to in the file view and then select the button on the individual file page that says "Upload Additional Files".


Project / File Relations  -  this is a project-level "Default Relations" that automatically applies to all the project files.They can be embedded libraries, optional libraries, required libraries, tools or incompatible files. Once app integration occurs required libraries will automatically be downloaded with the file.


Project Types

Experimental: Will not sync to the CurseForge app and will not appear in the website searches. The files in this project type can be played using the client import feature. Experimental projects can be changed to regular status by clicking on the 'Submit Project for non-experimental' button in the main project page in the warning box (see image below). Until then, experimental is great as a testing environment for your mods and addons, or a way to setup your project page before publishing it publicly. 



Abandoned: Projects with this status are either set to this by the project owner, or due to the project owner not migrating his account (accounts were migrated twice in the past, once from Curse to Twitch, and as of recent (Dec. 2020), from Twitch to Overwolf. Once the owner migrated his account, his projects will revert to their previous status.
Setting your project as abandoned is mostly useful when a project is not working as intended and the owner does not plan on releasing fixes or updates.

 

Adding Files to a Project

Navigate to your Author Dashboard, go to the "Projects" tab, and select your project by clicking on the "Edit" button. Then choose the Files tab, and at the top right of the page, you can find the "Upload file" option. The file submission page may differ from game to game. 

 

  • Choose file: Pick the file you want to upload
  • Display Name: Your project file is named v2.0 , but you want it to look a bit fancier, type in a name here that will show up in the file list. It is NOT recommended to give every file the same name, and this field is optional.
  • Release Type: Detailed Above
  • Changelog: A place to put all the updates you have done between versions
  • Supported Version: Pick which versions of the game your project is compatible with. You can choose multiple versions.
  • Related Projects: Dependencies and Incompatibilities. This is where you can link to other projects on CurseForge. You can link to a required project, or to a recommended project, or to a project that you know does not work well with your project.
  • Release Options: file publishing time either automatedly after passing moderation or at a later date.


After filling out all of the appropriate fields, click Submit File. You will be redirected to your Files tab and you should be able to see your newly added file. You can add more files by following the same process you just went through. At this point your file will be labelled "Under Review" and it is off to the moderators to review and approve it. They may send it back to you requesting changes. They may also reject it. 

 

Archiving or Deleting Files

There are two ways to remove a file from your project:


Archiving: Removes a file from the public view. It can no longer be downloaded on its own. However if a content pack or another mod depends on it they can still download it as a dependency. This is useful for CoreMods or API/Libraries where you want to remove an old file but not break a mod that depends on the old file. Archived files can be restored by their owner at any time

 

Deleting: Once a file is archived, an author has the option of deleting the file. Once the file is deleted any files that depend on it can no longer access it. Make sure you want to erase the file before doing so. In most cases Archiving is the better option. Deleted files require a site admin to restore.

Minecraft mod loader File Tagging

My project files were changed and are now tagged to support 'Forge', what happened?
As part of our efforts to add support for the Fabric modloader, we now require proper tagging of all project files to be correctly displayed and functional in the client. We have defaulted all untagged files to 'Forge', however you can still change the file tags through each file editing page as we explained in our Newsletter.

If you already have an existing project, this is how you can edit the modloader tag: 

  1. Open the Project Page.
  2. Click the Files Tab.
  3. Click the Edit button(hover over the file name).
  4. Change the Supported Modloader Versions selector to the chosen mod loader.
  5. Scroll down and click Update File


'Customization' category 

The 'Customization' category is a special space for people to upload user made configs for mods that are open ended.

To use the files, you first need the mod which the files were created for (can usually be found in the description) and then you place them where the mod says to. Usually in some folder to replace the config file.