How darkflameuniverse/darkflameserver works
Main Components Overview
The system consists of several key server components that should be represented as distinct blocks:
a. Server Components:
• AuthServer (Authentication)
• ChatServer (Chat services)
• MasterServer (Central coordination)
• WorldServer (Game world management)
b. Database Layer:
• Two database options:
• MariaDB/MySQL
• SQLite
• Both CDClient database and Game database
c. Core Systems:
• Entity Management
• Component System
• Networking Layer (RakNet)
• Game Systems (Missions, Inventory, etc.)
Architectural Patterns
• Use a layered architecture approach
• Clear separation between server components
• Database interactions
• Component-based game object system
Detailed Component Breakdown
Top Level:
[Client] <---> [Auth Server] <---> [Master Server] <---> [World Server]
• ^
• [Chat Server]
Database Layer:
[Game Database] [CDClient Database]
• ^ ^
[Database Abstraction Layer]
Game Systems:
[Entity Manager]
• ^
[Component System] --- [Behaviors]
[Game Systems]
• Inventory
• Missions
• Characters
• Combat
• etc.
Connection Types
Different types of connections:
• TCP/UDP connections (networking)
• Database connections
• Internal system communications
• Component relationships
Important Details
• Port numbers for different servers
• Database connection points
• File system interactions
• Client connection flow
• Authentication flow
• Game state management
Specific Implementation Notes
Notes for:
• RakNet implementation for networking
• Component-based architecture
• Database migration system
• Configuration management
• Script system integration