Local engine & GUI

The engine is a single program that serves the game UI in your browser and stores your collection locally. You do not need a website account to play.

Prefer hands-off setup? Give an AI agent the local-play prompt.

1. Get the right build

Choose your operating system and CPU on Downloads. Android has a standalone APK with the engine built in. Desktop and Pi releases are executables that open a local browser interface.

2. Start the engine

Example for Linux x64. Keep the database outside the executable directory:

mkdir -p "$HOME/.local/bin" "$HOME/.local/share/wavebeast"
curl -fL https://github.com/chvolk/wavebeast-dl/releases/latest/download/wavebeast-linux-amd64 -o "$HOME/.local/bin/wavebeast"
chmod +x "$HOME/.local/bin/wavebeast"
"$HOME/.local/bin/wavebeast" -addr 127.0.0.1:8777 -db "$HOME/.local/share/wavebeast/wavebeast.db"

On Windows, download the EXE, create a data directory, and run it in PowerShell:

New-Item -ItemType Directory -Force "$env:LOCALAPPDATA\WaveBeast"
.\wavebeast-windows-amd64.exe -addr 127.0.0.1:8777 -db "$env:LOCALAPPDATA\WaveBeast\wavebeast.db"

On macOS, use the matching macOS binary, make it executable, and choose a database path under your user’s Application Support directory. The same -addr and -db flags apply.

3. Open and verify

Visit http://127.0.0.1:8777/ on that device. /capabilities should return JSON with engine: wavebeast. Enter a real code or use available sensors, then Sweep.

The engine must stay running while you use the GUI. Stop it with Ctrl+C. Restart with the same database path to keep your collection. Local beasts start each battle at full battle HP; the online account has a separate persistent health pool.

Local vs linked play

The World tab optionally links a node code from your online account. It displays your account details and lets you submit snapshots. Linking does not merge your local and online wallets. See listener nodes and Free & Premium for online features.