Publisher transparency
Corrections and broken-link policy
How to report inaccurate project information, unavailable downloads, wrong creator credit, or unsafe destinations.
What to report
Report the listing URL, expected official source, problem type, Minecraft version, loader, and the final destination or visible error. Do not include passwords, cookies, private financial details, or private server information.
Priority order
Unsafe redirects, wrong project merges, creator attribution errors, and false download availability are handled before minor description or formatting issues.
What we change
We may update metadata, separate merged records, replace a source, mark a file unavailable, or remove a listing from live results while it is reviewed.
Creator requests
Creators can request corrections to names, links, images, descriptions, and project associations. Ownership claims follow the site verification process.
No hidden replacement
If a project is removed or no longer downloadable, we do not silently send users to an unrelated project. Alternatives are shown as separate recommendations.
What happens after a report
A report is first checked against the exact listing and destination supplied by the reporter. The reviewer confirms whether the issue can be reproduced, whether the project has moved, and whether the problem affects one source or every source attached to the project. When a card combines information from more than one platform, each source is checked separately so that a valid page is not removed because a different source failed.
Temporary API failures are not treated the same as a removed project. A listing may be marked unavailable or withheld from discovery while the source is checked again. If the creator has intentionally archived the project but leaves downloadable files available, the page may remain with a clear archived or unsupported status. If no usable official file or project page remains, the listing should not continue presenting itself as downloadable.
Evidence and response expectations
The most useful reports include the page URL, the button or link used, the final destination, the visible error, and the Minecraft version or loader involved. Screenshots can help, but they should not contain account tokens, private messages, private financial data, server credentials, or personal information. Reports are evaluated on the evidence supplied rather than on the number of people repeating the same claim.
FreeMinecraftMods does not promise a fixed response time for every metadata issue. Unsafe redirects, impersonation, malicious files, false creator credit, and links that claim to offer a download but cannot do so receive the highest priority. Routine description changes and cosmetic image issues are handled after safety and availability problems.
Trust and quality
What makes a useful correction report
A good correction report gives enough evidence for the listing to be fixed without guessing. The most helpful reports include the FreeMinecraftMods page URL, the official source URL, the specific field that is wrong, and a short explanation of the expected change.
Useful checks
- Report broken official links, copied or mismatched project pages, unsafe redirects, wrong creator attribution, and incorrect download availability.
- Include source evidence when a project has moved, changed ownership, removed files, or switched supported loaders.
- Describe whether the issue affects a single page, a creator profile, a category hub, or search results.
- Do not send private files or account credentials as proof; public source links are safer and easier to verify.
Why it matters
Corrections are handled as maintenance, not as hidden reputation votes. A listing can be updated, relabeled, de-emphasized, or removed from download-focused results when the available source evidence changes.
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.