If you find any violations of these Rules on our website, you should make us aware. You may use the Report button on any project, version, or user page, or you may email us at email@example.com.
1. Prohibited Content
Content must in their entirety comply with all applicable federal, state, local, and international laws and regulations. Without limiting the foregoing, Content must not:
- Contain any material which is defamatory, obscene, indecent, abusive, offensive, harassing, violent, hateful, inflammatory, harmful, damaging, disruptive, contradictory, or otherwise objectionable.
- Promote sexually explicit or pornographic material, violence, or discrimination based on race, sex, gender, religion, nationality, disability, sexual orientation, or age.
- Infringe any patent, trademark, trade secret, copyright, or other intellectual property or other rights of any other person.
- Promote any illegal activity, or advocate, promote or assist any unlawful act, including real-life drugs or illicit substances.
- Cause annoyance, inconvenience, or needless anxiety or be likely to upset, embarrass, alarm, annoy, harm, or deceive any other person.
- Make or share intentionally wrong or misleading claims.
- Impersonate any person, or misrepresent your identity or affiliation with any person or organization.
- Give the impression that they emanate from or are endorsed by us or any other person or entity, if this is not the case.
- Contain an excessive amount of profane language.
- Be designed to upload any data to a remote server (i.e. one that the user does not directly choose to connect to in-game) without clear disclosure.
2. Clear and Honest Function
Projects, a form of Content, must make a clear and honest attempt to describe their purpose in designated areas on the project page. Necessary information must not be obscured in any way. Using confusing language or technical jargon when it is not necessary constitutes a violation.
2.1. General Expectations
From a project description, users should be able to understand what the project does and how to use it. Projects must attempt to describe the following three things within their description:
- what the project specifically does or adds
- why someone should want to download the project
- any other critical information the user must know before downloading
Project descriptions must be accessible so that they can be read through a variety of mediums. All descriptions must have a plain-text version, though images, videos, and other content can take priority if desired. Headers must not be used for body text.
Project descriptions must have an English-language translation unless they are exclusively meant for use in a specific language, such as translation packs. Descriptions may provide translations into other languages if desired.
3. Cheats and Hacks
Projects cannot contain or download "cheats", which we define as a client-side modification that:
- is advertised as a "cheat", "hack", or "hacked client"
- gives an unfair advantage in a multiplayer setting over other players that do not have a comparable modification and does not provide a server-side opt-out
- contains any of the following functions without requiring a server-side opt-in:
- X-ray or the ability to see through opaque blocks
- aim bot or aim assist
- flight, speed, or other movement modifications
- automatic or assisted PvP combat
- active client-side hiding of third party modifications that have server-side opt-outs
- item duplication
4. Copyright and Reuploads
You must own or have the necessary licenses, rights, consents, and permissions to store, share, and distribute the Content that is uploaded under your Modrinth account.
Content may not be directly reuploaded from another source without explicit permission from the original author. If explicit permission has been granted, or it is a license-abiding "fork", this restriction does not apply. We define "forks" as modified copies of a project which have diverged substantially from the original project.
There are certain other small aspects to creating projects that all authors should attempt to abide by. These will not necessarily always be enforced, but abiding by all will result in a faster review with fewer potential issues.
- All metadata, including license, client/server-side information, tags, etc. are filled out correctly and are consistent with information found elsewhere.
- Project titles are only the name of the project, without any other unnecessary filler data.
- Project summaries contain a small summary of the project without any formatting and without repeating the project title.
- All external links lead to public resources that are relevant.
- Gallery images are relevant to the project and each contain a title.
- All dependencies must be specified in the Dependencies section of each version.
- "Additional files" are only used for special designated purposes, such as source JAR files. In other words, separate versions and/or projects are used where appropriate instead of additional files.