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 guidelines keep reviews respectful and useful. Reviews that break them are rejected.
Last updated Aug 29, 2026
Be Honest
Reviews must reflect your real, first-hand experience with the project. Don't post fake reviews, knowingly false claims, or misinformation. Don't rate a project you haven't actually used.
Disclose If You Worked on the Project
You may review a project you have worked on, but you must be clearly transparent about your relationship to it in your written review. If you are reviewing a Modrinth project you are on the team for, you must also connect your Modrinth account so your review carries a Verified Developer badge. Reviews that falsely claim to be from a developer will be removed and the account banned.
Be Kind and Constructive
Honest and blunt reviews are fine and we won't reject a review just for being harsh. Aim to be constructive: critique the work, not the people who made it. Personal attacks, hate speech, slurs, threats, and doxxing are never allowed and will be rejected.
Justify Your Rating
Reviews should explain the rating. A low rating without reasoning isn't useful to players, and neither is a perfect rating with no explanation. Tell us what the project does or doesn't do well.
Review Content, Not Compatibility
Do not base reviews on the Minecraft version, hardware, mod loader, or required dependencies the project needs. Reviews that contain porting requests or lower ratings based on such factors will be rejected.
Focus on Quality and Content
Reviews should focus on the project's quality and content. Anything about the experience is fair to judge, including gameplay, balance, features, stability, performance, presentation, and documentation. A developer's personal life, their conduct elsewhere, or how the project was made are not the subject of a review. You can mention these if they are relevant, but your review must stand on the project itself. Reviews that mainly discuss the developer or off-project drama will be rejected.
No Spam or Advertising
Reviews must be genuine reviews of the project. Do not post spam, copypasta, or duplicated text, and do not use a review to advertise or promote another project, product, or service.
Tag Your Spoilers
If your review reveals quest progression, story endings, or hidden mechanics, use spoiler tags to hide them.
Images Must Show the Project
Any image you attach has to show the project itself, from your own use of it. For most projects that means in-game screenshots. For dev tools and libraries with nothing to see in-game, screenshots of the code, config, or output you worked with are fine. Memes, fan art, and screenshots of chats or other websites are not, and we will remove them.
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.
Last updated Aug 25, 2026
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 offending project will include a disclosure notice stating it previously offered compensation for specific reviews. Known incentivized reviews will be 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.