Detonate rifle grenades on impact with original Half-Life fireball

This commit is contained in:
enne2
2026-10-15 14:20:07 +02:00
parent ae32ad9615
commit 5761e160c1
12 changed files with 581 additions and 81 deletions
+22
View File
@@ -1,5 +1,27 @@
# Web build and compressed deployment
## Contact grenade / original Half-Life fireball: add7baaef2b022ef
First-impact detonation (floor, props, walls, enemies and glass), no old timed fuse;
original `zerogxplode.spr` converted to a portable additive PNG atlas (15 frames,
15 FPS), see `docs/GRENADES-WAVES.md`. Damage, blast radius and cooldown unchanged.
- PCK 4,420,396 bytes; total gzip payload 12,866,911 bytes.
- SHA256 verified on all 14 uploaded files; HTTPS-decoded PCK byte-identical to local.
- Atomic root swap; backup `/home/debian/zombie-fps-backups/index-before-impact-add7baaef2b022ef.html`.
- No nginx/API changes, no release deletion; previous `a961c96175bc644e` and older
`209fa6b154fea8df` retained (three release directories after this deploy).
- 24 grenade checks passed headless and with the real Compatibility renderer;
all 15 Godot suites plus the 42-check API suite passed in their appropriate drivers.
`test_start_screen` needs a real display (headless dummy misses its GUI click).
- Captured five original fireball frames after a real floor impact in the office.
Exported Web build booted in Firefox/WebGL2 and touch grenade launch worked on
loopback (no production score submissions). Loopback has no score API, so its
HTTP 404/501 and JSON parse errors on death are expected test-environment limitations.
- Live root, PCK, WASM and API health verified; versioned WASM retains correct MIME
and immutable/Vary headers. Browser production check stays at the menu to avoid
recording test games in the global leaderboard.
## Global high scores release: a961c96175bc644e
Start screen with global leaderboard, player name and score submission; new score API