Victory, defeat, and the results screen #12

New issue

Open

opened 2026-08-06 21:51:50 +00:00 by icub3d · 0 comments

icub3d commented

2026-08-06 21:51:50 +00:00

Owner

End the mission and report it. The minimum that makes the slice a game rather than a
sandbox.

Scope

Objective check: the mission ends when one side has no living units.
Transition to GameState::Results carrying the outcome.
A minimal results screen: won or lost, turns taken, units lost, and a route back to
the main menu.

Acceptance criteria

The victory check is part of resolution, not a UI system, so the headless test can
observe it.
Mission entities are fully torn down on leaving GameState::Mission — no leaked
entities across a second run.
Starting a second mission from the menu works and is unaffected by the first.
The results screen is built from src/ui/widget.rs builders and theme tokens.

End the mission and report it. The minimum that makes the slice a *game* rather than a sandbox. ## Scope - Objective check: the mission ends when one side has no living units. - Transition to `GameState::Results` carrying the outcome. - A minimal results screen: won or lost, turns taken, units lost, and a route back to the main menu. ## Acceptance criteria - [ ] The victory check is part of resolution, not a UI system, so the headless test can observe it. - [ ] Mission entities are fully torn down on leaving `GameState::Mission` — no leaked entities across a second run. - [ ] Starting a second mission from the menu works and is unaffected by the first. - [ ] The results screen is built from `src/ui/widget.rs` builders and `theme` tokens.

icub3d added the

labels

2026-08-06 21:52:07 +00:00

icub3d added this to the M1 — Playable Vertical Slice milestone

2026-08-06 22:21:46 +00:00

icub3d referenced this issue from a commit

2026-08-07 02:03:31 +00:00