Changelog
Every change to the MC-Cheats database is recorded here with a date. Client status updates, version compatibility changes, security disclosures, and corrections.
What is tracked here
This changelog records meaningful changes to the database: when a client's status label changes, when version support expands or contracts, when a new client is added or removed, when a security issue is found, and when a correction is applied. Minor edits are not listed. Timestamps are in UTC.
Recent Changes
| Date | Category | Change |
|---|---|---|
| 2026-09-24 | Compatibility | Verified Wurst 26.2 build. Added 26.2 column to compatibility matrix. |
| 2026-09-24 | Database | Added individual client pages for Inertia, Raven, Raven XD, and Boze. |
| 2026-09-24 | Security | Published verification methodology, hash verification guide, and VirusTotal guide. |
| 2026-09-24 | Correction | Removed all "100% virus free" and similar unverifiable claims from site copy. Replaced with source-linked verification data. |
| 2026-09-24 | Database | Removed Impact Client from tracked clients — the client does not support 1.21 or later releases. |
| 2026-09-20 | Site | Migrated all inline CSS to a single external stylesheet for improved caching and Core Web Vitals. |
| 2026-09-18 | Status | Changed Phobos status from "Unknown" to "Discontinued" following source archive review. |
| 2026-09-15 | Status | Changed BleachHack status from "Active" to "Stale" after 14 months without commits. |
Frequently Asked Questions
How often is the changelog updated?
The changelog is updated whenever a meaningful change occurs in the database. Client pages are reviewed weekly; version compatibility is reviewed on new Minecraft releases; security notes are updated as findings arise.
Why are minor edits not listed?
The changelog is intended to track changes users might notice: status changes, version support shifts, security findings, and corrections. Formatting updates, spelling fixes, and other cosmetic edits are not listed.
Can I subscribe to changelog updates?
Not at this time. The blog occasionally publishes longer-form write-ups of significant changes.
How do I report a change that should appear here?
Use the report issue page. Include the URL, the current data, and the correct data with source.