witcher3-devkit
Native control, inspection, UI automation and evidence capture for a running Witcher 3 process.
mod witcher3
Star 0
Fork 0
Watch
witcher3-devkit docs ARCHITECTURE.md
1.4 kB · 29 lines
Markdown
at main

Architecture #

AgentCLI or Python clientSingle debugger ownerDurable operation journalREDengine loopbacktransportInstalled WitcherScriptbridgeGame state and inputhandlersSmall native adaptersPassive game HUD

The debugger writes an intent before dispatch, allows one operation at a time, and preserves uncertain native delivery. A client timeout ends the wait, not necessarily the operation. A finite step reports input delivery, observed ticks, release and paused boundary separately from gameplay effect. The host's CLI contracts (w3dev help COMMAND --json) specify current preconditions and bounds.

The Python package owns CLI, transport, owner and evidence logic. The ordered game scripts are compiled into one owned bridge; native adapters supply the few missing low-level primitives. Offline tests and explicit live harnesses have separate entry points and evidence claims.

Native adapters, UI asset build tools and receipts are installation-specific. This source snapshot omits local game assets, generated bundles and private session/evidence history. It is not a general first-time installer.