How dustywusty/dmud works
Main Components
A. Network Layer
• TCP Server
• WebSocket Server
• Client Connections Handler
B. ECS Core
• World Manager
• Entity Manager
• Component Manager
• System Manager
C. Game Systems
• Combat System
• Movement System
• Spawn System
D. Components
• Health
• Combat
• Movement
• NPC
• Player
• Room
• Spawn
E. Game Logic
• Chat Handler
• Combat Manager
• Movement Manager
• Game State Manager
F. Resource Management
• Room Definitions (rooms.json)
• Configuration
• [Client Connections]
• ↕
• [Network Layer]
• ↕
• [Game Logic Layer]
• ↕
• [ECS Core]
• ↕
• [Systems & Components]
• ↕
• [Resource Layer]
Component Relationships
a) Network Flow:
• TCP/WebSocket clients → Server
• Server → Game Logic
b) ECS Relationships:
• World → Entities
• Entities → Components
• Systems → Components
c) Game Logic Flow:
• Game Manager → Systems
• Systems → Components
• Resource Manager → Game Logic
Specific Implementation Details
Important architectural elements:
a) Component System:
• [Component Manager]
• Health
• Combat
• Movement
• NPC
• Player
• Room
• Spawn
b) System Pipeline:
• [System Manager]
• Combat System
• Movement System
• Spawn System
Technical Details to Highlight
• Go-specific implementations
• Concurrent operations
• Resource loading and management
• State management within the ECS