Repository navigation
Conversation
Discord's game detection matches a running process named hex.exe to the Steam game HEX: Shards of Fate, so the app was shown as that game for as long as Hex ran. The detectable list has exactly one entry with that bare executable, which is why the managed install matched. Windows now installs and runs hex-voice.exe. A terminal still runs hex: PATHEXT resolves it to hex.com, which starts the GUI executable beside it. Releases before the rename were staged as hex.exe by their own updater, so the app copies such an install to the new name, repoints the Start Menu shortcut and Launch at login, and relaunches before claiming the single instance. The installer, script installer, updater, console entry point, and docs use the new name; the published artifact stays hex.exe.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Discord's game detection matches a running
hex.exeto HEX: Shards of Fate. Discord's detectable list has exactly one entry with that executable: app496778870104653824,"executables": [{"name": "hex.exe", "os": "win32"}]. Hex's managed install ran exactly that name, so Discord showed the game for as long as Hex ran (#445).Windows installs now run
hex-voice.exe. The release artifact is still built and published ashex.exe; only the installed name changes.hexin a terminal still works:%APPDATA%\hex\bin\hex.comis on PATH and startshex-voice.exebesidecurrent-version, falling back tohex.exefor releases before this change.versions\<version>\hex-voice.exeand never writeshex.exeagain. Update identity is the executable's SHA-256, which the rename doesn't change.hex.execopies itself tohex-voice.exeon its first launch (only when it is the versioncurrent-versionnames, so a stale version can't take the launch surfaces), repoints the managed Start Menu shortcut and Launch at login, and relaunches before claiming the single instance. A failure keeps the old copy running and retries on the next launch.install-windows.ps1, the uninstaller's process stop, the console entry point, and the installer test use the new name.AppId, the receipt,current-version, and the published artifact names are untouched.docs/windows.md, the Windows feature map, and the release docs record the reason and the migration.Tests:
cargo test --bin hex updater::(32 pass) and the newinstall_namelayout test;crates/consoletests find both names; the Windows-only updater tests (activation_names_the_executable_for_discord_and_keeps_the_old_version,the_renamed_copy_is_complete_or_absent) compile under xwin and run in Check Windows.cargo clippy --bin hex --all-targets -D warningspasses on Linux and forx86_64-pc-windows-msvc;scripts/code-shape.py --checkpasses. No live Discord check was run.