- Add python-dotenv to load .env configuration
- Read USE_MOCK_DATA and EU_CHAT_LOG_PATH from environment
- Use real game log when USE_MOCK_DATA=false
- Show correct mode (Mock vs Live) in header
- Import os module for environment access
Fixes issue where app always used mock data regardless of .env settings.
- English loot uses parentheses: 'x (2)' not 'x 2'
- Add English damage pattern: 'You inflicted X points of damage'
- Support both Swedish and English damage dealt events
- Fix empty bracket pattern: [System] [] Message
Tested with real log output showing English client format.
- Add Swedish regex patterns based on real chat.log from user session
- Support loot, globals, skills, damage, healing, weapon tier
- Add real-chat-sample.log for testing (14 events parsed)
- LogWatcher now parses Swedish game client output correctly
- Fix terminology: Projects (activities) vs Sessions (gameplay)
- Add EntropiaNexusAPI integration for weapon/armor/tool stats
- Implement GearLoadout class for equipment management
- Calculate hunting/mining costs per hour
- Add DPP (Damage Per PEC) efficiency tracking
- Create comprehensive WINDOWS_TESTING_GUIDE.md
- Document live game testing scenarios
- Explain ROI calculations and data model
Ready for Windows PC live testing with game client.
- Replace Python-style # comments with SQL-standard -- comments
- SQLite does not recognize # as comment character
- Fixes database initialization failure on first run
Test: Database now initializes successfully.
- Mark Sprint 1 as complete with all deliverables
- Add main.py and USER_TEST_GUIDE.md to key files
- Update status: Ready for user testing v0.1.0
- Add Sprint 2 planning (GUI Foundation)
Application is now runnable and ready for first user test.
- Create main.py with interactive CLI for user testing
- Implement menu system: projects, sessions, stats, archive
- Add live session mode with mock log watching
- Real-time event display (loot, globals, skills)
- Auto-generate mock chat.log on first run
- Add USER_TEST_GUIDE.md with test checklist
- Document expected output and troubleshooting
Application is now runnable for first user test.
- Create schema.sql with Data Principle support (projects, sessions, loot)
- Implement DatabaseManager with connection pooling and WAL mode
- Add Decimal adapter for PED/PEC precision (Rule #4)
- Enable foreign keys and performance optimizations (Rule #3)
- Add backup functionality for data safety
Database supports project archiving, session tracking, and
historical data comparison per Data Principle.
- Create comprehensive PROJECT_INDEX.md with full directory structure
- Document current (documentation) vs target (implementation) structure
- Map all core modules and technology stack
- Update PROJECT_RESUME with Sprint 0 completion status
- Mark agent identity synchronization complete
- Reference AGENTS.md Never-Break Rules
Establishes canonical project reference for Lead Engineer workflow.
- Add OBSIDIAN_API_URL for flexible endpoint configuration
- Default: localhost (127.0.0.1:27123) for local Obsidian
- Configurable for remote Obsidian instances (e.g., main PC)
- Requires Local REST API community plugin enabled
Allows agents to connect to Obsidian running on different
machines within the network.
- Add OBSIDIAN_API_KEY for agent integration with notes vault
- Add OBSIDIAN_VAULT_PATH for local file access
- Add OBSIDIAN_PROJECT_TEMPLATE for documentation templates
Enables AI agents to read/write project notes and maintain
knowledge base synchronization with Obsidian.
- Add complete .env.example template with all 15+ configuration sections
- Include Gitea SSH key configuration
- Update .gitignore to track .env.example while securing .env
- Add PROJECT_RESUME.md for development state tracking
- Create project directory structure
Resolves merge conflict with remote version by combining both
approaches: comprehensive documentation + SSH configuration.
- Add comprehensive .env.example with all configuration options documented
- Update .gitignore to track .env.example while keeping .env secure
- Add PROJECT_RESUME.md for development state tracking
- Create project directory structure (data, screenshots, logs, etc.)
The .env.example serves as documentation and setup reference for
new deployments while actual credentials remain gitignored.
LemonNexus
ImpulsiveFPS