Technical reference / Updated 17 October 2026
Geometry Dash compatibility
MuchoCore exposes version-aware GDPS server endpoints. Supporting a version's server protocol, patching a client executable and verifying every feature in the real game are three different milestones.
Read the protocol/version profiles and client testing guide before claiming a fully supported configuration.
Compatibility at a glance
| Geometry Dash generation | MuchoCore scope | What the status means |
|---|---|---|
| 1.0–1.9 | Legacy compatibility profiles | Version-specific wire behavior and migration utilities are documented. Consult tested fixtures for individual client builds. |
| 2.0–2.1 | Protocol compatibility profiles | Shared server logic with version-specific request/response handling. Feature-by-feature client testing still matters. |
| 2.2 family | Modern protocol support and integrations | Accounts, levels and other core services, with some 2.2-specific feature implementations. |
| 2.209 (binaryVersion 51) | Active compatibility engineering | Client URL-patching work and new API implementation are documented. 100% native compatibility is not yet independently verified. |
What is the GD 2.209 status?
Geometry Dash 2.209 introduced new server endpoints for social and moderation features, editor audio, user searching and more. MuchoCore tracks their implementation separately from full client acceptance. In particular, the new in-game Moderation Queue requires a newer administrative API; registering the route alone is not sufficient proof that the game can parse every response.
For current project-specific engineering status, consult GD 2.209 notes, social API notes and the open compatibility pull requests. A test branch or pending pull request is not equivalent to a published stable release.
Windows, Android and MuchoClient
Server-side protocol support is distinct from the official game executable. Windows and Android clients require a correctly configured GDPS endpoint, and some versions require URL patching. MuchoClient is an optional, separately built Geode companion for client-side additions. Geode compatibility and client packaging must be validated per platform and game build.
See the repository's client setup guide and published releases.
What would prove 100% compatibility?
- Captured request and successful response fixtures for all required client endpoints.
- Registration, login, profile, level list, download/upload, comments, scores and cloud-save tests against actual builds.
- Moderation, notifications, threads, editor sounds and version-new features accepted by the game UI.
- Windows and Android smoke tests, repeatable CI and no major regressions.
This page deliberately separates supported protocol concepts from fully verified client behavior. For the most recent status, use GitHub tests, pull requests and release notes instead of assuming a marketing claim has been tested.