Skip to content

Installing

Requirements

Install

  1. Unpack the release into a folder you can write to (not Program Files — clockwork writes config and route files next to itself).
  2. Start EverQuest II.
  3. Run eq2loader.exe.

The loader finds the running client, injects eq2core.dll, and exits. The core brings itself up on the client's first rendered frame.

Verifying the install

Check Expected
Press End The clockwork overlay appears over the game.
Type /lua list in chat clockwork answers with the running script count.
Type /console The overlay toggles.

If the overlay never appears, the DX11 present hook didn't install. If the overlay appears but /lua is silent, the RunInputLine hook didn't resolve. Both cases are logged.

Unloading

clockwork is hot-unloadable — the core tears its own hooks down and unmaps without restarting the game client. Use the loader's unload option rather than killing the client.

After a game patch

clockwork resolves every game function and global from a byte-pattern signature at runtime, never from a hard-coded address, so a client patch that only shifts code around is survivable. A patch that changes the matched code will fail that one signature, and the feature depending on it disables itself with a log line. Check the signature inspector tab in the overlay to see what resolved.

Multiple clients

Every injected client registers itself in a shared participant table, which is what /dga and /dge broadcast across. Nothing extra to configure — inject into each client and they find each other. The overlay's Multibox tab picks which clients are selected as broadcast targets.

Peers on the same physical machine are discovered at the host's LAN address, not 127.0.0.1.