Backlog: a death drops the carried charge where the player fell

de91d3715a63eadebda6a90533b208cf12476c40 · Pavel Safronov · 2026-10-25 11:51:16 -0700 · parents 0bfdc8e66f5f

Claude Code usage: this commit ≈0 out / ~2.6M cached · cost unknown (no per-model trailer) · session 4 tally 3.4K in / 1.6M out / 705.7M cached · usage by commit and session

Backlog: a death drops the carried charge where the player fell

The user's choice of the options: the charge, with what is left of it,
becomes a drop on the tile where the player died, for the retry to pick
up again. To build.

Usage: 3.4K in / 1.6M out / 705.7M cached (session tally)
rtk:   1.9M saved, 39.0% over 4581 cmds (global/lifetime)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

 PLAN.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/PLAN.md b/PLAN.md
index 10c25a5..7b6a15c 100644
--- a/PLAN.md
+++ b/PLAN.md
@@ -1024,7 +1024,9 @@ tools/                 compose-icons.sh (composed sprites and the app icons), sc
 
 ### Backlog
 
-- **Lose the carried charge on a death? (user idea, 2026-10-25; to decide.)** Today the charge
+- **Decided (user, 2026-10-25): on a death, the carried charge drops where the player fell**, with
+  what is left of it, as a drop the retry can pick up again (option 1 below). To build.
+  Was: **Lose the carried charge on a death? (user idea, 2026-10-25.)** Today the charge
   carried goes through a death (§3.3). Dropping it would make a death cost more than the life and
   give a reason to use a charge rather than hoard it; but it also hits hardest the player who is
   already struggling, and the retry would start without the tool that might have saved them. A