← every conversation

update-combat-leader-and-viewer-issue-files-sep-15-26

written 2026-09-26 12:45:33 · claude-opus-5

she said

Your directive: You are a fork with the whole design conversation in context. The developer has answered many open questions. The documentation validator now reports issue files that still cite questions she has answered, and those issues need their citations and their bodies brought up to date.

Project root: /mnt/cmdo/ritz/games/tq/ai-stuff/double-diaper-dungeon.

FIRST read /tmp/claude-1000/-mnt-cmdo-ritz-games-tq-ai-stuff-double-diaper-dungeon/f76814ba-6c5e-46ea-90d1-128d98043fd5/scratchpad/her-answers-digest.md — that is her settled design, in her own words with the reading beside each. It is the authority. Also read docs/001-what-this-game-is.md for the fixed vocabulary.

YOU OWN EXACTLY THESE TWELVE FILES. Edit only these:

  • issues/401-the-melee-pool-and-the-cadence.md (cites E12)
  • issues/403-the-dodge-rule.md (cites D2)
  • issues/701-the-guild-leader-is-a-presence.md (cites G16)
  • issues/703-headspaces-and-communing.md (cites G16)
  • issues/707-curses-bind-to-a-hero-or-to-the-party.md (cites G16)
  • issues/709-haunted-furniture-is-a-table.md (cites C9)
  • issues/901-the-fixed-step-and-the-speed-control.md (cites H5, H6)
  • issues/902-the-hex-map-on-screen.md (cites H5)
  • issues/903-the-log-window.md (cites H3)
  • issues/905-emoji-through-a-fallback-font.md (cites H2)
  • issues/906-the-priority-slider-widget.md (cites H1)
  • issues/907-the-sheet-the-journal-the-shop-and-the-intro.md (cites H5)
  • issues/910-a-full-run-end-to-end.md (cites H6)

Do NOT touch any other file, any document under docs/, the balance table, or docs/020-open-questions.md. Do not run git. Do not rename any file.

FOR EACH ISSUE, two jobs.

One: the Open questions row. Remove every question id she has now answered. Keep the ones still open. If none remain, write "none". The ids she answered that touch your files are C9, D2, E12, G16, H1, H2, H3, H5, H6. Anything else stays.

Two: the body. Where her answer changes what the issue is meant to build, rewrite the Intended behavior and the Suggested implementation steps so the blueprint is correct. No worklog, no dated note; an issue is a blueprint and it simply says the right thing now. Keep the format: header table, Current behavior, Intended behavior, Suggested implementation steps, Related documents and tools, Still open.

The ones whose bodies genuinely change:

  • 403 is the big one. Her answer settles the dodge rule's stat wiring and it is not what the issue currently guesses. The avoid value is defensive attention: it decays as a defender coasts through swings that miss, and a hit snaps them back, which is why a hit restores it. The ATTACKER'S IMAGINATION widens the decay, because their picture of the enemy makes its defences transparent, so the entry called the attacker's dexterity widening becomes dodge.imagination_widening and the issue must say so. The ATTACKER'S DEXTERITY raises the chance to hit, a separate roll layered on the defender's avoid value, exploiting precise vulnerabilities. The DEFENDER'S CONSTITUTION raises how much of the missing value a hit restores, because stamina is what re-asserts attention. The defender's own dexterity plays no part in avoiding at all: dexterity is armour and to-hit, avoidance is attention. Keep the Monte Carlo findings that survive (roughly five whiffs per side open every fight; the widening is the strong lever) and correct which stat pulls the lever. Say what the scenario that tests this must show.
  • 401 gains that a caregiver is not necessarily a healer, which shortens the in-combat order of business.
  • 701 is substantially rewritten. The leader has confidence of their own, moved by what happens to the heroes but at a fraction of the size, because the leader only reads the reports. The leader can crybaby. The leader is calmed by a caregiver at a basecamp, which means the leader has a place at least while being calmed: reconcile that with "a presence, not a map unit" honestly rather than papering over it, and propose that the leader has no position while things go well and is at a named basecamp while being calmed, marked as a working ruling. Suggestibility is a number that rises and falls with the level's events and sets how readily the leader slips into a headspace. Name the entries.
  • 703 gains suggestibility as the thing that makes a headspace easier or harder to enter, and that the leader is not cursed into one.
  • 707 gains that a curse does not put the leader into a headspace; what the level does to the leader works through suggestibility instead.
  • 709 gains the woken haunted toilet: it infests its room like any infestation, and the hero who woke it becomes a crybaby who flees to the room they came from and cries there until calmed, after which both join the wait at that door. That is a second kind of crybaby and the furniture table must be able to express it.
  • 901 gains: full screen, high-DPI, 2560 by 1440 as the baseline, and no fast-forward — pause, half and normal and nothing else.
  • 902 gains the fog of war on screen: three states per room, a glimpsed room drawing only that it exists and whether it is infested, a fogged room drawing nothing of its contents, and re-fogging announced so the player notices a corridor closing behind them. Plus the full-screen baseline. Note that what a hex draws when it is too small for a picture is still open.
  • 903 is rewritten around one log window per battle, draggable AND resizable AND scrollable, logs kept after their battle ends and stored in the journal, which is reachable from the UI. That makes the journal the one place holding clues, ghost dialogue already seen, and past battle logs together.
  • 905 gains that the emoji list is closed and reused, checked at startup, refusing to run when a glyph is missing.
  • 906 is rewritten around dividers: each stat's share is the gap back to the previous divider, the last share is the leftover and cannot be dragged directly, the minimum share clamps every gap, adding a divider splits the gap it lands in, and the shares govern curatives as well as equipment. Work out and state what the drag arithmetic is under that model.
  • 907 gains: the intro stops the clock because it happens before the adventure, the ghost scene stops it too, and the character sheet is the page showing one hero's stats, mind, body, garment, gear and stickers — with the working ruling that the world keeps running while it is open, flagged as still hers to confirm. Also the chibi avatar of the leader, permanently in the corner of the screen, showing the leader's state; say which screen owns it.
  • 910 gains that the speed control has exactly three settings.

Note for 902 and 907: the stat colour palette is strength pink, constitution dark red, intellect blue, spirit yellow, dexterity green. Spirit is a stat this project has never had. Do not invent it, do not rename anything; where the palette matters, say the palette is incomplete because one colour names a stat the record does not hold, and leave it in Still open.

When done, reply with: each file and its word count, the balance-table entries you named that do not exist yet (dotted name and one line of meaning), and any new open questions (topic plus one sentence). Nothing else.

the assistant claude-opus-5
I'll update the thirteen combat, leader, and viewer issue files to drop answered question citations and rewrite their bodies to match her settled design.
Now I'll rewrite each file. Starting with 403, where her answer changes the most.
Now 703 and 707, which gain suggestibility.
Now 709, which gains the woken haunted toilet and its second kind of crybaby.
Now the viewer issues. 901, 905, 910 are small; 902, 903, 906, 907 change more.
Now 902 with the fog of war, and 903 rebuilt around the journal.
Now 906, rebuilt around dividers, then 907 and 910.
All cited ids exist and are still open. Let me confirm the validator agrees for my thirteen files.

Thirteen combat, leader, and viewer issue files updated: answered-question citations dropped, bodies rewritten where her answers changed the blueprint.

FileWords
401-the-melee-pool-and-the-cadence1155
403-the-dodge-rule1653
701-the-guild-leader-is-a-presence1895
703-headspaces-and-communing1270
707-curses-bind-to-a-hero-or-to-the-party1021
709-haunted-furniture-is-a-table1655
901-the-fixed-step-and-the-speed-control1362
902-the-hex-map-on-screen1774
903-the-log-window1388
905-emoji-through-a-fallback-font1144
906-the-priority-slider-widget1402
907-the-sheet-the-journal-the-shop-and-the-intro1550
910-a-full-run-end-to-end876

The validator reports no failures against any of them; every remaining cited id exists in the questions page and is still open. Only these thirteen were touched.

New balance entries named, all provisional:

  • dodge.imagination_widening — extra decay per point of the attacker's imagination. Replaces dodge.dexterity_widening, which now describes the wrong stat and should be retired, not merely renamed in one place; the combat document and 403 both carry the old name.
  • dodge.dexterity_to_hit — the attacker's chance-to-hit bonus per point of dexterity, a roll layered before the avoid roll.
  • leader.echo_fraction — how much of a hero's confidence change reaches the leader, who is only reading reports.
  • leader.crybaby_line — the leader's confidence below which they start crying.
  • leader.suggestibility_rise / leader.suggestibility_fall — how fast the level's events move the leader's suggestibility.
  • commune.suggestibility_to_fill — how much suggestibility scales the communing meter's fill rate.
  • journal.kept_log_count — how many finished battle logs the journal stores before dropping the oldest.

New open questions:

  • Retiring the widening entry. dodge.dexterity_widening is now a name for a rule that no longer exists; leaving it in the table means somebody reads it as live.
  • Armour from dexterity. Dexterity is to-hit and armour, and only the to-hit half is now specified; whether armour is flat or fractional belongs to 404.
  • The leader's position while crying. I ruled the leader is at a named basecamp while being calmed and nowhere otherwise, which strains "a presence, not a map unit"; she may prefer that calming needs only a caregiver somewhere in the guild.
  • Which basecamp the leader is placed at. Ruled nearest the guild's centre of gravity, which needs defining when the guild is spread out.
  • Spirit blocks three files. 902, 906 and 907 all need the stat palette, and one of her five colours names a stat the record does not have; the slider cannot offer a stat it cannot colour.
  • Fleeing heroes. Whether a hero fleeing a woken object can be intercepted (ruled no, the flight is one tick), and what happens if the room they flee to is itself infested by the time they arrive (ruled they cry at its door).
  • A glimpsed room that was once seen should probably look different from one never entered; ruled yes with a dimmer outline, since losing the map is the point and losing the memory of it is not.
  • Camera bounds under fog. Whether the player can pan into rooms that are wholly unknown.
  • Full-screen mode. Borderless desktop or exclusive, which changes how leaving the game behaves.
  • Run length. With no fast-forward, how long a whole run takes at normal speed decides whether the tick rate is right, and nobody can know until one is played.
  • Unused emoji rows. Whether a listed glyph that nothing ever draws should warn, since an unchecked row is an unchecked meaning.
  • Journal logs across a level transition. Ruled they survive, since the level is gone but the run is not.