How salaron/sunlight works
re:Light is a server emulator for Love Live! School Idol Festival. Its principal workflow is a client request entering an API endpoint, passing request checks, invoking account or game services, and returning a response; login authenticates credentials and establishes a session. Other visible product areas include downloads, login bonuses, live play, units, rewards, and user inventory. The graph reflects documented capabilities and source-index references; unsampled handler implementations and runtime wiring are not assumed beyond those references.
Main entry points: ServerContext.cs Player database · UnitService.cs Unit service · Handlers API endpoints · WebApplicationBuilderExtensions.cs Server startup
Components 23
HTTP API
- API endpoints
Server.Endpoints/Handlers - Authorization filter
Server.Endpoints/Filters/AuthorizationFilter.cs - Version filter
Server.Endpoints/Filters/ClientVersionFilter.cs - Auth header
Server.Common/AuthorizeHeader.cs
Accounts & Progress
- Login
Server.Endpoints/Handlers/Login/Login.cs - Auth key repository
Server.Common/Login/AuthKeyRepository.cs - User service
Server.Common/Users/UserService.cs - Login bonuses
Server.Common/LoginBonus/LoginBonusService.cs
Game Features
- Unit service
Server.Common/Units/UnitService.cs - Deck service
Server.Common/Units/UnitDeckService.cs - Items & rewards
Server.Common/Items - Item categories
Server.Database/Enums/AddType.cs - Live features
Server.Endpoints/Handlers/Live - Content downloads
Server.Endpoints/Handlers/Download/Update.cs
Persistence & Runtime
- User record
Server.Database/Server/User.cs - Player database
Server.Database/Server/ServerContext.cs - Unit catalog
Server.Database/Game/UnitContext.cs - Owned units
Server.Database/Server/UnitOwning.cs - Unit album
Server.Database/Server/UnitAlbum.cs - Saved decks
Server.Database/Server/UserUnitDeck.cs - Server configuration
Server.Common/Config/ServerConfig.cs - Server startup
Server/Startup/WebApplicationBuilderExtensions.cs
Other components
- Game client
Connections 21
- Game client → API endpoints: sends requests
- API endpoints → Authorization filter: checks authorization
Server.Endpoints/Filters/AuthorizationFilter.cs - API endpoints → Version filter: checks version
- Authorization filter → Auth header: reads header
Server.Endpoints/Filters/AuthorizationFilter.cs - Login → Auth key repository: gets auth key
Server.Endpoints/Handlers/Login/Login.cs - Login → Player database: looks up user
Server.Endpoints/Handlers/Login/Login.cs - User service → Player database: reads and updates
Server.Common/Users/UserService.cs - User service → User record: maps user data
Server.Common/Users/UserService.cs - Login bonuses → Player database: reads and records
Server.Common/LoginBonus/LoginBonusService.cs - Login bonuses → Server configuration: reads bonus settings
Server.Common/LoginBonus/LoginBonusService.cs - Unit service → Player database: reads unit data
Server.Common/Units/UnitService.cs - Unit service → Owned units: queries ownership
Server.Common/Units/UnitService.cs - Unit service → Unit album: queries album
Server.Common/Units/UnitService.cs - Unit service → Saved decks: uses deck data
Server.Common/Units/UnitService.cs - Deck service → Player database: reads deck data
Server.Common/Units/UnitDeckService.cs - Deck service → Saved decks: uses saved decks
Server.Common/Units/UnitDeckService.cs - Items & rewards → Item categories: classifies items
Server.Database/Enums/AddType.cs - Content downloads → Server configuration: uses download settings
- Server startup → Player database: configures database
Server/Startup/WebApplicationBuilderExtensions.cs - Server startup → Unit catalog: configures database
Server/Startup/WebApplicationBuilderExtensions.cs - Server startup → API endpoints: registers API