Extension API
The addon contract (get_init_addr / get_release_addr), the combat
callback, arcdps_exports, and the extension registry — plus a
field-tested practice guide.
arcdps ships as a d3d11.dll proxy that GW2 loads in place of the real
Direct3D 11 library; it forwards the real D3D calls through while adding a
combat-log overlay and, most importantly for developers, an extension
surface. Once loaded, arcdps exposes a small export table that other DLLs
(arcdps_*.dll extension modules) can hook into — most notably a combat
event callback and a handful of helper exports (e0, e3, e5–e10;
e4 is present in the export table but not documented by the official
notes) for things like reading the INI path, writing to the arcdps log,
and drawing into arcdps’ own UI. Everything on this site describes that
surface: the
addon lifecycle, the structs passed across it, and the raw exports on the
DLL itself.
Extension API
The addon contract (get_init_addr / get_release_addr), the combat
callback, arcdps_exports, and the extension registry — plus a
field-tested practice guide.
EVTC log format
A full binary spec of .evtc/.zevtc logs — header, agent and
skill tables, event stream, and the standard parsing recipe.
Enums & payloads
Every enum value, and the complete per-statechange payload mapping with evtc/realtime availability.
Guides
Installation, files & settings, the tool ecosystem, and the Unofficial Extras API.