Blood II current browser world and controls, 2026-11-18

Registered blood2_demo, owner-designated DEMO V1.0A BUILD109, reached its original first-person world through ordinary menus and loading. Forward movement, turning and firing have visible consequences on normal browser guest Workers, slice100000, with music, chaining, uops and guest features unchanged. Enemy damage/kill and ordinary game Quit remain unverified. Quit reaches the promotional card, then worker4 traps during final teardown. No engine or music repair is claimed.

Evidence: scratch/runs/20261118-blood2-current-browser-world-combat/ (final result.json). The tested immutable published source is 7741a4cfda8a260690370a2c37a1197ef3b119a7; every observed guest Worker module hashes to 3e2030df3d6f53e2ca0ffee2a6822278e691374f7e997801785de7d3310c5994. All99 original media pins match unchanged, with HTTP availability checked before guest launch. The multi-GB compilation was not downloaded. Foreign shared-tree overlays were excluded from serving. Subsequent pulled commits are not covered by these runtime claims.

Concrete helper repairs and preparation

The first original scope stopped before guest creation because the server admitted only the shortened binaries/ alias while the registered app requested test/binaries/. The helper now maps both names to the exact pinned file. The next original rendered the complete BUILD109 menu but the helper erroneously waited for an initialized GPU presentation before admitting a DirectDraw menu. Stable process/module/main Worker/window identity now remains mandatory across normal menu-to-world backend creation; the actual backend is recorded separately. The affected original3 then completed the ordinary menu/start/control route. Neither fix changes guest rendering or settings.

Focused oldfail/newpass tests cover media aliases, stable core versus legitimate renderer birth, replacement/missing identity rejection, exact matching key/code pairs (including A/KeyA, S/KeyS and Control/ControlLeft), delayed prearm before a finite release lease, and expired-lease NOT_SENT with release completion. An authored browser fixture calibrated focus, visible key consequences, independent releases/passive physical neutral and ordinary ExitProcess0 before the affected original. The earlier calibration2 transport UNKNOWN is closed and was not queried again. Other calibration admission failures are retained separately.

Preparation fixed transport15s, capture/encode3s, review90s, release prearm30s followed by a finite5s lease, runtime20min and Quit reserve4min. Prearm is outside the lease clock; no lease was relaxed in flight. An independent release child was armed before each DOWN. Every original3 gesture records transport completion, matching UP, passive physical state0 and actual child wait/EOF. CDP completion is only transport; no invented native consumption ACK was required or claimed. Finite native supervision, independent disk watchdog, display waits and capture-count bounds were set before launch.

Original consequences

Selected whole private-display PNGs in original3/ retain the route: whole-main-menu.png, Caleb and Homicide menus, level-loading.png, then loading-progress.png (despite its filename, this is the first-person world: elevator, pistol, corridor/crates, health100/ammo50). There are exactly three startup Enter gestures, not a fourth loading bypass.

after-forward.png follows ArrowUp800ms and shows the player outside the elevator with a changed viewpoint and an armed humanoid visible at the doorway. aimed-enemy.png, after a left turn, instead shows the player dead at health0; this happened before firing. Player death is observed, but the exact killing actor is not separately established. It does not prove damage to an enemy.

Ordinary Escape/menu/Caleb/Homicide restarts the same process. restart-world.png shows health100/ammo50. ControlLeft800ms produces after-fire.png, health100/ammo49, establishing firing/ammo expenditure. No enemy hit or muzzle flash is asserted from that frame. ArrowLeft100ms produces the substantially rotated elevator-aim-left.png, establishing causal turning. Initial startup-image review wording was corrected immediately in review-correction.json; that turquoise frame was not the game menu and authorized only a visible runtime-log checkbox click. Subsequent game DOWNs use personally reviewed complete game scenes.

Actual browser identity is retained in owner/worker pins, source inventory, backend observations and actual-backend-restart.json. Five guest Workers use the same module; nonzero uop counters and slice100000 are recorded. The initialized d3dim-gps bridge reports selected WebGL, render Worker, ANGLE Intel/Mesa and webgl1 device, but its sampled counters show only two LAYOUT records and zero draws/presents. That sample establishes initialized backend identity, not GPU authorship of the world pixels. The selected whole PNGs establish visible world rendering independently. No diagnostic native-watch result is relabeled as default-runtime proof.

Quit fault and bounded next cause

Escape returns to the main menu, ArrowUp visibly selects Quit (quit-selected.png), and Enter reaches the Prime Gibs promotional card (quit-promo.png). Escape dismisses that reviewed card. Its independent UP completes at1794989695296 with physical state0. Three application threads return normally; at1794989695903.902 worker4 traps unreachable at EIP0xc06edb, prev2=0xc06ef1, ESP0x7ecfffe0 within its stack. Its saved frame is return0x7505a48, timerID1, message0, user0xb1b554, zero, zero. This closes the run immediately; no later runtime inspection or input replay follows. A later independent root capture fails because its owned display is already closed.

Offline published source establishes that 0x7505a48 lies in the fixed continuation-thunk range, and the multimedia timer worker pushes that six-word callback frame. The log's d3d.ren+... / imrt25.dll+... labels select the nearest lower module base without checking size; they are not valid image ownership evidence. The pinned AM18.dll has a periodic timer registration using its this object and callback RVA0x11edb; that callback checks timer ID at this+0xb8 and returns ret20 at RVA0x11ef1. Subtracting the historical module-layout difference0x100000 aligns both callback PCs and the actual IMUSIC thread entries. This makes AM18 periodic callback teardown the concrete bounded next cause, explicitly an inference: this run did not retain the current occupied AM18 row or fault-time bytes.

offline-cause.json and am18-timer-candidate.asm preserve the distinction. Actual timer creation/kill/selection ordering, object final Release/free, occupied module generation, detach/retirement and code/decode validity at fault are still missing. The evidence does not select a safe engine fix or establish the old IMRT primary-object invalidation. No silent stub, fake handle, guessed reference repair, music disable, INI/registry/guest patch, synthetic polling/focus/clock, crash suppression or new diagnostic replay is used.

Waits, recovery and limits

All eight native scopes are closed. Original3 native-supervise records exit1 and leaked:false; browser exits0, Openbox/Xvfb exit0, all actual waits have stdout/stderr EOF. Each independent release has its own actual wait and both EOFs. Disk watchdog completes with minimum2255282176 bytes, above1.5GB. These host cleanup facts do not prove game Quit. The enclosing launcher wait JSON is absent for calibration5 and original3; the tool observes exit143, with outer EOF unestablished. Board watcher likewise returns143. No complete outer-cleanup claim fills these gaps.

Exact Git/source/module/media identities, relevant excluded-overlay binary patch, own new-file patches, later shared-build binary comparison, recovery instructions, command/review/release receipts, actual native/browser/display waits and selected named whole PNGs are retained. No source-tree archive, capture bundle, media copy or frame series is retained. Focused test and locked-build results are indexed in the final result; the intermediate build refused the active foreign UT lifetime review and did not authorize publication. No public deployment, agents/workers/boxes, Python or Wine were used. Box ID null; state NOT_CREATED; expiry null; stop receipt null.