ok-ww: background automation for Wuthering Waves, judged on its own terms

What ok-ww automates, and who the README is written for

The project describes itself as an image-recognition-based automation tool for Wuthering Waves with background mode support, developed on top of ok-script. The stated mechanism is Windows API input simulation: the README says there is no memory reading and no file modification. That distinction matters if you are evaluating it against injection-based tools, because it means ok-ww drives the game the way a second keyboard and mouse would, by looking at the screen and pressing keys.

The feature list is short and concrete. It supports 16:9 resolutions up to 4K with a 1280x720 floor, with partial support for ultrawide ratios such as 21:9. Background mode lets it keep working when the game window is minimized or covered. Character skills are recognized automatically rather than configured per character. It can mute the game while running in the background.

The audience is Windows players who want daily chores and echo farming done without watching. The README is candid that this is not a sanctioned tool. It quotes Kuro Games' fair play statement, which names macro scripts and auto-idling among prohibited behaviours and lists penalties including frozen or permanently banned accounts. Anyone deciding to install ok-ww should read that section before the quick start, not after.

How the image-recognition loop actually works

The architecture follows the ok-script pattern: capture the game window, run the frame through OCR and vision models, decide on an action, then dispatch synthetic input through Windows interfaces. The dependency list confirms the pieces. opencv-python handles frame processing, openvino runs inference, and onnxocr-ppocrv5 supplies the OCR model. pydirectinput and pynput are the input layers, and pywin32 plus comtypes and pycaw give access to Windows-level window and audio control, which is how the auto-mute feature works.

Because decisions come from pixels, the troubleshooting section reads like a list of ways to keep those pixels predictable. The README asks users not to enable GPU filters such as NVIDIA Digital Vibrance or AMD sharpening, to keep the game's default brightness, and to disable overlays that draw frame rates on top of the game, naming MSI Afterburner and Fraps. Any of those changes the image the models see.

The dependency on visual input also explains the 60 FPS requirement. If the frame rate is unstable, the state machine can misread what is on screen. Note that the package metadata pins ok-script at 2.0.7b1, a beta version, and the build uses Cython to compile .pyx extensions from src/. That is a real build-time dependency, not a packaging detail you can ignore if you intend to run from source.

Installing ok-ww on Windows and running a first task

The README's quick start is three steps: download the latest ok-ww-win32-China-setup.exe from the releases page, run the installer, then launch ok-ww from the desktop shortcut or Start menu. The download section warns explicitly to take the setup.exe installer rather than the Source Code archive. Mirrors are listed for users in China, including Mirror酱, Baidu Netdisk and Quark Netdisk, and the Mirror酱 route may require purchasing a CD-KEY on that platform.

After installation, the troubleshooting list is worth walking through once. Add the install directory to your antivirus whitelist, including Windows Defender. Confirm the game runs at a stable 60 FPS. If you remapped keys in game, mirror those bindings in ok-ww's settings, since only the keys listed there are supported.

For developers, the README gives a source route. It recommends Python 3.12, requires 3.9 or above, and notes other versions are not fully tested. From a checkout, install the pinned dependencies and launch the release entry point. The debug entry point is separate and is what the developers ask contributors to use before joining the developer group.

pip install -r requirements.txt --upgrade

python main.py

python main_debug.py

requirements.txt is generated by pip-compile against pyproject.toml, so the versions it pins are the ones the maintainers build against. Running python main.py starts the release build; python main_debug.py starts the debug build.

Command-line automation for scheduled runs

ok-ww can start a task and exit when it finishes, which is the useful shape for scheduling. The README gives this example, where -t selects the Nth task in the list and -e exits after completion.

ok-ww.exe -t 1 -e

Task 1 is the first entry in the task list, which the README calls the one-dragon (一条龙) run. With -e added, the process terminates itself once that task completes, so the command can be dropped into a scheduler without a separate cleanup step.

Where ok-ww breaks, and when it is the wrong tool

The most specific failure mode in the README is also the easiest to miss: every character in the party must have a main echo equipped, and the echo skill icon should be visible in the lower right of the screen. If any character lacks one, the README states that auto combat will not work properly and may repeatedly lock onto enemies without attacking. That is a silent-looking failure caused by a loadout mistake, not a bug.

A second hard constraint is the key binding sync. If you changed in-game controls and did not mirror them in ok-ww's settings, input will go to the wrong actions, and only the keys listed in the settings are supported at all.

The OpenVINO error 0x000005 on Intel CPUs with an NPU is documented with a fix: update to Intel's latest NPU driver. Disconnection issues have a documented workaround as well, enabling the option to close the launcher after startup so the launcher process is not running, or running from source instead.

If none of that appeals, ok-ww is the wrong tool. It is Windows-only, it demands a stable 60 FPS and a clean visual environment, and the README itself reproduces the publisher's warning that macro scripts and auto-idling fall under prohibited behaviour. Players who care about account longevity over daily convenience should stop here.

ok-ww versus ok-genshin-impact and the rest of the ok-script family

The closest alternative is not a different automation stack but a sibling project. ok-ww is one of several tools built on ok-script, and the README lists them: ok-genshin-impact for Genshin Impact, ok-gf2 for Girls' Frontline 2, ok-starrailassistant for Honkai: Star Rail, ok-star-resonance, ok-duet-night-abyss, and ok-baijing. The difference between them is the game they target and the state machines their authors wrote for it, not the underlying approach. All of them share the same image-recognition and input-simulation model.

The interesting comparison is maintenance. The README marks ok-genshin-impact as stopped maintenance, noting that background story progression still works, and ok-baijing as no longer updated. ok-ww, by contrast, had its last push on 2026-09-19 and shipped v3.6.7 on 2026-09-06. In a family where several siblings have gone dormant, that is the practical signal: if you pick a game from this list, check whether its tool is still receiving releases before you build a routine around it.

If you want a different approach entirely, you would be looking at tools that read game memory rather than the screen. ok-ww's README positions itself against that category by stating it does no memory reading and no file modification. Whether that distinction changes your risk calculus is a judgement call the project leaves to you.

Licence, upgrade cost and what AGPL-3.0 means here

The repository is licensed AGPL-3.0. The practical consequence for anyone modifying ok-ww and offering it to others over a network is the copyleft obligation that licence carries, which is a different posture from the permissive MIT licence declared in setup.py's classifiers. That classifier is inconsistent with the repository's LICENSE.txt, and it is worth treating the LICENSE.txt as authoritative. This is not legal advice; if you plan to redistribute a modified build, get your own reading.

The upgrade cost is low for end users. Releases arrive on a roughly two-week cadence based on the dates of v3.6.6, v3.6.7-beta.2 and v3.6.7, and the installer is the supported path. The README's own advice is to check that you are on the latest version before reporting a problem, which implies the maintainers expect version drift to be a common cause of breakage. Beta releases such as v3.6.7-beta.2 exist, so you can choose whether to ride the beta channel.

For source users, the cost is higher. Dependencies are pinned through pip-compile, ok-script is pinned to a beta version, and setup.py compiles Cython extensions from src/, so a Python upgrade or a dependency bump can require build work. Budget for that if you run from source rather than the installer.

Editorial conclusion

ok-ww suits Windows players who already run Wuthering Waves at a stable 60 FPS and want repeatable daily chores handled without babysitting the window. It is the wrong tool for anyone unwilling to accept the account risk the README itself quotes from Kuro Games' fair play statement, and for anyone on Linux or macOS, since the project is Windows-only. Before adopting it, verify the two conditions the README calls out as hard requirements: every character in the party has a main echo equipped, and your in-game key bindings match what you configure in ok-ww.

Frequently asked questions

Official sources

1. License: AGPL-3.0
2. ok-oldking/ok-wuthering-waves on GitHub
3. Project website
4. README
5. Releases