•Using mobile data or a different network? If you want to use the panel over mobile data (LTE/5G) or from an entirely different network, you can use Tailscale or similar VPN tools.
•The panel protocol does not include your Wand bearer token or installation-path fields.
•You do not need to open a pull request to this repository to build your fork.
•Record the workflow's source commit SHA, not just 2.0.0.0: the RC tag, RC branch and a local build may contain different fixes.
•In the patch dialog, add one or more .js files (only existing .js files are accepted), or
•Drop .js files into a renderer-scripts/ folder placed next to the patcher executable.
•Each script runs inside Wand's renderer (full DOM access, plus Node require).
•It is wrapped so a thrown error is logged and never crashes Wand.
•It may run more than once per launch (on load and again shortly after), so guard one‑time work behind a global flag.
•A small WandEnhancer helper is available: WandEnhancer.log(...), WandEnhancer.remoteUrl, WandEnhancer.apiVersion.