Open Questions
Open Questions
Things deliberately left undecided as of 2026-09-27 (design sessions 1-2):
- Damage during exec: no auto-abort by default (large spells stay viable), but the game needs disruption tools (reactions/abilities that push or slow a cycle) or committed casters are untouchable. Tuning, not structure.
- Reaction PER values: exact phase costs for reaction actions - baseline guideline is short/zero prep, short exec, padded recover as the tax (the 0/1/N shape).
- Initiative magnitude: how much prep/recover jitter initiative should shave (and whether it compounds with the fighters' zero-phase feats).
- Encumbrance model: weight lands in the exec stat-side for movement (alongside dex) but the concrete numbers are open.
- Danger tiles and 3D: proposed approach is 3D tiles - there are no "open" tiles; stepping into an open space at your level means falling until you hit the bottom, then you're on that level; fly/levitate keeps you at height unless you take an action to rise or sink. Open because ASCII display is hard: shading on tiles could indicate space above; blank tiles could indicate space below.
- UI/information design: how ASCII conveys phase state, and whether the player's Lore/Int gates what the UI reveals (identification-tradition style).
- Exact tick basis and tile size: confirm the ~10 ticks/foot granularity and the base tile (leaning to 1 cubic foot; human footprint ~2 wide x 1 deep, matching the taller-than-wide roguelike glyph). Per-tile movement baseline at even terrain.
- Decision-model backend choice: hosted vs local vs fallback, when the judgment layer actually ships.
- Reaction chaining: can a reaction trigger a reaction in the same tick? Proposal: reactions triggered during the reaction pass queue for the next tick - bounded and deterministic, one reaction per actor per tick. Feats/stances may bend it.
- Reactive builds: acting almost entirely on reactions (a duelist stance that punishes anything acting nearby; reacting during your own reaction's recover to skip the tax). The exploit window makes this risky by design - a feat/stance space to explore.
- Interruptibility details: which actions pause vs cancel when the actor reacts (concentration-dependent
on_reactproperty); the taxonomy needs building out per action. - Terrain on all prep/recover? Should terrain influence every action's prep and recover, not just movement? Casting on a mountain ledge in a thunderstorm should be harder than on steady ground. If yes, terrain applies a general prep/recover modifier, with movement-specific rules layered on top.