MissionPhase sub-state and combat system ordering #8
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#8
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?
Declare in-mission phases as a sub-state and combat ordering as named
SystemSets, so"what runs when" is readable in one place rather than reconstructed from
.after()chains scattered across plugins.
Follow
MenuScreeninsrc/core/state.rs— a sub-state, not a resource, so leavingGameState::Missiontears everything down for free.Scope
MissionPhasesub-state ofGameState::Mission:PlayerTurn,EnemyTurn,Resolving,Animating.CombatSetenum of named ordering sets, configured in one place.(
CLAUDE.md§ State).Acceptance criteria
MissionPhasedoes not exist outsideGameState::Mission, asserted by a test inthe style of
menu_screen_exists_only_inside_main_menu.not by timers.