How smcameron/space-nerds-in-space works
Main Components
a. Core Server Components:
• Lobby Server (handles client-server discovery)
• Multiverse Server (manages player ship data across systems)
• Game Server (manages individual solar system instances)
• Server Tracker (coordinates multiple server instances)
b. Client Components:
• Main Game Client
• Limited Client (non-OpenGL version)
• Multiple Bridge Stations:
• Navigation
• Weapons
• Engineering
• Damage Control
• Communications
• Science
• Game Master
c. Asset Management:
• 3D Models
• Textures
• Sounds
• Shaders
• Solar System Configurations
d. Scripting System:
• Lua Script Engine
• Mission Scripts
• Interactive Fiction System
Component Relationships
• Clients ←→ Lobby Server (initial connection)
• Lobby Server ←→ Game Servers (registration)
• Clients ←→ Game Server (gameplay)
• Game Servers ←→ Multiverse Server (ship data sync)
• Lua Script Engine ←→ Game Server (mission control)
Technical Implementation Details
Specialized subsystems:
Network Layer:
• Socket I/O (snis_socket_io)
• Protocol Handling (snis_packet.h)
• Bridge Updates (snis_bridge_update_packet)
Graphics Pipeline:
• OpenGL Rendering
• Shader Management
• Model Loading
• Texture Handling
Audio System:
• Voice Chat
• Sound Effects
• Text-to-Speech
Top Layer:
• Client Applications
• User Interface Components
Middle Layer:
• Network Communication
• Game Logic
• Physics Engine
Bottom Layer:
• Asset Management
• Data Storage
• System Configuration
Additional Elements
Annotations for:
• Network protocols and data flow
• Asset loading paths
• Bridge station interactions
• Solar system instance management
• Voice chat and audio routing
Implementation Notes
• The distributed nature of the system
• Real-time networking requirements
• Multiple bridge station coordination
• Asset management and loading
• Mission scripting integration
This system design should reflect SNIS's architecture as a multiplayer space simulation game with multiple coordinated interfaces and real-time networking requirements.