How ebkr/r2modmanplus works
Main Components
a) Frontend Layer:
• Vue.js based UI components (src/components)
• Quasar Framework integration
• Store management (Vuex - src/store)
• Routing system (src/router)
b) Backend Layer (Electron):
• Main process (src-electron/main-process)
• IPC communication system
• File system operations
• Game management system
c) Core Services:
• Mod Management System
• Profile Management
• Package Installation System
• Game Directory Resolution
• Configuration Management
• Update System
Key Relationships to Highlight
a) Data Flow:
• User Interface → IPC Bridge → Main Process
• Main Process → File System
• Main Process → External Services (Thunderstore)
• Profile System → Mod Management
• Config Editor → File System
b) Integration Points:
• Game Platform Integration (Steam, Epic, Xbox)
• Mod Repository Integration
• Update Service Integration
[User Interface Layer]
• ↓↑
[IPC Communication Layer]
• ↓↑
[Core Services Layer]
• ↓↑
[System Integration Layer]
Important Elements
a) Core Features:
• Mod Download/Installation Pipeline
• Profile Management System
• Configuration Editor
• Game Detection System
• Update Management
b) External Integrations:
• Game Platforms (Steam, Epic, Xbox)
• Mod Repositories
• Auto-Update System
c) Storage Systems:
• Local File System Integration
• Profile Storage
• Configuration Storage
• Cache Management
Implementation Details to Highlight
• Cross-platform compatibility (Windows, Linux, macOS)
• Multiple game support architecture
• Profile import/export system
• Mod dependency management
• Configuration management system