Epic: Reputation Data Model & Storage #201
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.
Reference: aethyr/Aethyr#201
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 covers the foundational data model and persistence layer for the Reputation & Social Standing system in Aethyr. The reputation system allows players to build and track standing with factions, settlements, and individual NPCs across a 9-tier scale from Reviled to Exalted.
The data model must support multi-dimensional reputation tracking per entity, categorized by type (faction, settlement, NPC), with named tiers and score thresholds. All reputation data is persisted in the player's info hash and changes are broadcast via Wisper events for other systems to react to.
This epic is a prerequisite for all other reputation-related epics, as the mechanics, UI, and devotee systems all depend on the underlying data model.
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.