immortal
/
autohero
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '867a00bf8c'
${ noResults }
autohero/.claude/agent-memory/backend-engineer-go/project_quest_equipment.md

1.2 KiB
Raw Blame History

name description type
Quest and unified gear systems Quest system backend (towns/NPCs/quests/hero_quests) and unified gear system replacing weapons/armor/equipment_items project

Quest system uses migration 000006 schema (towns, npcs, quests, hero_quests tables). Go layer: model/quest.go, storage/quest_store.go, handler/quest.go. Quest progress hooks in processVictoryRewards call IncrementQuestProgress for kill_count and IncrementCollectItemProgress for collect_item quests.

Unified gear system (migration 000014): single gear + hero_gear tables replace weapons, armor, equipment_items, and hero_equipment. model/gear.go has GearItem, GearFamily, GearCatalog. storage/gear_store.go replaces equipment_store.go. weapon.go, armor.go deleted; equipment.go keeps only slot constants. Hero.Gear map[EquipmentSlot]*GearItem replaces Weapon/Armor fields. All loot drops use EquipmentSlot names (main_hand, chest, etc.).

Why: ONE table, ONE model, ONE store for all equippable items -- simpler code, easier to add new slots.

How to apply: NewGameHandler takes gearStore (not equipmentStore). NewNPCHandler takes gearStore. processVictoryRewards handles all slots uniformly. AutoEquipGear replaces AutoEquipWeapon/AutoEquipArmor.