Community

Community guidelines

Reviewer guidelines are also shown before you submit a review. Creator guidelines apply to project authors and communities. Bookmark this page for reference.

Reviewer Guidelines

Our review guidelines are designed to maintain a respectful and informative environment. Reviews that violate these guidelines will be removed.

Be Authentic, Be Kind

Reviews should be honest and respectful. Constructive criticism is welcome, but disrespectful or offensive language is not allowed. Avoid hate speech, personal attacks, and fraudulent information. We strive to create a friendly and safe space for all users.

Justify Your Rating

Your written review should explain why you gave your score. A low rating without reasoning isn't useful to other players, and neither is a perfect score with no explanation. Tell us what the mod or modpack does well or where it falls short.

Review Content, Not Context

Do not base reviews or ratings on the Minecraft version, hardware, or mod loader the mod or modpack is designed for. Reviews that contain porting requests or lowering ratings based on such factors are not acceptable.

Focus on Quality and Content

Reviews and ratings must focus on the mod or modpack's quality and content. Refrain from discussing the personal lives of developers or their decisions unrelated to the project. This also includes reviews that are spam or solely a "copypasta" that do not actually review the project's quality or content. Irrelevant reviews will be removed.

Tag Your Spoilers

If your review reveals quest progression, story endings, or hidden mechanics, use spoiler tags to hide them.

In-game Screenshots Only

If you are uploading images as part of your review, they must be in-game screenshots of the mod or modpack.

No Alternate/Multiple Accounts

You may not leave reviews on multiple accounts. If we detect you are leaving multiple reviews with different accounts, all associated accounts and IP addresses will be banned.

Creator / project author guidelines

Rules for developers and project owners. Violations can lead to notices on the project, review removal, or account action.

Developers reviewing their own projects must be transparent

You may review projects you have developed for; however, you must be clearly transparent about your relationship to the content. Failure to do so will lead to your review being flagged or removed.

If reviewing your own Modrinth project, connect your Modrinth account in ModDex account settings to get a Verified Developer badge attached to your review automatically.

Reviews that impersonate or falsely advertise that they are a developer will be removed and their account banned.

No compensation for specific ratings or reviews

Any form of compensation or incentives, whether direct or indirect, in exchange for specific ratings or reviews is not allowed.

Projects whose developers are found to engage in such practices will be flagged. The project's description will include a notice stating: "This project has previously offered compensation for specific reviews. Known incentivized reviews have been removed."

No encouraging specific ratings, raiding, or review bombing

Organizing or participating in campaigns to flood projects (including your own) with specific or controlled reviews or ratings is strictly prohibited. Developers must not control reviews from their communities, whether positive or negative. Encouraging honest reviews is fine; manipulating ratings is not.

Examples of what developers can and cannot say

  • "@everyone Go to ModDex and leave a 5-star review! Let's get to the top!"
  • "@everyone Leave a 1-star review on my project! Let's be the worst rated project on ModDex."
  • "@everyone My project is on ModDex! Please leave a review. If you like my project, maybe leave a 5-star review!"
  • "@everyone Check out our project on ModDex and share your honest thoughts!"

The point is to keep ModDex useful, not a popularity contest where the biggest Discord ping wins the leaderboard.

Developers encouraging or compensating for specific ratings (especially against other projects) will face serious consequences, such as removal of reviews, permanent disabling of all reviews on their own project, and/or a notice stating this project participated in review bombing other projects.