Publisher transparency

How we review Minecraft project listings

The checks used before a project appears as downloadable, comparable, or recommended on FreeMinecraftMods.

Identity check

We compare project name, creator or organization, source links, repository or website references, branding, and release history. Similar titles are not enough to merge listings.

Download availability

A download-focused card should lead to an official page with an identifiable file or supported installation path. Informational pages are labeled differently and should not imply a file exists.

Compatibility check

Minecraft version, loader or platform, client/server side, dependencies, file channel, and update date are treated as separate compatibility signals.

Cross-source comparison

When the same project is available on several sources, each official link is preserved. Download totals are not silently added because platforms count activity differently.

Card quality

Cards should have a meaningful title, creator, project type, source label, summary, and real project image when the source provides one. Category placeholders are used only when no official image is available.

Ongoing verification

Live metadata is cached briefly for performance, then refreshed. Repeated source failures can remove a project from live discovery until the listing is verified again.

See something that needs attention?

Use the contact page with the exact URL and a concise description. Reports about unsafe redirects, false download availability, or creator attribution receive priority.

Submit a correction

A practical review, not a certification

Reviewing a listing does not mean that FreeMinecraftMods has audited every line of code or guarantees that a project will work in every installation. The review is designed to answer the questions a discovery site can verify responsibly: Is the title and creator association credible? Does the destination appear to be an official project page or release page? Is there a usable download path? Do the advertised Minecraft versions and loaders agree with the source metadata? Are images and descriptions attached to the correct project?

Where a source provides an API, live fields are requested through the site’s Cloudflare functions and cached for a limited time. Where no reliable live API exists, the card should identify the source clearly and avoid inventing counts. Missing data is preferable to a convincing but unsupported number.

Cross-source matching

Projects with similar names are not automatically merged. Matching considers the normalized title, creator, project type, official URLs, platform identifiers, and compatibility information. A Forge mod and a resource pack with the same name should remain separate. A project published by the same creator on Modrinth and CurseForge may be shown as available on multiple sources, but each source link remains visible so the user can choose.

Ongoing maintenance

Download availability and compatibility can change after a page is indexed. Live refreshes improve accuracy, but they do not replace human correction paths. Broken source links, moved releases, changed ownership, and misleading images can be reported through the corrections process. Visibility status never overrides the requirement that a project card point to a real and relevant destination.

Trust and quality

What review can and cannot promise

A FreeMinecraftMods review checks discoverability signals that a public site can responsibly verify. It is not a malware audit, code certification, or guarantee that a mod will behave perfectly in every pack.

Useful checks

  • Review can check identity, source destination, compatibility fields, file availability, creator attribution, and visible metadata conflicts.
  • Review cannot prove every dependency combination, server configuration, or private file mirror is safe.
  • When the source page and cached metadata disagree, the source page should guide the installation decision.
  • When user reports show a mismatch, the page should be corrected instead of relying on stale automated data.

Why it matters

This boundary keeps recommendations honest. The site should help players ask the right questions, preserve official source context, and make safer choices without overstating what a discovery page can know.

These practices support people-first pages: the content should help a real player or creator make a decision, verify a source, or report a problem.