combat-ui

To build a pre-battle UI and battle report workflow in Bevy, trigger PendingCombatEngagement to spawn the pre-battle screen, then transition to the battle report after combat resolves. This coordinates phase-gated systems and visualizes unit rosters.

Yes, you can track per-unit kill attribution and upgrade bonuses in a Bevy combat system. The workflow maps upgrades to specific combat roles and highlights bonus kills within the battle report, supporting debugging and design iteration.

Counter relationship visualization for 7-roles combat mechanics works by displaying unit rosters and counter relationships across pre-battle and battle-report screens. This exposes the modular UI pipeline to support design iteration for single-player and AI-vs-AI scenarios.

Yes, this Bevy combat UI supports both AI-vs-AI scenarios and single-player modes. It coordinates complex combat systems by applying modifications to combat resolution, UI screens, and army composition displays universally across these gameplay contexts.

The best way to style unified combat panels and status indicators in Bevy is to use data-driven UI tokens. This provides consistent design tokens for panels, borders, and status indicators across all pre-battle and battle-report views.