How faberuser/sprk works
SPRK combines a real-time RPG client, a Rust private-server backend, and a Windows launcher that selects a server and installs signed client updates. The principal player workflow is choosing a server in the launcher, updating the game from that server’s update service, then playing against the game server. The graph preserves documented game domains and sampled server/API and account-state layers. Several client domains and server routes are represented by enclosing directories because their implementations were not sampled; edges are limited to documented or indexed relationships.
Main entry points: db.rs Database access · Program.cs Windows launcher · main.rs Server runtime · UpdateEngine.cs Update engine
Components 18
Launcher and updates
- Windows launcher
client/launcher/SprkLauncher/Program.cs - Server profiles
client/launcher/SprkLauncher/ServerManagerForm.cs - Update engine
client/launcher/SprkLauncher.Core/UpdateEngine.cs - Client update service
Game client
- RPG client
client/managed/Assembly-CSharp - Heroes and equipment
client/managed/Assembly-CSharp/NShared - Preset storage UI
client/managed/Assembly-CSharp/NGame2.NUI.NComponent2/HeroEquipStoragePanel.cs - Storage requests
client/managed/Assembly-CSharp/NGame2.NUI.NManager/HeroPresetStorageWebManager.cs
Game server
- Game API
server/src/api - Campaign handlers
server/src/api/battle/campaign_handlers.rs - Storage APIs
server/src/api/extensions/storage.rs - System APIs
server/src/api/system - Server runtime
server/src/main.rs - Database access
server/src/db.rs - PostgreSQL
server/src/database.rs
Account and persistence
- Account managers
client/managed/Assembly-CSharp/NGame2.NAccount/AccountManager.cs - Equipment presets
client/managed/Assembly-CSharp/NGame2.NAccount/UserEquipPresetStorageManager.cs
Other components
- Player
Connections 13
- Player → Windows launcher: starts
README.md - Windows launcher → Server profiles: manages servers
client/launcher/SprkLauncher/ServerManagerForm.cs - Windows launcher → Update engine: installs updates
client/launcher/SprkLauncher/Program.cs - Update engine → Client update service: downloads manifest and files
client/launcher/SprkLauncher.Core/UpdateEngine.cs - Player → RPG client: plays
README.md - Storage requests → Equipment presets: applies responses
client/managed/Assembly-CSharp/NGame2.NUI.NManager/HeroPresetStorageWebManager.cs - RPG client → Account managers: uses account state
client/managed/Assembly-CSharp/NGame2.NUI.NManager/HeroPresetStorageWebManager.cs - Server runtime → Game API: mounts APIs
server/src/main.rs - Server runtime → Database access: initializes database access
server/src/main.rs - Campaign handlers → Database access: uses database
server/src/api/battle/campaign_handlers.rs - Storage APIs → Database access: uses database
server/src/api/extensions/storage.rs - System APIs → Database access: uses database
server/src/api/system/storage.rs - Database access → PostgreSQL: persists game data
server/src/database.rs