Stockade Weapon Utilities Playtest — 2026-10-05

Outcome

Two normal offline Bite-Sized Stockade / Cellblock Rush runs completed with a level-30 Discipline Priest profile and four Ready NPC companions. Each run seeded and defeated exactly one real Stockade boss through ordinary UI play. The same frozen build and content snapshot were used both times. The first run's boss clear is valid, but its live weapon telemetry was lost in the route-sample projection; one corrected run was performed and retained as a separate run record. No further gameplay run was made.

Both runs used build SHA-256 58dfe50765b0635caeae50bd3eca2fd079cd69cce0e571ff6cb2dd5aeec77b39 and content-manifest SHA-256 36614a23f3b98b4289bc3726c8a9bdb075445ada50dfce6504ade4e36325be1f. The before/after build and content hashes matched on both runs. Each run served and verified 2,124 manifest-referenced hash-addressed content objects, with zero integrity failures and no page errors. Parent audit also confirmed the frozen inputs and sampled assets were unchanged.

Run	Seeded boss	Native result	Player effective healing	Deaths
`20261006-012123000`	Hamhock, entry 1717, actor `creature-79098`	1/1 clear, 03:14.6	3,057.6	0 player, 0 party
`20261006-013934624`	Bazil Thredd, entry 1716, actor `creature-79124`	1/1 clear, 03:20.7	1,504.5	0 player, 0 party

The route result is recorded in each run's run-record.json, including the visible native dungeon-results text and required boss ID. The boss-arrival.png capture also shows the post-clear results panel with the single boss marked defeated.

Corrected live telemetry

The corrected run retained 328 source NPC snapshots and 764 sampled combat events. Each mob snapshot now carries dualWieldEnabled, nextEnemyOffhandAttackAt, pendingExtraAttacks, and lastDamagedActorId through to the final route evidence. Bazil Thredd's dualWieldEnabled was true in 35 samples. No sampled mob had a positive offhand timer: all 328 nextEnemyOffhandAttackAt values were zero. No nonempty pending-extra-attack queue, non-null lastDamagedActorId, or non-null attackHand on source attack definitions or retained combat events was observed. These are ordinary snapshots, so short-lived states or events may fall between polls.

The captured run's original summary field samplesWithOffhandSchedule counted 328 non-null timer fields, including zero. It must not be read as 328 scheduled attacks. The raw rows show 328 zero values and zero positive timers. The harness counter has since been corrected to report timer-field presence separately from positive scheduled timestamps; this source-only counter fix was syntax/preparation checked and was not used to run another dungeon.

Global combat-store telemetry captured 26 snapshots of the Disease aura Infected Wound on the party tank. All snapshots share one stable aura instance and one stack. Four distinct source/application/expiry tuples were observed, each with a 300,000 ms duration:

creature-79035, applied at 1791250853253
creature-79042, applied at 1791250872255
creature-79065, applied at 1791250898558
creature-79062, applied at 1791250928053

No active aura snapshots for Bloodlust (6742) or Disarm (6713) were recorded. The first run's Hamhock checkpoint had smart-1717-2-bloodlust: 1 in its ability-cast counter while unengaged; that counter alone does not prove the aura landed. No live outcome claim is made for Bloodlust, Disarm, or Thrash. Aura snapshots and combat events are sampled, so zero observations cannot establish that an effect never occurred.

First-run telemetry limitation

The first run's route result contains 327 source NPC samples, but a later sample-projection whitelist dropped all four requested weapon fields. Its 327 null summaries describe the harness projection gap, not evidence that the runtime lacked weapon state. That run also filtered global aura telemetry to older unrelated IDs, so it cannot establish whether the new utility auras reached party targets. The first run's raw route and screenshots were preserved without rewriting; the corrected run above supplies the usable measurements.

The second run's mob route samples and global source-aura snapshots are available in playtest-artifacts/stockade-weapon-utilities/20261006-013934624/weapon-utilities-evidence.json and campaign/final-build-20261006-013937115/bite-sized-stormwind-stockade-campaign-boss-route.json. The first run's matching artifacts remain under playtest-artifacts/stockade-weapon-utilities/20261006-012123000/.

Screenshots

Both runs saved the Priest roster preview, compact roster preview, campaign picker, dungeon entrance, equipped party silhouettes, three route checkpoints, and a results capture named boss-arrival.png. The player robe/shoulders/staff and several companion bodies with staff/club/shield silhouettes are visible in the route captures. Party clustering and overlap prevent a complete per-companion gear audit from these screenshots.

Corrected run captures:

The same capture set is in playtest-artifacts/stockade-weapon-utilities/20261006-012123000/campaign/final-build-20261006-012126038/. Parent review found the player and party silhouettes visible there as well, with the same overlap limit.

Scope and cleanup

The harness used normal UI character creation, dungeon selection, movement, targeting, attacks, support healing, and party commands. It did not use Boss Testing, teleports, collision bypass, combat-state writes, manual aura or health seeding, loot claims, or readiness promotion. The corrected run exited successfully; the wrapper's cleanup path closed its browser and server and removed its generated temporary campaign wrapper.

After this run, only the new harness and this report were updated. The post-run counter change affects future evidence summaries only; no gameplay state, build, content snapshot, or prior run evidence was modified.

7.5 KiB Raw Permalink Blame History