Action model and deterministic resolution #7
Labels
No labels
area/ai
area/build
area/character
area/combat
area/data
area/docs
area/game
area/net
area/ui
area/world
size
l
size
m
size
s
type
bug
type
design
type
feature
type
refactor
type
test
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
icub3d/terra-redux#7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The core of the simulation/presentation split (
CLAUDE.md). An action is submitted,resolution computes the entire outcome immediately, and the outcome is emitted as
events. Nothing in resolution waits on an animation, a frame, or a tween.
Scope
Actionenum:Move,Attack,Wait. Bounded and closed — this is the samediscipline the M3 effect primitives will need.
Outcomeevents describing exactly what happened: who moved along which path, whotook how much damage, who died.
CombatRngresource carrying a seeded RNG, threaded through resolution. Resolutionnever touches an unseeded RNG.
Acceptance criteria
always produce the same outcome. Asserted by a test that replays a sequence.
reason, and leave state untouched.
committed — pillar 4. A preview path exists even if no UI consumes it yet.
Notes
Worth an ADR on the action/outcome boundary, since netcode (M7) and replays depend on it.