Native control, inspection, UI automation and evidence capture for a running Witcher 3 process.
README.md

Game-side bridge sources #

The bridge concatenates these WitcherScript templates in order:

  1. bridge.ws.in — session identity, dispatch, lifecycle and bounded input.
  2. observations.ws.in — native state, event and water observations.
  3. encounters.ws.in — disposable encounter operations.
  4. request_algorithm.ws.in — explicitly bounded Approach observation/intervention.
  5. crossbow.ws.in — crossbow input boundary.
  6. overlay.ws.in — passive in-game annotation state and rendering calls.
Ordered script templatesBuild hash and@@BUILD@@replacementOwned PathDevkit.wsGame-backed compile andcold restart

../witcher_devkit/support.py owns the concatenation order. A host hash or source-only test does not establish that WitcherScript compiles or the HUD renders. Build/deploy only against the hash-owned installation with the game closed; keep consumer memory and combat policy in the consumer repository.