Files
Patryk GenschandClaude Opus 5.5 e03037647e data: extract 33 scene modules and the Wojna Trojańska engine (68 builds)
The DLL collection gains every WORLD/KOLOROWANKA variant, MATRIX, QMAN
(TEST), INERTIA and BOARD, plus the later PIKLIB72 build from Wojna
Trojańska, taken from the game discs. All 68 builds re-extracted; engine
snapshots are unchanged except the Piklib 6.1 switch dispatch. Roadmap,
batch results and docs follow.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 21:38:11 +01:00

4.0 KiB
Raw Permalink Blame History

Kolorowanka pilot — bounded static surface extraction

Target: /Users/genszu/Reksio/Herkules + Odyseusz/Odyseusz/Kolorowanka.dll. SHA-256: 7f26356f30f283f7697c9b430fadc68e3932b124dd099d4affd4dc3a21d8e06e. Provider: REA with Ghidra 12.1.2, x86 PE, default analysis. No target code executed.

Artifacts: snapshots/kolorowanka.snapshot.json (AMS schema 4 with provenance extensions), snapshots/kolorowanka.evidence.json (18 complete evidence records).

Established surface

The plugin factory at VA 0x1000a820 compares TYPE with KOLOROWANKA, allocates 0xfc bytes and calls 0x100035d0. The latter creates its runner via 0x1000b1c0; that constructor installs vtable 0x10010c1c. Vtable slot +0x28 points to registration routine 0x1000b200.

The registration routine calls the base CMC_Runner::prepareMthHashSet, then constructs CInteger IDs and CStringHashCode names and inserts them via CHashtable::put. Its 23 explicit registrations are recorded with method IDs, string VAs and the address of each ID PUSH instruction. All 23 ID values were checked against assembly, not inferred from list order. Names were recovered from the registration pseudocode and cross-linked to string operand addresses. Method owner and runner labels are synthetic labels for the observed KOLOROWANKA construction chain; original C++ class spelling remains unknown.

IDs 1–23: LOAD, SETPOSITION, MOVE, SETCOLOR, FLUSH, SHOW, HIDE, ENABLE, DISABLE, CLEAR, APPLYANNSEQ, APPLYSNDSEQ, STOPWAV, PRINT, GETLATESTWAV, GETFIELDNAME, LOADSTATE, SAVESTATE, DRAW, GETCURRENTCOLOUR, SETPATTERN, SETDEFCOLOR, GETENDCOLOR.

Evidence anchors

  • Registration pseudocode: ev_aeb62723f834068c3c02cfbc35a6e47a05bb9d53a88922d2cbf1d91349a8c353.
  • Complete registration assembly: ev_26ce096869cd21ca415ffe44d1fd337db7bbc93b64e4b08c41cf7e222f26e63e.
  • Object constructor: ev_0c36b49ccf457c15f803a650826790164dc4dcb02f19ba3da05450786789fb7f.
  • Runner constructor: ev_46cfab66dd3dcc9bf902a8ae52c445da16d225d30c8084d08d5b513f32fa428c.
  • Runner vtable bytes: ev_edc8f35dba4956477de0225d0ce0c19e13dbfb1671b25202130e5c34502463e3.
  • Type literal: ev_15fdba5dc76642a47e3771a83a549a4912ca994072bbfbee48f2c9acc1b76fa8.

All VAs use preferred image base 0x10000000; RVA = VA minus image base. Evidence bundle retains the original provider limitations and source digest.

Limits and next extraction work

This is partial extraction, not proof of complete DLL API or behavioral correctness. Base runner methods are not expanded. Empty fields/events/dispatch arrays mean unextracted, not absent. No emulator implementation has been certified by this analysis. Ghidra default string inventory missed short names and reported STOPWAV as TOPWAV because of its string-object boundary; registration references recover the correct spelling. Therefore string inventory alone is not a safe method extractor.

The candidate runner dispatch pointer at vtable +0x44 is 0x1000c950, but Ghidra default analysis did not recognize it as a function (ev_b935c945474b0e6ab5b710736af786e94ed5bceb5a27d7898bf1a09ec16ac0ab). Recovering that function and its cases is a follow-up, requiring function creation or a targeted headless script. We deliberately leave method_dispatch empty rather than making guessed case mappings.

Automation strategy: detect module factories through TYPE comparison and construction, follow object -> runner constructor -> vtable, then extract CInteger/hash registrations with direct assembly cross-checks. A generalized plugin extractor should use Ghidra references/P-code, not regex over uppercase string inventory. This pilot snapshot was assembled from the retained evidence and validated with AMS Snapshot.load.

REA session was closed after exporting evidence.

Automatic extraction (2026-10-28)

The batch (ams.acquire.batch, the scene-module path of extract_engine_surface.py) now extracts every variant of this module. On this binary it yields the same 23 name/ID pairs as the REA analysis above, plus dispatch with signatures and per-type events and fields. In the tracker the batch result takes precedence over this snapshot.