Changelog

Version 1.1.5

1.1.5 Current

Released 6 November 2026

Fixed

  • The download size is given to the same precision everywhere. The README badge said 0.9 MB while the download page and the build output said 0.95 MB. Both now say 0.95 MB, which is the archive rounded to two decimal places.
  • The landing page described the current release with the work of 1.0.0 under a 1.1.5 label. It now describes the launcher without naming work from a particular version.

Documentation

  • The site reads the download size from the README badge instead of keeping its own copy, so the two cannot drift apart. The release build fails if the badge and the archive it just packed disagree, and if the README names a release other than the one being built.

1.1.4

Released 6 November 2026

Fixed

  • The README inside the download no longer links to files it does not ship. It pointed at docs/, CONTRIBUTING.md and SECURITY.md, none of which are in the archive, so thirteen of its fourteen links went nowhere. Repository files are now absolute URLs, and the build fails if a shipped document links to something the release does not contain.

Documentation

  • The custom domain procedure described a CNAME file and a constant that do not exist. It now matches how GitHub Pages builds this site from a workflow, and the site generator fails if a file naming the site address still names the old one.
  • The contributing guide said the Pages workflow runs on a push to main. The default branch is master. It also now names the checks the build runs, so a contributor who trips one knows what failed.

1.1.3

Released 6 November 2026

Fixed

  • The published archive now carries the same text files as the repository. The release workflow runs on Windows, where Git wrote CRLF into the checkout, so every text file in the download differed from its source by one byte per line. Line endings are now pinned to LF, and the build fails if a copied file still contains CRLF.

Documentation

  • The size of the session stub is given as about 36 KB. The binary is 36,864 bytes, and several pages said 35 KB.

1.1.2

Released 6 November 2026

Fixed

  • Stop all on the Sessions page now ends every session. The button was present and did nothing.
  • History shows how each session ended. The Reason column was in the table but never filled.
  • Auto stop rounds a typed value to the nearest fifteen minutes, so the documented step is the step that applies.
  • Game names containing control characters are refused in the custom game dialog and in the library, not only when a session starts.
  • Links on the not-found page resolve from any mistyped path, instead of only from the site root.

Documentation

  • Statements that the launcher makes no network request were corrected. The interface does load game icons from Discord's CDN, and several pages said otherwise.
  • The claim that nothing is written outside the data folder now notes the log export you choose a location for.
  • The path rules name all eight extensions the validator accepts, instead of describing the rule as .exe only.
  • The self test figure for 1.0.0 now matches the checks that release ran.

1.1.1

Released 6 November 2026

Custom games

  • The custom game dialog checks the executable name against the same detectable list the catalog is built from, and says what it finds before you add the game.
  • A custom game whose file name is not on that list is still accepted, with a warning that the session will run but will not appear as activity. It carries a Not detected tag wherever it is shown.
  • The session window reports whether the file name is one Discord lists, instead of claiming detection for every session.

Documentation

  • The custom game list was described as behaving like any other game. Discord credits a session only when the running process name is on its detectable list, and this page now says so.
  • The path rules list all eight extensions the validator accepts, and the self test figures match the checks it runs.

1.1.0

Released 6 November 2026

Custom games

  • A Custom game button on the Games page adds a title Discord does not list. You give it a name and the executable name, and it is searchable, savable and startable like any other game.
  • Custom entries appear in search, in the library, in favourites and in history, and they carry a Custom tag wherever they are shown.
  • A Custom games filter isolates them, and Remove takes the entry out of the catalog, the library, the favourites and the recents together.
  • Up to 200 custom entries. Names are unique, case-insensitively, and the executable goes through the same path validation as a catalog entry.

Catalog

  • 18 more games: 10,465 in total, with 11,171 executable entries and 10,452 icons.
  • The catalog now keeps the non-.exe entries Discord publishes, such as Aion's aion.bin, the Command & Conquer .dat and .game files, and the YOU DON'T KNOW JACK .jbg builds. Windows starts a program under any extension, so these run exactly like the .exe entries.
  • Script types are still refused. A session can never be a .bat, .cmd or .ps1.

Packaging

  • Release archive entries now carry a fixed timestamp, so rebuilding the same folder produces a byte-identical zip and an identical checksum. The compiled binaries still carry their own build timestamps, so two separate builds do not match.

1.0.0

Released 5 November 2026

The first public release. Everything below shipped in it.

Launcher

  • A borderless window with a native title bar, minimise, maximise and close.
  • The interface is rendered in Microsoft Edge WebView2 from files in the same folder. No installer, no background service, no account and no server.
  • Ten sections: Home, Games, Library, Favourites, Sessions, History, Settings, Logs, About and Help.
  • Light and dark themes, a reduced motion setting, and tray behaviour that keeps sessions running when the window closes.
  • Settings, library, favourites, history and logs are stored in %LOCALAPPDATA%\Zycord. Nothing leaves the machine.

Catalog

  • 10,447 games and 11,151 executable entries, generated from Discord's public detectable list and filtered to Windows executables.
  • 20 launcher entries and 10,434 game icons.
  • The catalog is stored as about 583 KB compressed, against about 2.0 MB of raw JSON.
  • Search by name, alias or theme, with exact matches ranked first, then prefixes, then word matches.
  • Filters for a single executable, multiple executables, and games that ship a launcher process.

Sessions

  • A session stub of about 35 KB, copied into %LOCALAPPDATA%\Zycord\games\<app_id>\ under the executable name Discord expects, then started.
  • The stub holds no game code and makes no network calls. It shows a window with the elapsed time and an End session button, or runs with no window at all.
  • It watches the launcher's process id and exits if the launcher disappears, so a crash cannot leave a session running with no way to stop it.
  • A live timer, an optional auto stop in minutes, extension by fifteen minutes, and protection against starting the same game twice.
  • Every session is written to history with its start, stop, duration and end reason.

Packaging

  • python build.py compiles the launcher and the stub with the .NET Framework compiler that ships with Windows, runs a 23 check self test against a real WebView2 host, and writes Zycord-1.0.0.zip with SHA256.txt.
  • The zip you download is 0.93 MB. Unpacked, the release folder is about 3.1 MB across 12 files, including the WebView2 assemblies.

Security

  • Every path that comes from the catalog or from user input is validated before use. The self test feeds ten hostile inputs through the validator and requires all ten to be rejected.
  • The interface runs under a content security policy that allows only local scripts and styles, plus images from the Discord icon CDN.
  • A build time check fails the build if an identifier from an earlier project appears in the source.

Earlier versions

Version 1.0.0 was the first release.

The full history is kept in CHANGELOG.md, and each release is tagged at github.com/iZynu/zycord/releases.