projects / wow-toolbox
WoW Toolbox
A commercial desktop toolbox for World of Warcraft 3.3.5 private-server development: spells, items, classes, talents, quests and a 3D map editor. React 19 and Tauri 2 over a Rust core.
- 512 Accounts Supabase· live
- 3,337 Commits GitHub commits· live
- 64 Signed releases GitHub releases· live
- 957 Downloads GitHub releases· live
- v1.0.78 Current version GitHub releases· live
Overview
Problem
WoW 3.3.5 server developers edit spells, items, talents and quests through scattered command-line tools and hand-written SQL.
Approach
One desktop app with 30 visual editors and a 3D map editor. A Rust core parses DBC files and talks to MySQL, and all 541 IPC channels moved from Electron to Rust behind the same API.
Result
DBC parse in ~50 ms instead of ~2.5 s, delta auto-save in ~5 to 15 ms, and a renderer that shipped unchanged.
Profiled before optimizing. The JS DBC reader was what blocked 50k-record table loads, not the renderer.
On the Electron to Rust port
Decisions · why this stack
-
Port behind the existing API
All 541 IPC channels in 33 namespaces moved from Electron to Rust behind window.toolboxAPI, guarded by tests, so the React renderer shipped unchanged.
-
Link the Rust core as a plain crate
The Tauri shell calls the core directly, so DBC parsing, MPQ access and model decoding are function calls with no napi or serialisation boundary.
-
Stream geometry over a WebSocket
Terrain and model geometry stream from a Rust-hosted WebSocket into three.js, because IPC serialisation was the bottleneck for the 3D editors.
-
Delta auto-save with a write-ahead log
The core writes batched diffs to a WAL and replays it after a crash, so saving can run constantly without the user noticing.
-
Detect the server schema
MySQL profiles fingerprint the characters and world tables to tell TrinityCore from AzerothCore, so one build works against both.
-
Keep the old settings format
Encrypted settings stores are read and written in place in their Electron-era format, so existing installs carried over without a migration.
Runs in production
- Auth
- Supabase auth with role-based entitlements
- Billing
- Stripe billing tiers tied to entitlements
- Releases
- Signed builds through GitHub, in-app auto-update
- Collaboration
- Hocuspocus and Yjs for real-time shared editing
- Feedback
- In-app issue reporting and changelog
Stack
- React 19
- Redux Toolkit
- three.js
- React Three Fiber
- Pixi
- Tailwind
- Tauri 2
- Rust
- Supabase
- Stripe
- Hocuspocus
- Yjs
- MySQL
Architecture
Three views of the same system
Solo-built desktop platform: React 19 renderer, Tauri 2 shell, Rust core linked straight in. Same architecture at three depths. Start glanceable, drill in as far as you want.
Switch views 1 2 3
Demo
Screens
Numbers
Measured · one linear scale per row
By the numbers
- 541 IPC channels in 33 namespaces Codebase
- 30 Visual editors Codebase
- 41 Feature folders Codebase
- ~71k Lines of TypeScript, renderer Codebase
- ~77k Lines of Rust, core Codebase
- ~30k Lines of Rust, Tauri shell Codebase
- ~50 Rust DBC parsers Codebase
- 150+ Schema definitions Codebase