Advanced UX and interoperability extension for Wand (WeMod) app

★ 33,513⑂ 87,694
33,513
stars
+-330+-241+2,784
87,694
forks
–
watchers
–
prs
–
issues
–
releases
–
discussions

README

!logo

 WandEnhancer





An open-source tool that extends the local client-side configuration of the Wand app and improves its UX.

 This project has no official downloads and no official video tutorials. GitHub releases contain notes only, never .exe files. Scammers use the project's name for fake tutorials and put malware or password stealers in the video descriptions. An executable or archive from a video, a website or a mirror did not come from this project, and we are not responsible for it. The official sources are this repository and its GitLab mirror. Look-alike forks and accounts are not ours.

 Features

- Local environment configuration management
- Automated compatibility adjustments for new client versions
- Layout and theme customization (client side only)
- AI features
- Remote web panel: control Wand from your phone

 Network and privacy

The patcher modifies files in the selected local Wand installation. By default it has no update check and no telemetry. Wand itself stays an online application. The optional remote web panel starts a LAN HTTP/WebSocket server and uses Wand API and CDN data, such as trainer translations and artwork.

An opt-in build variant checks GitHub's latest public release when Wand starts. That request exposes your IP and User-Agent, sends no Wand or account data, and never downloads an update.

 How to use

The project publishes no prebuilt executables. You build your own in your fork with GitHub Actions:

1. Fork this repository and click Sync fork before each build, so your fork has the latest fixes.
2. Open the Actions tab of your fork and enable workflows if GitHub asks.
3. Select the Build executable workflow and click Run workflow. Leave "Include GitHub release checks when Wand starts" off for a fully offline patcher, or turn it on to compile in new-version notifications.
4. When the run finishes, download the artifact from it and extract the zip.
5. Run WandEnhancer.exe. If your Wand install is not detected, drag its folder (or Wand.exe) onto the window.

Video walkthrough:

https://github.com/user-attachments/assets/7966cabe-0aa6-424d-8c2f-981ad91e0f91

You do not need a pull request to this repository to build your fork. master is the stable source. When you report a problem, give the workflow's source commit SHA and not only the version number: builds of one version can contain different fixes.

 Troubleshooting

Two causes account for most reports. Check them before opening an issue.

Pro or mods stop working after a day or two. Wand updates itself in the background, and the new version is not patched. Run Restore, then Patch again. To stop repeating this, enable Auto-apply after updates or Disable updates in the patch dialog.

Wand does not open, or patched files disappear. Patched Wand files are modified and unsigned, and the WandEnhancer.exe you build is unsigned and uncommon. Antivirus products and SmartScreen can flag both, even when the code was built from your own fork.

- SmartScreen on 

Snapshot: 2026-11-10T09:35:25Z · Data license Apache-2.0 · JSON