How eraxium-mc/lofty-launcher works
Main Components
a. Frontend Layer (UI Components):
• Landing Page (landing.ejs)
• Login System (login.ejs, loginOptions.ejs)
• Settings Panel (settings.ejs)
• Overlay System (overlay.ejs)
• Welcome Screen (welcome.ejs)
b. Core Services Layer:
• Authentication Manager (authmanager.js)
• Configuration Manager (configmanager.js)
• Distribution Manager (distromanager.js)
• Language Manager (langloader.js)
• Discord Integration (discordwrapper.js)
c. System Integration Layer:
• Components for:
• Process Builder (processbuilder.js)
• Server Status Handler (serverstatus.js)
• Drop-in Mod Utility (dropinmodutil.js)
d. Asset Management:
• Containers for:
• Static Assets (images, CSS, fonts)
• Configuration Files
• Language Files
Connection Flow
• User Interface → Authentication Manager
• Authentication Manager → Configuration Manager
• Distribution Manager → Process Builder
• Language Manager → UI Components
• Discord Wrapper → External Discord Service
Important Architectural Patterns to Highlight
• Event-driven architecture (IPC Constants)
• Service-based modular design
• Multi-language support system
• Configuration management system
Technical Details
• Electron Runtime Environment
• Node.js Backend Services
• EJS Template Engine
• Java Integration (libraries/java)
External Integrations
• Discord Services
• Microsoft Authentication (referenced in docs/MicrosoftAuth.md)
• Game Distribution System (referenced in docs/distro.md)
Development Tools Layer
A separate section for:
• Build System (electron-builder.yml)
• Development Tools (.eslintrc.json)
• CI/CD Pipeline (.github/workflows)
User Interface Layer (Top)
↓
Core Services Layer
↓
System Integration Layer
↓
External Services (Bottom)
This structure reflects the launcher's primary purpose of managing game distributions, handling authentication, and providing a user-friendly interface for game management.