Roadmap
What is shipped, what comes next, and what is deliberately not planned
This is a short list on purpose. It describes intent, not a schedule, and nothing here is a promise of a date.
Version 1.1.5
The download size is the same figure in the README badge, the download page and the build output, and the release build refuses to build when the README names a different release or a different size.
Version 1.1.4
Every link in the shipped README resolves, and the custom domain procedure matches the way the site is actually published.
Version 1.1.3
The release archive carries the same line endings as the repository, so the download can be checked against the source it was built from.
Version 1.1.2
Stop all wired up, the end reason shown in history, the auto stop step enforced, one name rule across the app, and the network and write claims corrected.
Version 1.1.1
Detection checking in the custom game dialog, a session window that reports detection honestly, and documentation corrected to match.
Version 1.1.0
Custom games, 18 more games in the catalog, and a release archive that is byte-identical across rebuilds.
Version 1.0.0
The launcher, the ten sections, the fixed catalog, session tracking and the build script, all released together.
A refreshed catalog
Discord adds games to its detectable list over time. Each release rebuilds the catalog from that list, so new games appear with the next version rather than through a download.
Compatibility checks on current Windows builds
Verifying the launcher and the WebView2 host on the latest Windows 10 and Windows 11 servicing updates before each release.
Clearer failure messages
When the WebView2 Runtime is missing or a prepared file cannot be written, the message should name the cause and the fix directly, rather than a generic error.
Requests from the issue tracker
Ideas are considered one at a time against the rule that the launcher stays local and contacts no Discord API or gateway. Open an issue to propose one.
Not planned: accounts, telemetry and auto-update
These are excluded by design, not deferred. Zycord has no sign-in, collects nothing and does not update itself.
How to read this
Shipped means the work is in a release you can download. Next means it is the current focus. Later means it is wanted but not scheduled. Never means the decision is settled and will not change.
There are no dates on this page because there is no team with a release calendar. The project is maintained in the open, and the issue tracker is where priorities are discussed.