Editorial Policy

This policy describes how entries are selected, how data is verified, what we refuse to publish, and how corrections are handled. It applies to every page on this site.

Inclusion criteria

A client is added to the database when all of the following are true:

• It has a public source — a repository, official website, or release channel.
• There is enough public information to determine its current status.
• There is a version or version range we can verify support for.
• It has been requested by users or referenced by at least one other tracked entity.

A client is not added merely to fill a keyword. Pages exist for entities that have their own data. We would rather have thirteen well-documented clients than fifty thin entries.

Exclusion criteria

We do not include:

• Clients without a verifiable public source.
• Clients that exist only as paid, closed-source products with no public metadata.
• Clients that have been discontinued for more than one major Minecraft version with no archive, unless the archive is publicly documented.
• Entities added purely to produce keyword variations of an existing page.

Status assignment

Each tracked client receives one of five status labels. The label is based on public repository activity:

Verification process

1. Identify the primary public source for the client.
2. Record the latest release version and date from that source.
3. Compute the SHA-256 hash of the current file when a stable download is available.
4. Check VirusTotal for existing reports; record detection count and report link.
5. Cross-check version support against the client's changelog or release notes.
6. Assign a status label and record the last-checked date.

Full methodology: verification methodology.

What we refuse to publish

• Absolute claims. "100% safe", "virus-free", "undetectable", "best" — none of these can be proven and none appear on the site.
• Fake reviews. We do not generate testimonial quotes or invent usernames.
• Unverified numerical claims. "50,000 users", "10,000 downloads" — we do not publish numbers we cannot source.
• Unsubstantiated comparisons. Comparisons use factual criteria only.
• Duplicate pages. We do not produce keyword-variation copies of the same content.

How errors are handled

1. A correction is submitted through the contact page or a page's correction link.
2. We verify the correction against primary sources.
3. If the correction is valid, the page is updated and the change is recorded in the changelog.
4. If the correction cannot be verified, we respond with the reason.

Update cadence

• Client pages: reviewed weekly.
• Version compatibility: reviewed on new Minecraft releases and weekly thereafter.
• Security pages: reviewed monthly and updated on new findings.
• Blog articles: published when a topic warrants a longer write-up; articles are not backdated.

Author responsibilities

Contributors to this site are expected to:

• Cite sources for every factual claim.
• Refuse to publish data that cannot be verified.
• Correct errors when identified.
• Apply the same status labels, criteria, and tone across all pages.

Author profiles: authors.

Independence

MC-Cheats is not affiliated with any client developer. We do not accept payment for inclusion, status upgrades, or higher placement in the database. Clients are added, updated, and removed based on verifiable data alone.

Contact for editorial matters

Editorial corrections and policy questions: corrections@mc-cheats.com.

Last updated: 2026-09-24