Is there an official .exe download?

No. GitHub Releases only contain release notes, not binaries. You must build the executable yourself via GitHub Actions on your own fork or from source locally.

Does WandEnhancer send my data anywhere?

The .NET patching step runs locally and contacts no update or telemetry service. The optional Remote Web Panel listens on your LAN and may fetch trainer translations/artwork through Wand's existing API/CDN paths, but it doesn't include your Wand bearer token or installation-path fields in its protocol.

What license is this under?

Apache-2.0, as stated in the repository's LICENSE.md file.

Is the Remote Web Panel safe to expose to the internet?

No. It uses plain HTTP on port 3223 with no pairing code or authentication, so anyone who can reach that port can control the active trainer. Use it only on a trusted LAN or over a VPN like Tailscale, never port-forwarded to the public internet.

What do I need to build this from source?

On Windows: CMake, Node.js with pnpm, Visual Studio 2022 (or Build Tools) with the Desktop development with C++ workload and MSBuild, and the .NET Framework 4.8 targeting pack. Run build.cmd after installing these.

How do custom JavaScript injections work?

You add .js files via the patch dialog or place them in a renderer-scripts/ folder next to the patcher, then patch as usual. The scripts run inside Wand's renderer with DOM access and Node require, and this requires the Remote Web Panel patch to be enabled since it reuses the same injection mechanism.

Wand Enhancer: A local patcher that extends

WandEnhancer is an open-source interoperability tool for the Wand (WeMod) desktop app. It's aimed at Wand users who want more control over the client's look and behavior, and at developers comfortable building their own executable from source. The project patches local Wand installation files and a bundled version.dll proxy to flip an Electron ASAR-integrity fuse inside Wand's own process. It does not inject into other processes, contact an update server, or send telemetry.

Key features

Local environment configuration: manage client-side settings that Wand itself doesn't expose.
Automated compatibility adjustments: keeps the patch working across new Wand client versions without manual rework.
Layout and theme customization: client-side visual changes only, no server-side bypass.
AI features: additional AI-driven functionality baked into the patched client.
Remote Web Panel: a LAN HTTP/WebSocket server on port 3223 that lets you control the active trainer from a phone via QR-code pairing, no login token exposed in the protocol.
Custom script injection: drop your own .js files into a renderer-scripts/ folder (or add them in the patch dialog) to run inside Wand's renderer with full DOM access and Node require.

Ideal use cases

WandEnhancer fits Wand users who want to tweak the client's UI, fix small client-side annoyances with a custom script, or control the app remotely from a phone on the same network. It also suits developers who want to study Electron ASAR-fuse patching or WPF-based interop tooling and are willing to build from source.

It is not a fit if you're looking for an official, signed, ready-to-run executable: the project deliberately ships no prebuilt binaries, and any .exe you find on YouTube, Discord, or a random mirror is not from this project and may be malware. It's also not suited for exposing the Remote Web Panel to the open internet, since the panel uses plain HTTP with no pairing code or auth, anyone who can reach port 3223 can control the active trainer. For remote access outside your LAN, the README recommends a VPN tool like Tailscale rather than opening the port directly.

Installation

There are no official compiled downloads. You build the executable yourself, either via GitHub Actions on your own fork or locally from source.

Via GitHub Actions (recommended path in the README):

Fork the repository on GitHub.
Use Sync fork to pull the latest fixes before each build.
Open your fork's Actions tab and enable workflows if prompted.
Select the Build executable workflow and click Run workflow on the default branch.
Wait for the run to finish, then download the artifact.
Extract the zip and run WandEnhancer.exe to apply local client modifications.

Building from source on Windows requires:

CMake
Node.js and pnpm
Visual Studio 2022 or Build Tools for Visual Studio 2022 with MSBuild
the Desktop development with C++ workload
.NET Framework 4.8 desktop build tools / targeting pack

Once these are installed:

git clone https://github.com/k1tbyte/Wand-Enhancer.git
cd Wand-Enhancer
build.cmd

build.cmd installs the web panel's dependencies, builds the frontend, compiles the native helper with CMake, restores NuGet packages, and builds the WPF solution.

For custom scripts, enabling the Remote Web Panel patch is required since script injection reuses the same renderer-injection mechanism. Add .js files through the patch dialog or place them in a renderer-scripts/ folder next to the patcher executable before patching.