Content Rules

Last modified: October 10, 2025

These Content Rules are part of our Terms of Use and apply to all User Contributions, Gaming Content (e.g., mods, resource packs, shaders, data packs), and use of interactive features (e.g., profiles, posts, comments; collectively, "Content") on Modifold (modifold.com and api.modifold.com).

If you find violations of these rules, please report them using the Report button on any project, version, or user page, or email us at support@modifold.com.

1. Prohibited Content

Content must comply with all applicable federal, state, local, and international laws and regulations, including those set by Mojang for Minecraft content. Content must not:

Contain material that is defamatory, obscene, indecent, abusive, offensive, harassing, violent, hateful, inflammatory, harmful, disruptive, 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 rights of any person.
Violate the legal rights (e.g., publicity or privacy) of others or create civil or criminal liability under applicable laws or conflict with our Terms of Use or Privacy Policy.
Promote illegal activity or advocate, promote, or assist unlawful acts, including real-life drugs or illicit substances.
Cause annoyance, inconvenience, or anxiety, or be likely to upset, embarrass, alarm, harm, or deceive others.
Make or share intentionally false or misleading claims.
Impersonate any person or misrepresent your identity or affiliation with any person or organization.
Suggest they are endorsed by us, Mojang, or any other entity, if not true.
Contain excessive profane language.
Upload data to a remote server (not chosen by the user in-game) without clear disclosure.
Bypass Mojang’s restrictions to prevent users from joining certain in-game servers.

2. Clear and Honest Function

Projects (a form of Content) must clearly and honestly describe their purpose in designated areas on the project page. Using confusing language, technical jargon, or obscuring necessary information is a violation.

2.1. General Expectations

Project descriptions must allow users to understand:

What the project specifically does or adds.
Why someone should want to download the project.
Critical information users must know before downloading.

2.2. Accessibility

Project descriptions must be accessible and readable across various mediums. Requirements include:

A plain-text version of the description (images, videos, or other media can complement but not replace it).
Proper use of headers (not for body text).
An English-language description, unless the project is exclusively for a specific language (e.g., translation packs). Additional translations are optional.

3. Cheats and Hacks

Projects must not contain or download "cheats" or "hacks," defined as client-side modifications that:

Are advertised as a "cheat," "hack," or "hacked client."
Provide an unfair multiplayer advantage without a server-side opt-out.
Include functions like:
- X-ray or seeing through opaque blocks.
- Aim bot or aim assist.
- Flight, speed, or other movement modifications.
- Automatic or assisted PvP combat.
- Client-side hiding of third-party modifications with server-side opt-outs.
- Item duplication.

These functions are allowed only if they require server-side opt-in.

4. Copyright and ReUploads

You must own or have the necessary licenses, rights, consents, and permissions to store, share, and distribute Content uploaded under your Modifold account.

Content must not be directly reuploaded from another source without explicit permission from the original author. This restriction does not apply to license-abiding "forks" (modified copies that have diverged substantially from the original project).

5. Miscellaneous

Authors should follow these best practices to ensure faster review and fewer issues (enforcement is at our discretion):

All metadata (e.g., license, client/server-side info, tags) must be accurate and consistent.
Project titles should only include the project name, without unnecessary filler.
Project summaries should be concise, unformatted, and not repeat the title.
External links must lead to relevant, public resources.
Gallery images must be relevant to the project and include titles.
Dependencies must be specified in the Dependencies section of each version.
"Additional files" should only be used for special purposes (e.g., source JAR files), not as substitutes for separate versions or projects.