Release Healer Man 0.1.39

This commit is contained in:
phenom committed 2026-09-13 11:07:56 -04:00
1 parent b417b7c3c3
commit ed0d2fea3d
51 files changed
+17811 -49

No files matched your search

+117
View File
@@ -2762,3 +2762,120 @@ Vite's existing large-chunk advisory remains informational.
passed, along with the native vocation-import regression. The production
TypeScript/Vite build and release-bundle verification passed. The final
release candidate check includes the new tests and generated catalogs.
## RoM dungeon enemy durability — September 13, 2026
- Reproduced Barren Caves' low health with a RoM Priest and the four shipped
companions. Tested 108 combinations: 12 party seeds at levels 1, 2, 4, 8, 9,
20, 40, 70, and 80. The old fallback had 94 health at level 1 and 1,832 at
level 80; kills took 0–1.9 seconds from the first damaging NPC hit.
- Normal RoM dungeons now use a party-health baseline of
`1000 + 100 * enemyLevel + 8 * enemyLevel * enemyLevel`, with authored
creature/boss multipliers applied separately. This is explicit Healer Man
balancing because native RoM creature health tables are not packaged.
Barren Caves' Anglo retains his 7.5 multiplier and one-level advantage.
- Loaded RoM creatures receive the new health when the character levels up.
Re-registration preserves wounds as a health percentage and keeps corpses
dead. Enemy attack damage also rebases on a level change instead of retaining
its original low-level value. Regression checks cover these transitions.
- With the new health, the 108 isolated party-damage pulls lasted 3–17.5
seconds. A separate pull exercised actual enemy attacks and Priest healing
before the enemy died, with all companions surviving. These are opening
pulls with baseline equipment, rather than an audit of every geared build.
- Live PC check at 1280×720: created the offline Human Priest Barrenaudit and
entered Barren Caves as Healer. A level-1 Cave Sand Bug had 1,108 health.
At 10 seconds it still had 374 health, with 734 party damage on the meter.
The completed first fight showed 14 seconds and 1,108 total damage:
Morgha 370, Ilyen 369, Maerwen 289, and Cael 80. Urgent Heal then restored
Maerwen to 407/407 while the next pull was active. No browser errors were
captured during that bounded combat check.
- Concurrent navigation edits triggered development hot reloads around the
playtest; the captures above were taken during uninterrupted combat. This
check did not complete the dungeon or use physical Ayn Thor hardware.
Restored the original Hudtest roster selection, closed the test tab, and
stopped the temporary development servers.
- Evidence: `artifacts/rom-dungeon-health/report.json`,
`barren-caves-health.png`, `barren-caves-combat.png`, `barren-caves-healed.png`,
`live-combat-dom.txt`, and `browser-errors.json`.
- Validation: all 407 focused combat, party, CoA, RoM, DPS-meter, stat, and
dungeon-scaling tests passed across 52 files. The final production
TypeScript/Vite build and release-bundle verification passed.
## 2026-09-13 - WoW dungeon lighting and stair fleet pass
- Applied environment-specific readable lighting to all 54 WoW dungeon entries,
using the reviewed Stockades ambient/hemisphere fill as the baseline. Stone,
cavern, fire, arcane, crypt, and outdoor profiles preserve distinct coloration.
Stockades' existing presentation/three ramps and RuneWaker lighting are unchanged.
- Scanned every shipped WoW collision package, including authored Wailing
Caverns' actual source assets. Added 347 verified walking proxies across 22
other dungeons and eight filled navigation portal bridges in Uldaman. Rendered
steps and source visual/collision/navigation GLBs remain unchanged.
- Added package-identity gates and a compiler-independent shared runtime adapter.
Collision preparation spatially indexes flights; rejected candidates cannot
supply geometry needed by accepted proxies. Existing navigation validation,
content, encounter, and availability gates were not promoted to green.
- Shipping-asset regressions independently pass all 347 new proxies through
prepared collision and the live NPC segment validator uphill/downhill at the
center and two interior lateral lanes. Exact portal matching and all existing
Stockades player/NPC/wall tests pass.
- The game-playtest visual viewer uses shipped meshes and runtime lighting and
material policies without touching saved character/party state. At 1280x720,
Uldaman's old/new-fill comparison showed clearer stonework; Wailing Caverns
retained green, readable rock; Mechanar retained cool arcane interiors;
Scholomance's visible entrance steps/masonry remained intact and readable.
Blood Furnace's dark source textures remained visible at its wall-facing
entrance viewpoint. Durnholde's visual load completed without console errors.
- Zul'Farrak entrance/boss views and Durnholde's exterior boss view showed
geometry/terrain/viewpoint gaps, recorded for separate investigation. This is
not exhaustive staircase certification: curved/short/heavily-decimated flights,
rejected candidates, outer stair edges/landing lips, complete dungeon routes,
full clears, and physical Android QA still require individual review.
- Evidence/coverage: `dungeon-pipeline/WOW_ENVIRONMENT_REVIEW.md`,
`src/game/generated/wowDungeonStairs.generated.json`, and screenshots in
`artifacts/wow-dungeon-environment/`. No hosted release was published.
- Validation: 247 Vitest files passed, 1,599 tests passed, six existing tests
skipped. Production TypeScript/Vite build, texture/performance audits, bundle
compression/verification, and release candidate check passed. Existing physics
initialization and bundle-size/import advisories remain.
## 2026-09-13 - Dungeon completion results and run leaderboards
- Fixed missing RuneWaker completion bookkeeping for the 21 dungeons with
configured bosses. Barren Caves now awards Anglo's objective on his actual
death and announces the completed run. Bossless placeholder entries do not
fabricate a completion.
- Run timing starts when the dungeon is playable, survives wipes, pauses, and
saved resumes, and freezes at the final-boss objective. Older checkpoints
without a recorded start time still announce completion but remain unranked.
- The results dialog shows the final-boss time, final-clear and full-clear
placement, party classes/levels, and defeated bosses. Stay and loot, reopening
results, and Return to main menu were verified through the live UI. Returning
clears the completed checkpoint.
- Replaced the dungeon picker's minimap with persistent completion-time
leaderboards. Final Boss clears includes all qualifying runs; Full dungeon
clears requires every available boss for the selected difficulty. Expanded
entries show each party member and boss status. Normal/heroic rankings are
separate; disconnected results use an explicitly labeled device leaderboard.
- An actual combat integration check fought Barren Caves' level-2 Anglo with
9,240 health using NPC ability selection, enemy attacks, and Priest healing.
NPCs dealt 9,239 damage after a one-damage player tag; healing totaled 441.
The final death awarded completion at 84.1 seconds with all companions alive.
- Manual browser combat confirmed NPC damage and healing on Barren Caves
trash. The live results check restored the integration fight's completed
checkpoint through an isolated local QA account: 01:24.1 ranked #1 of three
seeded local-server entries in both filters. This was not a manual browser
full clear and no production leaderboard entries were published.
- PC results and expanded final/full leaderboard layouts were visually
reviewed at 1280x720. The built-in Thor preview displayed the leaderboard,
filters, and role-selection control within its 960x540 main surface. Compact
480x360 DOM bounds kept the dialog footer inside the viewport; the in-app
browser's viewport-override screenshot scaled incorrectly, so that capture
does not establish compact visual quality. Physical Thor hardware was not used.
- Evidence: `artifacts/dungeon-runs/combat-completion.json`, `results-world.png`,
`leaderboard-final-expanded.png`, `leaderboard-full-expanded.png`, and
`leaderboard-thor.png`. The bounded final browser check captured no errors.
- Validation: 70 completion, checkpoint, encounter, catalog, client, and UI
tests plus the real-combat integration test passed. The 432-test focused
combat/party/class/health/input regression suite and 18 server tests passed.
Production build, final TypeScript check, and release candidate check passed.