Implement quality effects on reputation #248
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
#213 Epic: Crafting Quality & Skills
aethyr/Aethyr
Reference: aethyr/Aethyr#248
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-quality-reputation-effectsImplement quality effects on reputation (#248)Background and Context
Crafting is not just about making items — it is about building a reputation as a craftsperson within the game world. When a player crafts high-quality items (Masterwork or Legendary tier), this achievement should be recognized by the local settlement and its NPCs. Similarly, selling crafted items to merchants should affect the player's merchant reputation, influencing future trade prices.
This feature connects the crafting quality system to the reputation system, creating a meaningful feedback loop: better crafting leads to better reputation, which leads to better trade deals, which supports further crafting investment.
Expected Behavior
Acceptance Criteria
Subtasks
tests/unit/quality_reputation.featurecovering crafting reputation gain per tier, selling reputation effects, notification messages, persistence.tests/integration/for crafting-to-reputation-to-trade flow.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.