Phillip Tarrant
df26abd207
Add YAML-driven quest system with context-aware offering:
Core Implementation:
- Quest data models (Quest, QuestObjective, QuestReward, QuestTriggers)
- QuestService for YAML loading and caching
- QuestEligibilityService with level, location, and probability filtering
- LoreService stub (MockLoreService) ready for Phase 6 Weaviate integration
Quest Content:
- 5 example quests across difficulty tiers (2 easy, 2 medium, 1 hard)
- Quest-centric design: quests define their NPC givers
- Location-based probability weights for natural quest offering
AI Integration:
- Quest offering section in npc_dialogue.j2 template
- Response parser extracts [QUEST_OFFER:quest_id] markers
- AI naturally weaves quest offers into NPC conversations
API Endpoints:
- POST /api/v1/quests/accept - Accept quest offer
- POST /api/v1/quests/decline - Decline quest offer
- POST /api/v1/quests/progress - Update objective progress
- POST /api/v1/quests/complete - Complete quest, claim rewards
- POST /api/v1/quests/abandon - Abandon active quest
- GET /api/v1/characters/{id}/quests - List character quests
- GET /api/v1/quests/{quest_id} - Get quest details
Frontend:
- Quest tracker sidebar with HTMX integration
- Quest offer modal for accept/decline flow
- Quest detail modal for viewing progress
- Combat service integration for kill objective tracking
Testing:
- Unit tests for Quest models and serialization
- Integration tests for full quest lifecycle
- Comprehensive test coverage for eligibility service
Documentation:
- Reorganized docs into /docs/phases/ structure
- Added Phase 5-12 planning documents
- Updated ROADMAP.md with new structure
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
5.8 KiB
5.8 KiB
Phase 11: Beta Testing & Iteration
Goal: Gather feedback, fix issues, balance gameplay Priority: High Status: Not Started Last Updated: November 29, 2025
Overview
Launch a closed beta to gather real user feedback, identify bugs, balance gameplay mechanics, and optimize performance before public launch.
Key Goals:
- Recruit 10-20 beta testers
- Systematic feedback collection
- Bug fixing and stabilization
- Combat and economy balancing
- Performance optimization
- AI prompt improvements
Task Groups
Beta Recruitment (3 tasks)
| Task ID | Task | Status | Notes |
|---|---|---|---|
| 11.1 | Create beta signup form | ⬜ | Collect email, gaming experience, availability |
| 11.2 | Recruit 10-20 beta testers | ⬜ | Friends, communities, Discord |
| 11.3 | Create beta tester onboarding | ⬜ | Welcome email, how to give feedback, known issues |
Beta Tester Profile:
- Mix of casual and hardcore gamers
- Some D&D/RPG experience helpful
- Willing to provide detailed feedback
- Available for 1-2 weeks of testing
Deliverable: Active beta tester group
Feedback Collection (3 tasks)
| Task ID | Task | Status | Notes |
|---|---|---|---|
| 11.4 | Create feedback form | ⬜ | Bug reports, suggestions, ratings |
| 11.5 | Set up Discord server for testers | ⬜ | Channels: bugs, suggestions, general |
| 11.6 | Checkpoint: Collect first round of feedback | ⬜ | After 3-5 days of testing |
Feedback Categories:
- Bugs: Crashes, errors, broken features
- UX Issues: Confusing UI, unclear instructions
- Balance: Too easy, too hard, unfair
- Suggestions: Feature requests, improvements
- AI Quality: Narrative quality, NPC responses
Deliverable: Organized feedback pipeline
Monitoring & Analysis (3 tasks)
| Task ID | Task | Status | Notes |
|---|---|---|---|
| 11.7 | Monitor Sentry error logs daily | ⬜ | Prioritize critical and frequent errors |
| 11.8 | Monitor AI costs | ⬜ | Track daily spending, adjust limits if needed |
| 11.9 | Analyze usage patterns | ⬜ | Popular features, drop-off points, session length |
Deliverable: Data-driven insights
Bug Fixing (3 tasks)
| Task ID | Task | Status | Notes |
|---|---|---|---|
| 11.10 | Triage and prioritize bugs | ⬜ | Critical → High → Medium → Low |
| 11.11 | Fix critical and high priority bugs | ⬜ | Game-breaking issues first |
| 11.12 | Fix medium priority bugs | ⬜ | UX issues, minor glitches |
Priority Definitions:
- Critical: Game unplayable, data loss, security issues
- High: Major feature broken, frequent crashes
- Medium: Minor feature broken, visual glitches
- Low: Edge cases, cosmetic issues
Deliverable: Stable, bug-free experience
Balancing (3 tasks)
| Task ID | Task | Status | Notes |
|---|---|---|---|
| 11.13 | Balance combat difficulty | ⬜ | Adjust enemy HP, damage, encounter rates |
| 11.14 | Balance economy | ⬜ | Gold rewards, item prices, quest rewards |
| 11.15 | Checkpoint: Verify balance feels right | ⬜ | Tester feedback on difficulty |
Balancing Metrics:
- Average combat win rate: 70-80%
- Time to level up: ~30 minutes per level
- Gold earned vs. needed for upgrades
- Quest completion rates
Deliverable: Balanced gameplay
Optimization (3 tasks)
| Task ID | Task | Status | Notes |
|---|---|---|---|
| 11.16 | Optimize slow API endpoints | ⬜ | Profile and improve <200ms target |
| 11.17 | Optimize AI prompts for quality/cost | ⬜ | Better prompts, lower token usage |
| 11.18 | Reduce page load times | ⬜ | Asset optimization, caching |
Performance Targets:
- API response time: <200ms (non-AI)
- AI response time: <3s
- Page load time: <2s
- Time to interactive: <1s
Deliverable: Optimized performance
Documentation Update (2 tasks)
| Task ID | Task | Status | Notes |
|---|---|---|---|
| 11.19 | Update documentation based on learnings | ⬜ | API docs, user guide, troubleshooting |
| 11.20 | Final Checkpoint: Beta sign-off | ⬜ | All critical issues resolved |
Deliverable: Updated documentation
Files to Create/Modify
New Files:
/docs/BETA_FEEDBACK.md- Aggregated beta feedback/docs/KNOWN_ISSUES.md- Known issues and workarounds
Modified Files:
- Various bug fixes across codebase
/api/app/data/enemies/*.yaml- Balance adjustments/api/app/data/quests/*.yaml- Reward adjustments/api/app/ai/prompts.py- Prompt improvements
Testing Criteria
Bug Verification
- All critical bugs fixed
- All high priority bugs fixed
- Medium priority bugs addressed or documented
Balance Verification
- Combat feels challenging but fair
- Economy feels rewarding
- Progression pace feels good
Performance Verification
- API endpoints meet targets
- AI responses acceptable
- No noticeable lag in UI
Beta Tester Satisfaction
- Overall positive feedback
- Testers would recommend to friends
- Major concerns addressed
Success Criteria
- 10-20 active beta testers
- Feedback collection system working
- Zero critical bugs
- < 5 high priority bugs remaining
- Combat balanced (70-80% win rate)
- Economy balanced
- Performance targets met
- Positive beta tester sentiment
Dependencies
Requires (from earlier phases):
- Production deployment (Phase 10)
- All features implemented
Task Summary
| Group | Tasks | Checkpoints |
|---|---|---|
| Beta Recruitment | 3 | 0 |
| Feedback Collection | 2 | 1 |
| Monitoring & Analysis | 3 | 0 |
| Bug Fixing | 3 | 0 |
| Balancing | 2 | 1 |
| Optimization | 3 | 0 |
| Documentation Update | 1 | 1 |
| Total | 17 | 3 |