Implement Character Sheet display with stats, skills, equipment summary, and reputation overview #236
Labels
No labels
Blocked
Duplicate
MoSCoW/Could Have
MoSCoW/Must Have
MoSCoW/Should Have
Points/1
Points/13
Points/2
Points/21
Points/3
Points/5
Points/8
Priority/Backlog
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
State/Completed
State/In progress
State/In review
State/Paused
State/Unverified
State/Verified
State/Wont Do
Type/Bug
Type/Epic
Type/Feature
Type/Legendary
Type/Task
Type/Testing
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#226 Epic: Skill UI & Commands
aethyr/Aethyr
Reference: aethyr/Aethyr#236
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?
Metadata
feature/m4-character-sheet-displayfeat(skills): implement Character Sheet display with stats, skills, and equipment summaryBackground and Context
A character sheet is a fundamental UI element in any RPG. Players need a single command that presents a comprehensive overview of their character's current state: base stats, skill levels, equipped items, and reputation standing. This is distinct from the detailed skill tree overlay — the character sheet provides a summary view suitable for quick reference.
The
status(orsheet) command renders the character sheet in the main output window (not an overlay), making it easy to glance at during gameplay. The format should be clean, well-organized, and use ASCII formatting to create visual sections.Expected Behavior
CharacterSheetRenderer class at
lib/aethyr/core/render/character_sheet_renderer.rb:render(player)— returns an array of strings representing the formatted character sheet.Character Sheet Layout:
Sections:
+prefix. Only show skills with level > 0.Command Registration:
statusandsheetboth trigger the character sheet display.Graceful Handling:
Acceptance Criteria
CharacterSheetRendererclass exists atlib/aethyr/core/render/character_sheet_renderer.rb.render(player)returns correctly formatted character sheet output.+prefix.statusandsheetcommands both display the character sheet.Subtasks
lib/aethyr/core/render/character_sheet_renderer.rbwith theCharacterSheetRendererclass.+prefix.statusandsheetcommands to triggerCharacterSheetRenderer#render.tests/unit/character_sheet_renderer.featurecovering full sheet rendering, stats section formatting, skills section with progress bars, sub-skill indentation, equipment with bonuses, empty equipment slots, reputation labels, new character defaults, command registration.tests/integration/for Character sheet display and status/sheet command interaction.bundle exec rake unit_profileand verify no performance regressions.bundle exec rake unit. If coverage is <97% then review the current unit test coverage report atbuild/tests/unit/coverage/and use it to write new Cucumber based unit tests to improve code coverage. Specifically, write Cucumber/Gherkin style unit tests that are descriptively named and specifically improve coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerunbundle exec rake unitto verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%.bundle exec rake(default task: unit tests with coverage) andbundle exec rake integration, fix any errors if needed ensuring both pass across entire code base, do not ignore any failure even if it seems unrelated to this commit, fix it.Definition of Done
This issue is complete when:
master, reviewed, and merged before this issue is marked done.