Authors & Contributors

MC-Cheats is maintained by a small team of contributors who build, verify, and update the database. This page lists roles and areas of responsibility. We do not publish personal details — the goal is to make it clear who is responsible for what, not to profile individuals.

Summary

The database is maintained by a rotating group of contributors. Each area — clients, versions, security, guides — has a designated maintainer. The editorial policy applies to all contributors equally. If you want to contribute, use the contact page.

Database maintainer

Role: Oversees the overall structure of the database, coordinates contributions, and applies the editorial policy. Has final say on inclusion and exclusion decisions.

Responsibility: Client database structure, version compatibility matrices, status labels, and consistency across all pages.

Client data contributors

Role: Verify client version support, record status changes, and update client pages when developers publish new releases.

Responsibility: Client entries, changelogs on client pages, and the status tracker. Each contributor follows the same verification process described in the methodology.

Security contributors

Role: Handle file hash verification, VirusTotal data, and security reports. Respond to reported issues.

Responsibility: The security section, the report issue workflow, and disclosures recorded in the changelog.

Content writers

Role: Write and maintain the guides and blog articles. Ensure that long-form content reflects the current state of the database.

Responsibility: Guides, blog, and the compare pages where narrative explanation is required.

How to contribute

Contributions are welcome in the form of corrections, additions, or new data points. To contribute:

  1. Read the editorial policy to understand our standards.
  2. Identify a specific correction or addition you want to propose.
  3. Find a public source for the change.
  4. Submit it via the contact page with the source included.

Contributions that meet our verification standards are usually applied within 7 business days. Contributions that cannot be verified are declined with an explanation.

What we do not publish

Individual contributor names, personal social media, or personal contact details do not appear on this page. Contributors communicate with the site through the team addresses listed on the contact page.

Independence

No contributor accepts payment from client developers for inclusion, status upgrades, or coverage. All data on the site is based on public sources and follows the same verification process. See the editorial policy for the full statement.