Userscript · MIT · read-only
One install button adds an Addons entry to the game menu. Browse a built-in marketplace, install an addon, configure it, all inside the game, with nothing about the game itself modified.
It runs as a userscript. It reads only what the game already hands the browser, and it never plays for you.
Needs Tampermonkey or Violentmonkey. Three minutes, mostly waiting on the store.
Combat Meter · 1.0.0
A row per ability with crit rate, average and biggest hit, plus your real miss, dodge and parry rates and what is hitting you back.
The game has its own meter. This answers what that one does not.
Cooldown Bars (Example) · 1.0.0
A draining bar for every ability you have on cooldown, with an exact bar for anything regenerating a charge.
Also the example addon: one file, no build step. It is what authors copy.
The whole install
No launcher, no account, nothing to keep running. The loader waits for the HUD to exist and adds one button to the menu you already use.
Dev Harness ships too: it exercises every API surface and reports what it found, so authors can check a change in the game rather than only in a test.
Before you install anything
Addon code runs in the game page and can read anything the page can, including your session
token. The woc API is an ergonomic surface, not a security boundary.
Ships with the loader, cannot be removed, and its contents are reviewed. It is the same repository as the loader itself.
You may add your own. Doing so means trusting whoever maintains it with your account. The loader says so at that moment, not afterwards.
No send API, no synthetic input, no automation of play. Addons reformat information you already have. This is a boundary, not a missing feature.
The loader shows what the addon declares. Read the declaration and the caveat under it together: they are one statement.
The declared list is what the author says the addon is for, not a limit the loader enforces.
No game source is modified and no build is forked. The loader reaches the game only through surfaces a browser already gets:
window.__gamethe global the game already exposesWebSocketobserved, never written toHUD DOM idswhere panels anchor themselvesaudio packfor addon sounds that match the gameA folder, a JSON manifest, one plain JavaScript file. No bundler, no toolchain, no framework.
const win = woc.ui.frame({
id: 'main',
title: 'My Addon',
save: true,
});
woc.net.onEvent('damage', (event) => {
win.body.textContent = String(event.amount);
});
woc.keys.bind('toggle', () => {
win.toggle();
woc.sound.play('ui_click');
});