Take me to...
- General Guidelines
- General CurseForge Moderation Policies
- Minecraft specific Moderation Policies
- Hogwarts Legacy specific Moderation Policies
- The Sims 4 specific Moderation Policies
- Ark: Survival Ascended specific Moderation Policies
- inZOI specific Moderation Policies
What happens in Moderation?
CurseForge has a large collection of mods which all go through a series of processors, automated checks, and manual reviewing.
The team works hard to prevent abuse of the platform and puts in great efforts to make sure CurseForge is a safe, fun, and engaging space for authors and players alike.
In case you feel there is an inappropriate project that passed moderation, you can report it via the reporting function in the website. We also invite you to use the ticketing system if you encounter a problematic file, and open an issue with supporting information.
In the instances that a project or file was approved but raises a copyright question (On the content or technical level), the original owner of that content can make a claim by following these guidelines and citing the reason for us to review again.
This process is what makes CurseForge the safest and most trusted source for mods.
What happens when a project doesn't qualify?
If your project submission received a reply that changes are required, or that it was rejected altogether - This guide should help you understand the reasoning better.
Note that these messages are generated either automatically by the system, or by the moderator staff. You can identify a staff member by the Admin tag on their user profile.
DO NOT delete your project or file and try to upload it all again to solve a rejection message, it will only make things more complicated for everyone :)
General Guidelines
- Projects should add value to players while respecting the game creators and the game itself.
- Projects should not encourage any sort of discrimination, in any way.
- CurseForge follows game developers EULA and ToS, and so should your projects. This is true for content and functionality alike.
- Your project should contain distinct content and assets, including in its name, avatar, summary and description. If your project is a fork of another project and allowed by their license - credit and link the original creator and make sure forking is allowed to begin with.
- Moderation is done under our best efforts. You can appeal a rejection, ask for clarification or report a project if you feel they are inappropriate, and are reminded to be respectful at all times.
- It is strongly recommended that you enable a communication channel with your audience to allow bug reporting and feature requests as well as feedback.
- CurseForge supports authors by ads and subscriptions which do not interfere with the players’ in-game experience. We expect the same from the authors who submit projects to the platform.
Projects on CurseForge are first and foremost for the CurseForge community.
Therefore, it is essential that each project provides comprehensive information about its mod functionality, support, and relevant content directly on CurseForge.
Any promotional or non-descriptive content and information, including but not limited to:
- Server hosting affiliate banners (with the exception of the integrated Bisect Hosting banner)
- Personal donations (such as ko-fi, Patreon, etc..)
- Personal websites
- Cross-hosting or portfolio pages leading outside of the platform
must appear at the bottom of the page, following the project description.
In addition, any such content must be of reasonable size and relevant content so as to not overwhelm the description page and distract users from the project's relevant information.
It is allowed to use dependency badges or functional link badges at the top similar to the below for cross-hosting/social linking purposes but those must not include any promotional material.
We recommend reviewing our author support section and articles for more information regarding project requirements, submissions and moderation.
General CurseForge Moderation Policies
| Policy | Description |
| Clear and Informative Description | Your description should include what your project adds or changes in the game. If it is a fork, you must describe what has changed from the original and you cannot copy the description of the original project. The description can include descriptive and storytelling langauge, but it must also contain functional information so the players know what your mod does. Avoid using generic terms: "Changes the core/vanilla game" or "adds items to the game" is not enough. |
| Clear Summary | Your Summary is like a tldr for your Description. You can provide a more high level general description here, preferably no longer than 1 sentence. Try to avoid copying the same text from the description. |
| English content | Names must be in English. Descriptions and Summaries can have other languages in addition, but must have English translations that appear before other languages. |
| Name - functional Information | Names should not contain game name, versions, file versions ect.... Any technical information belongs in the description or relevant file tagging. |
| Project Avatar | Avatars must not be solid colors, contain anything NSFW or copyrighted imagery. All avatars need to be 400x400 pixels. Note - There is a known bug currently with webp formats, avoid using those |
| Inappropriate Project | Projects that either do not appear to be the correct content for the current category, game, or adult content in an age restricted game or otherwise deemed inappropriate by moderation. NSFW and 18+ content would normally be prohibited (nudity, adult substances, etc.) |
| Third Party Downloads | External download links for files are not allowed. |
| Texture Pack Missing Sample | Texture Packs/Resource Packs or other visual mods must have a sample image showing accurate in-game representation of the content. |
| Content Copyright | If you upload a project that is using copyrighted content from other registered works or belonging to other authors on the platform, you must either be allowed to do so under their respective license or have explicit permission to do so. Either way getting permission from the content owner is recommended, and a proper credit is also required. Accounts found to be abusing this can be subject to a permanent ban. |
| Anti-Griefing | Content that is used to harass, discriminate or negatively impact players in-game in any way is not allowed. |
| Fair Play | It is not allowed to upload multiple similar and/or low effort projects in an attempt to game the system. It is not allowed to completely overhaul previously approved projects to bypass moderation and/or use their previous popularity for the purpose of a new project. Additionally - Files updates in order to increase visibility is not allowed. These can include but are not limited to:
|
Minecraft specific Moderation Policies
| Policy | Description |
| Modpack format | Modpacks must be created with the CurseForge App, with the correct format. Read more about this here: Exporting a Modpack for Submission |
| Zip formats | Any files uploaded in an archived folder must be in .zip format. .rar or .7z aren't supported by the system. You also can't rename a .rar archive to .zip you must zip it Any zipped formats need to not include root folders but zip the contents directly |
| Non-CurseForge Mods | Mods that are not hosted on CurseForge and are not listed in the Non-CurseForge Approved list cannot be included in modpacks. You can request to add a mod via the form linked in the list. |
| Server Files | To upload a server pack you must upload the file as an "Additional File" to your relevant main pack file. |
| Removed from CurseForge | All files within a modpack -for CF hosted mods- must exist and be approved on CurseForge. Files or projects that have been deleted or archived cannot be used in new packs |
| Manually Modified Manifest | Edits to the manifest that the CurseForge App generates for a modpack are not allowed. |
| Mod Loader compatability | Modpacks must include mods with the matching Mod Loader only. Even if those mods may work in-game, that is not normally the case, and the system has no way to know which. It is up to the mod author to tag their mods with all compatible mod loaders |
Hogwarts Legacy specific Moderation Policies
| Policy | Description |
| General Warner Bros. guidelines | See related article |
| In-game images | Projects must have at least 1 image added to the Gallery to demonstrate the mod looks in-game. This can be relevant models, UI screens, or others. |
The Sims 4 specific Moderation Policies
| Policy | Description |
| General Maxis guidelines | See related article |
| Unnecessary files | CC/Mod files should not include preview images, txt instructions or any files that aren't functionally required for the mods. These just clutter the modding folders for players. Preview images should instead be uploaded to the project page. Any message to players should be added to the project's description. |
| File upload format | When uploading files you must zip them. Even if its a single .package file |
| Proper file types | Each root category has it's own type of files supported:
|
| Proper categorization | Each type of CC/Mods belong in specific root categories(or Class). This is to ensure proper search and installation by the client
|
Ark: Survival Ascended specific Moderation Policies
| Policy | Description |
| General Studio Wildcard guidelines | See related article |
inZOI specific Moderation Policies
| Policy | Description |
| General KRAFTON guidelines | See related article |