A web-based editor for Warcraft III: Reforged CustomKeys.txt files.
Pick a unit, inspect its command card, drag commands onto new slots,
change hotkeys, and export a file the game can load.
Live: https://clemenscodes.github.io/warcraft-hotkey-editor/
The app is built with Dioxus, compiles to WebAssembly, and runs entirely in the browser. There is no server, account system, telemetry, or file upload to a backend.
- Inspect units, heroes, buildings, abilities, items, upgrades, and system hotkeys from the bundled Warcraft III: Reforged data.
- Edit command-card positions visually on the same 4x3 grid Warcraft III uses in-game.
- Override hotkeys and positions for unit commands, hero abilities, research levels, build menus, inventory slots, control groups, and hero selection.
- Highlight hotkey conflicts on the currently selected unit.
- Start from a built-in QWERTY, QWERTZ (by Neo), or default Warcraft III template.
- Export a complete
CustomKeys.txtfile that can be copied into the Warcraft III custom-keybindings folder.
- Open the live editor.
- Import an existing
CustomKeys.txt, or start from one of the bundled templates. - Edit the command cards and system hotkeys.
- Download
CustomKeys.txt. - Put it in Warcraft III's custom-keybindings directory:
Documents/Warcraft III/CustomKeyBindings/CustomKeys.txt
Then enable custom hotkeys in the Warcraft III options menu.
The primary development path is Nix. It provides the pinned Rust, Dioxus CLI, Tailwind CSS, binaryen, and wasm-bindgen versions used by CI and GitHub Pages.
# Dev server: builds generated assets first, then runs dx serve
nix run .#dev
# Production bundle through the same moon task CI uses
nix run .#bundle
# Fully reproducible static bundle in ./result/
nix build .#warcraft-hotkey-editorFor an interactive shell:
nix develop
moon run :dev # Tailwind + dx serve
moon run :bundle # production dx build
moon run :ci # fmt + clippy + tests + wasm build + e2e
moon run :nix/bundle # nix build .#warcraft-hotkey-editorThe dev server usually prints:
http://127.0.0.1:8080/warcraft-hotkey-editor/
Docker is the recommended path on Windows and on any machine where Nix is not available. You need Docker Desktop (or Docker Engine on Linux) and moon installed.
# Start the dev server (accessible at http://localhost:8080/warcraft-hotkey-editor/)
moon run :docker/up
# Run the e2e tests
moon run :docker/e2e
# Stop the dev server
moon run :docker/downThe first run takes several minutes while the image builds (Rust toolchain, dioxus-cli, playwright chromium). Subsequent runs reuse the cached image and named build-artifact volumes so incremental builds stay fast.
The image pins the same tool versions as the Nix dev shell:
| Tool | Version |
|---|---|
| Rust | 1.95.0 |
dioxus-cli |
0.7.9 |
wasm-bindgen-cli |
0.2.121 |
| Tailwind CSS | v4.3.0 |
| Node.js / pnpm | 24.15.0 / 11.0.9 |
crates/hotkey-editor/Dockerfile builds a self-contained nginx image — no
Nix, no dev server, no Rust toolchain at runtime.
# Build prod image and serve on http://localhost:8080/warcraft-hotkey-editor/
moon run hotkey-editor:docker/serve
# Stop the prod container
moon run hotkey-editor:docker/downThe app is served at http://localhost:8080/warcraft-hotkey-editor/.
This path is not supported on Windows. On Linux or macOS, you need matching local versions of:
- Rust with the
wasm32-unknown-unknowntarget dioxus-cli0.7.9wasm-bindgen-cli0.2.121- Tailwind CSS v4
- binaryen /
wasm-opt - Node.js 24.15.0 and pnpm 11.0.9
Version mismatches can fail late in the WASM build, so prefer Nix or Docker unless you are deliberately debugging the toolchain.
E2e tests live in crates/hotkey-editor/e2e/tests/ and run against a
live dev server via Playwright.
# Nix dev shell
moon run hotkey-editor:playwright/test
# Docker
moon run :docker/e2ee2e/run.mjs manages the server lifecycle: it starts dx serve, waits
for the build to finish (watching stdout for "launching app"), runs
the tests, then kills the server. If a dev server is already running on
port 8080, it reuses it and skips the startup entirely.
E2e tests are part of moon run :ci and run on every pull request.
crates/
├── hotkey-editor/ # Dioxus web app (wasm)
│ └── e2e/ # Playwright end-to-end tests
├── warcraft-api/ # Shared Warcraft III data types
├── warcraft-database/ # Pre-extracted Warcraft III object database
├── warcraft-extractor/ # Native CLI: regenerates db.rs from CASC
├── warcraft-keybinds/ # CustomKeys.txt parser and serializer
└── warcraft-slk/ # SLK table parser used by warcraft-extractor
docs/
├── ARCHITECTURE.md # Runtime and build architecture
└── EXTRACTION.md # How db.rs is generated and regenerated
Generated frontend assets such as
crates/hotkey-editor/assets/tailwind.css are not committed. The dev,
bundle, and Nix build paths generate them before Dioxus reads them.
crates/warcraft-database/src/db.rs is machine-generated by
warcraft-extractor from a Warcraft III: Reforged CASC install. Hand
edits are wiped on the next regeneration. To refresh it after a patch
or fix an extraction bug, see docs/EXTRACTION.md.
The extractor is native-only (CASC + cmake + zlib) and is intentionally kept out of the default workspace operations so the wasm build remains clean. Run it explicitly:
nix develop --command cargo run -p warcraft-extractor -- --casc "$W3_CASC"Before pushing a launch build:
moon run :ci # fmt + clippy + tests + wasm build + e2e
nix build .#warcraft-hotkey-editorThe GitHub Pages workflow runs moon run :ci (which includes the e2e
gate) and then builds the same Nix package, deploying the resulting
static files from ./result.
Source code: AGPL-3.0-only. See LICENSE.
Bundled Warcraft III assets and game data: property of Blizzard
Entertainment. See DISCLAIMER.md.