orbit/.pi/goals/archived/goal_2026091623080422_mu4xe...

121 lines
13 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

{
"version": 3,
"id": "mu4xefwj-ebnq8h",
"objective": "=== Goal ===\nObjective: A visual overhaul of combat FX in Orbit — visually impressive laser bolts from both the player and enemies, a strong impact read when enemies are hit, and a shield-sphere hit effect that shows the player's shield struck from the laser's incoming bearing with the hit region highlighted — delivered consistently in both combat contexts (the /combat range and the main game's ?combat boot).\n\nSuccess criteria:\n- Player and enemy shots render as elongated glowing bolts: hot-white core, colored halo (cyan player / magenta enemy), a fading motion trail along the flight axis, and a directional muzzle flash on fire — in BOTH the range (js/combat/CombatScene.js) and the main game (js/combat/CombatSystem.js).\n- Enemy hits show impact: a hot core flash at the point of impact, directional sparks along the bullet's travel vector, a visible white hit-flash on the enemy craft, a cyan arc ripple on shield hits vs orange sparks/debris on hull hits, and a polished damage-number pop.\n- Player shield hits read as a sphere being struck: a brief full-sphere outline flash, a bright arc segment centered on the laser's incoming bearing (the highlighted hit region), a radial ripple from the impact point, and a spark burst — intensity scaled with damage, decaying over ~0.5s. A shield→hull break shows a distinct shield-collapse cue. Rams (ship collisions) get the same impact treatment.\n- Subtle world-camera shake on player hits, enemy kills, and shield-break — the separate fx-ui camera keeps the HUD/combat bar perfectly still.\n- New visual parameters (bolt size/trail, muzzle, arc span, shake intensity, etc.) are tunable in data/combat.json, consistent with the project's single-tuning-surface convention.\n- No regressions: dev/combat.test.mjs passes with 0 failures; both contexts boot and play; no new dependencies, no build step.\n\nBoundaries:\n- In scope: js/combat/Bullet.js, js/combat/Fx.js, the FX call sites in js/combat/CombatScene.js and js/combat/CombatSystem.js (firing, collisions, damage, kills), camera shake wiring, and tuning knobs in data/combat.json.\n- Out of scope: gameplay numbers (damage, cooldowns, speeds, hull/shield values), enemy AI, new weapons or skills, audio changes (existing SFX events stay as-is), HUD/combat-bar redesign, and non-combat main-game visuals.\n\nConstraints:\n- Plain ES6 modules, no build step, no new dependencies (Phaser 4.2.1 stays vendored).\n- No particle emitters — this build's emitter velocity semantics are fiddly (documented in js/combat/Fx.js); follow the existing hand-rolled pattern: canvas-generated textures + additive-blended images stepped in update().\n- Keep the FX cheap enough for 60fps with 3+ enemies and auto-fire (small per-hit item counts, shared textures, depth discipline: ships 10, FX 19–22, HUD 100).\n- Implement in the SHARED code (Fx.js / Bullet.js) so the range and the main game stay identical; both contexts' FX call sites must be updated together.\n- Camera shake on the world camera only (the fx-ui UI camera must remain unshaken).\n\nVerification contract:\n- Run `node dev/combat.test.mjs` → 0 failures.\n- Manual pass in the range (/combat via the dev server) AND the main game (index.html?combat): player cannon fires elongated bolt + trail + directional muzzle flash; enemy hits show the impact event with distinct shield (cyan ripple) vs hull (orange debris) reads; an enemy lance landing on the player shows the sphere struck — arc highlight centered on the laser's bearing + ripple + sparks, with a shield-collapse cue when shields break; kills show the burst + subtle shake; HUD stays still throughout.\n- Re-read this goal's requirements (lasers, enemy impact, shield sphere hit from the laser's angle, hit-region highlight, shake) and confirm every item is addressed in both contexts before marking complete.\n\nIf blocked: stop and ask the user.",
"status": "complete",
"autoContinue": true,
"usage": {
"tokensUsed": 13148597,
"activeSeconds": 7982
},
"sisyphus": false,
"revision": 176,
"createdAt": "2026-09-17T02:44:06.019Z",
"updatedAt": "2026-09-17T05:08:04.233Z",
"scheduler": {
"version": 1,
"owner": "01a0ad39-dd0b-70d4-8386-f6f507b06334",
"generation": "56a9c1ee-eef2-4266-b1c3-53ca3acc81a2",
"used": 1,
"phase": "running",
"repairUsed": false,
"decision": {
"kind": "ready",
"nextAction": "Continue pursuing the goal, then verify and complete it when satisfied.",
"purpose": "ready"
},
"dispatch": {
"id": "22068984-d87c-408b-980d-fdb9d75adf87",
"kind": "ready",
"claimedAt": 1789613046046
}
},
"taskList": {
"tasks": [
{
"id": "task-1",
"title": "Laser bolt visuals: elongated bolts, trails, muzzle flashes",
"status": "complete",
"verificationContract": "In the /combat range and index.html?combat, player (cyan) and enemy (magenta) shots render as elongated glowing bolts with hot-white cores, colored halos, a fading motion trail along the flight axis, and a directional muzzle flash. Weapon visual knobs (bolt size/trail length, muzzle size) exist in data/combat.json and change the look when edited.",
"completedAt": "2026-09-17T04:34:16.884Z",
"evidence": "Bolt texture (128x32 gradient trail+core+bloom) + white core head in js/combat/Bullet.js; fx.muzzle in CombatScene/CombatSystem; boltLength/boltWidth/muzzle knobs in data/combat.json; verified in /com"
},
{
"id": "task-2",
"title": "Enemy hit impact FX (shield ripple vs hull debris, craft flash)",
"status": "complete",
"verificationContract": "Hitting an enemy in both contexts shows: hot core flash at the impact point, directional sparks along the bullet's travel vector, a visible white hit-flash on the enemy craft, cyan arc ripple + sparks on shield hits vs orange sparks/debris on hull hits, and a damage-number pop. No plain 34px dot flash remains at the hit site.",
"completedAt": "2026-09-17T04:34:16.884Z",
"evidence": "Fx.enemyHit: core flash, dir sparks along travel vector, craft white tintFill flash, cyan arc ripple (shield) vs orange shards (hull), damage-number pop; called identically in CombatScene.collide + Co"
},
{
"id": "task-3",
"title": "Player shield-sphere impact FX (arc at laser bearing, ripple, collapse)",
"status": "complete",
"verificationContract": "When an enemy lance or ram hits the player in both contexts: brief full-sphere outline flash around the ship, bright arc segment centered on the laser's incoming bearing (the highlighted hit region), radial ripple from the impact point, spark burst; intensity scales with damage and decays ~0.5s; when shields break to hull a distinct shield-collapse cue plays. Shield-hit SFX still fires as before.",
"completedAt": "2026-09-17T04:34:16.884Z",
"evidence": "Fx.shieldImpact: sphere outline + arc centered on bearing (travel+PI), ripple, sparks, k-scaled by damage, 520ms decay; shieldBreak implosion+shockwave; rams use same treatment with bearing; verified "
},
{
"id": "task-4",
"title": "Camera shake, config tuning, final polish pass in both contexts",
"status": "complete",
"verificationContract": "Subtle world-camera shake fires on player hits, enemy kills, and shield-break; the fx-ui camera and combat bar stay perfectly still. Shake intensity + FX timing knobs are in data/combat.json. `node dev/combat.test.mjs` passes with 0 failures; both contexts boot clean; all goal success criteria re-checked item by item in both the range and the main game.",
"completedAt": "2026-09-17T04:34:16.884Z",
"evidence": "combatShake on hit/kill/break; live probe: main cam shakeEffect isRunning=true duration=230, fx-ui cam isRunning=false; knobs in data/combat.json fx.shake/fx.shield; node dev/combat.test.mjs = 146 che"
}
],
"blockCompletion": false,
"proposedAt": "2026-09-17T02:43:45.159Z"
},
"stopReason": "agent",
"archivedPath": ".pi/goals/archived/goal_2026091623080422_mu4xefwj-ebnq8h.md"
}
# Goal Prompt
=== Goal ===
Objective: A visual overhaul of combat FX in Orbit — visually impressive laser bolts from both the player and enemies, a strong impact read when enemies are hit, and a shield-sphere hit effect that shows the player's shield struck from the laser's incoming bearing with the hit region highlighted — delivered consistently in both combat contexts (the /combat range and the main game's ?combat boot).
Success criteria:
- Player and enemy shots render as elongated glowing bolts: hot-white core, colored halo (cyan player / magenta enemy), a fading motion trail along the flight axis, and a directional muzzle flash on fire — in BOTH the range (js/combat/CombatScene.js) and the main game (js/combat/CombatSystem.js).
- Enemy hits show impact: a hot core flash at the point of impact, directional sparks along the bullet's travel vector, a visible white hit-flash on the enemy craft, a cyan arc ripple on shield hits vs orange sparks/debris on hull hits, and a polished damage-number pop.
- Player shield hits read as a sphere being struck: a brief full-sphere outline flash, a bright arc segment centered on the laser's incoming bearing (the highlighted hit region), a radial ripple from the impact point, and a spark burst — intensity scaled with damage, decaying over ~0.5s. A shield→hull break shows a distinct shield-collapse cue. Rams (ship collisions) get the same impact treatment.
- Subtle world-camera shake on player hits, enemy kills, and shield-break — the separate fx-ui camera keeps the HUD/combat bar perfectly still.
- New visual parameters (bolt size/trail, muzzle, arc span, shake intensity, etc.) are tunable in data/combat.json, consistent with the project's single-tuning-surface convention.
- No regressions: dev/combat.test.mjs passes with 0 failures; both contexts boot and play; no new dependencies, no build step.
Boundaries:
- In scope: js/combat/Bullet.js, js/combat/Fx.js, the FX call sites in js/combat/CombatScene.js and js/combat/CombatSystem.js (firing, collisions, damage, kills), camera shake wiring, and tuning knobs in data/combat.json.
- Out of scope: gameplay numbers (damage, cooldowns, speeds, hull/shield values), enemy AI, new weapons or skills, audio changes (existing SFX events stay as-is), HUD/combat-bar redesign, and non-combat main-game visuals.
Constraints:
- Plain ES6 modules, no build step, no new dependencies (Phaser 4.2.1 stays vendored).
- No particle emitters — this build's emitter velocity semantics are fiddly (documented in js/combat/Fx.js); follow the existing hand-rolled pattern: canvas-generated textures + additive-blended images stepped in update().
- Keep the FX cheap enough for 60fps with 3+ enemies and auto-fire (small per-hit item counts, shared textures, depth discipline: ships 10, FX 19–22, HUD 100).
- Implement in the SHARED code (Fx.js / Bullet.js) so the range and the main game stay identical; both contexts' FX call sites must be updated together.
- Camera shake on the world camera only (the fx-ui UI camera must remain unshaken).
Verification contract:
- Run `node dev/combat.test.mjs` → 0 failures.
- Manual pass in the range (/combat via the dev server) AND the main game (index.html?combat): player cannon fires elongated bolt + trail + directional muzzle flash; enemy hits show the impact event with distinct shield (cyan ripple) vs hull (orange debris) reads; an enemy lance landing on the player shows the sphere struck — arc highlight centered on the laser's bearing + ripple + sparks, with a shield-collapse cue when shields break; kills show the burst + subtle shake; HUD stays still throughout.
- Re-read this goal's requirements (lasers, enemy impact, shield sphere hit from the laser's angle, hit-region highlight, shake) and confirm every item is addressed in both contexts before marking complete.
If blocked: stop and ask the user.
## Progress
- Status: complete
- Auto-continue: on
- Sisyphus mode: no
- Time spent: 2h13m02s
- Tokens used: 13M (13,148,597) tokens
## Tasks
<!-- blockCompletion: false -->
- [x] task-1: Laser bolt visuals: elongated bolts, trails, muzzle flashes — evidence: Bolt texture (128x32 gradient trail+core+bloom) + white core head in js/combat/Bullet.js; fx.muzzle in CombatScene/CombatSystem; boltLength/boltWidth/muzzle knobs in data/combat.json; verified in /com
- [x] task-2: Enemy hit impact FX (shield ripple vs hull debris, craft flash) — evidence: Fx.enemyHit: core flash, dir sparks along travel vector, craft white tintFill flash, cyan arc ripple (shield) vs orange shards (hull), damage-number pop; called identically in CombatScene.collide + Co
- [x] task-3: Player shield-sphere impact FX (arc at laser bearing, ripple, collapse) — evidence: Fx.shieldImpact: sphere outline + arc centered on bearing (travel+PI), ripple, sparks, k-scaled by damage, 520ms decay; shieldBreak implosion+shockwave; rams use same treatment with bearing; verified
- [x] task-4: Camera shake, config tuning, final polish pass in both contexts — evidence: combatShake on hit/kill/break; live probe: main cam shakeEffect isRunning=true duration=230, fx-ui cam isRunning=false; knobs in data/combat.json fx.shake/fx.shield; node dev/combat.test.mjs = 146 che