Epic: Reputation Mechanics #202
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 milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#199 Reputation & Social Standing
aethyr/Aethyr
Reference: aethyr/Aethyr#202
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
Background and Context
This epic implements the core mechanical systems that drive reputation changes in Aethyr. It covers three key areas: reputation propagation between related entities (allied factions, rival factions, parent/sub-regions), natural decay of reputation scores over time toward neutrality, and the gameplay effects that reputation tiers have on merchant prices, area access, and quest availability.
Reputation propagation ensures that actions affecting one faction ripple through the faction relationship graph — helping allies and hurting rivals. Decay prevents permanent grudges or favor from single actions. Gameplay effects give reputation mechanical weight so players feel the consequences of their standing.
This epic depends on the Reputation Data Model & Storage epic (#201) being complete.
Child Issues
Acceptance Criteria
master.Definition of Done
This epic is complete when all child issues listed above are completed, reviewed, merged to
master, and verified.