As a game designer
I want to view how player states map to sprite suffixes
So that I can understand how player visuals work without reading the code
Context / Problem
Player state appearance is currently defined in a hard-coded constant in PSDK, making it difficult to discover and understand. This particularly impacts non-technical users who need this information but cannot easily access it.
Acceptance Criteria
Scope
- Read-only visualization of player states and suffix mapping
- UI focused on clarity and discoverability
Out of Scope
- Editing values
- Configuration files
- Runtime integration
- Custom states
Notes
- This is a pure UX improvement with low technical risk
- Should be considered as a foundation for future enhancements
As a game designer
I want to view how player states map to sprite suffixes
So that I can understand how player visuals work without reading the code
Context / Problem
Player state appearance is currently defined in a hard-coded constant in PSDK, making it difficult to discover and understand. This particularly impacts non-technical users who need this information but cannot easily access it.
Acceptance Criteria
Scope
Out of Scope
Notes