Implement Survival discipline tree: Foraging, Tracking, Navigation → Herbalism, Hunting, Map, Astronomy → Alchemy, Pathfinding #233
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
#225 Epic: Non-Combat Discipline Trees
aethyr/Aethyr
Reference: aethyr/Aethyr#233
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-survival-discipline-treefeat(skills): implement Survival discipline tree with 3 tiersBackground and Context
The Survival discipline represents wilderness and exploration skills. It is the first non-combat discipline to receive a full three-tier tree, mirroring the depth of the Combat tree. The Survival tree is organized as follows:
This tree demonstrates the full range of prerequisite patterns: single prerequisites, and multi-prerequisite convergence (Pathfinding requires both Map 5 and Astronomy 5).
Expected Behavior
YAML Definitions added to
conf/skill_trees.yaml:Tier 1 branches (require Survival 1):
survivallevel 1.survivallevel 1.survivallevel 1.Tier 2 branches (require tier-1 at level 3):
foraginglevel 3.trackinglevel 3.navigationlevel 3.navigationlevel 3.Tier 3 branches (require tier-2 at level 5):
herbalismlevel 5.maplevel 5 ANDastronomylevel 5.Tree Structure:
Node Count: 10 nodes total in the Survival discipline (1 root + 3 tier-1 + 4 tier-2 + 2 tier-3).
Multi-Prerequisite: Pathfinding requires both Map 5 AND Astronomy 5, similar to how Martial Arts requires Kick 5 AND Grapple 5.
Acceptance Criteria
conf/skill_trees.yaml.list_by_discipline(:survival)returns 10 nodes sorted by tier.children_of("navigation")returns Map and Astronomy.children_of("map")andchildren_of("astronomy")both include Pathfinding.validate!passes with the full survival tree.check_unlockablecorrectly evaluates all prerequisite chains.Subtasks
conf/skill_trees.yaml.conf/skill_trees.yaml.conf/skill_trees.yaml.list_by_discipline(:survival)returns 10 nodes across 4 tiers.children_offor all survival nodes returns correct children.validate!on the tree with all survival nodes loaded.check_unlockablewith various player skill levels across the survival tree.tests/unit/survival_discipline_tree.featurecovering tier 1/2/3 node loading, single prerequisite chains, multi-prerequisite for Pathfinding, discipline listing, children traversal, tree validation, unlockable checking across tiers.tests/integration/for Survival discipline tree loading and multi-tier prerequisite validation.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.