How torikushiii/hoyolab-auto works
Main Components
a. Core System Components:
• Command Handler System
• Cron Job Manager
• Platform Integration Layer
• HoyoLab API Integration
• Game-Specific Modules
• Notification System
b. External Services:
• HoyoLab/Hoyoverse APIs
• Discord Webhook
• Telegram API
• Google App Script (alternative deployment)
Top Layer: User Interface/Entry Points
Middle Layer: Core Business Logic
Bottom Layer: External Services Integration
Component Relationships
a. Core Components:
• Command Handler (commands/) → HoyoLab Modules
• Cron Jobs (crons/) → Game-specific Tasks
• Platform Integration (platforms/) → Notification Delivery
• HoyoLab Client (gots/) → API Communication
b. Game-Specific Modules:
• Genshin Impact Module
• Honkai: Star Rail Module
• Honkai Impact 3rd Module
• Tears of Themis Module
• Zenless Zone Zero Module
Specific Implementation Details
a. Service Architecture:
Command Handler → Game Module → HoyoLab Client → External API
• ↑ ↓
Cron Manager ←→ Notification System
b. Data Flow:
• How commands flow from user input through the system
• How cron jobs trigger automated tasks
• Demonstrate notification dispatch paths
Key Features to Emphasize
• Multi-game support architecture
• Automated task scheduling system
• Notification delivery pipeline
• Code redemption flow
• Check-in automation process
┌─ User Interface Layer ─┐
• Discord │
• Telegram │
• Webhook │
• ┘
• ↓
┌─ Core Services ───────┐
• Command Handler │
• Cron Manager │
• Game Modules │
• ┘
• ↓
┌─ External Integration ┐
• HoyoLab API │
• Notification APIs │
• ┘
Additional Notes
• Version/configuration management flow
• Error handling paths
• Caching mechanisms