roadcraftEMU

RoadCraft work across three repositories: client evidence, an observe/forward proxy, and a local C++ state service.

overview

ANALYZE holds client and transport evidence. REDIRECTOR supplies a version.dll proxy and an application-local observer; provider hooks record selected state metadata and forward calls to the original functions. WinHTTP observation is limited to WinHttpConnect and WinHttpOpenRequest metadata. SERVER contains a local control service and match-session registry, not the game's backend protocol. Endpoint redirection and provider emulation remain disabled by default.

in the repository

• Client and transport evidence in ANALYZE
• version.dll proxy with app-local provider observation
• WinHTTP connection/request metadata only
• Local control service with match-session create, search, join, and leave
• Provider calls forwarded; endpoint redirection remains disabled

current work

Tests exercise proxy startup, callback/configuration paths, and local match-session create/search/join/leave state. They do not show a RoadCraft backend response or an in-game matchmaking session. WinHTTP observation does not capture headers or bodies, and endpoint redirection remains off.

change history

• 2026-10-03 · roadcraftEMU · developmentWinHTTP observation restricted to metadata APIs REF 2ebd2d8

  The REDIRECTOR policy permits observation only for WinHttpConnect and WinHttpOpenRequest. Request and response bodies and headers remain outside the observer; the hooks are off by default and endpoint redirection remains disabled.