How mongodb-developer/leafsteroids works
Leafsteroids is a multiplayer arcade game with a Blazor website and ASP.NET API backed by MongoDB Atlas. The documented player workflow is to choose an event, play and submit a timed run, then compare scores and gameplay-style similarities. The sampled API shows recording creation and vector-based similarity search, plus player and event lookup. The README documents the game client and real-time scoreboards, but their implementation is not present in the supplied tree; website-to-API wiring is likewise not shown, so those relationships are not asserted as verified.
Main entry points: PlayersController.cs Player Lookup · RecordingsController.cs Run Submission · EventsController.cs Event Management · BaseController.cs Database Access
Components 20
Website
- Blazor Website
website/Program.cs - REST Client
website/Utils/RestServiceClient.cs - Chart URLs
website/Utils/ChartsUrl.cs
REST API
- API Entry
rest_service/Controllers/RootController.cs - Event Management
rest_service/Controllers/EventsController.cs - Game Configuration
rest_service/Controllers/ConfigsController.cs - Player Lookup
rest_service/Controllers/PlayersController.cs - Run Submission
rest_service/Controllers/RecordingsController.cs - Database Access
rest_service/Controllers/BaseController.cs
Game Data
- Request DTOs
rest_service/Dtos/RequestObjects - Response DTOs
rest_service/Dtos/ResponseObjects - Player Records
rest_service/Entities/Player.cs - Event Records
rest_service/Entities/Event.cs - Recording Records
rest_service/Entities/Recording.cs - Embedded References
rest_service/Entities/RecordingPlayer.cs
Atlas Search
- MongoDB Atlas
- Autocomplete Index
deployment/game_database/search_autocomplete_index.js - Vector Index
deployment/game_database/vector_index.js
Other components
- Player
- Unity Game Client
Connections 29
- Player → Blazor Website: views
- Player → Unity Game Client: plays
- Unity Game Client → Run Submission: submits runs
- Unity Game Client → Event Management: selects event
- Blazor Website → REST Client: uses client
- REST Client → Event Management: HTTP requests
- REST Client → Player Lookup: HTTP requests
- Player → API Entry: checks service
- Event Management → Database Access: inherits access
rest_service/Controllers/EventsController.cs - Game Configuration → Database Access: inherits access
rest_service/Controllers/ConfigsController.cs - Player Lookup → Database Access: inherits access
rest_service/Controllers/PlayersController.cs - Run Submission → Database Access: inherits access
rest_service/Controllers/RecordingsController.cs - Event Management → MongoDB Atlas: reads and writes
rest_service/Controllers/EventsController.cs - Player Lookup → MongoDB Atlas: queries and writes
rest_service/Controllers/PlayersController.cs - Run Submission → MongoDB Atlas: stores and searches
rest_service/Controllers/RecordingsController.cs - Player Lookup → Autocomplete Index: searches index
rest_service/Controllers/PlayersController.cs - Run Submission → Vector Index: vector searches
rest_service/Controllers/RecordingsController.cs - MongoDB Atlas → Autocomplete Index: uses index
- MongoDB Atlas → Vector Index: uses index
- Run Submission → Request DTOs: accepts recording DTO
rest_service/Controllers/RecordingsController.cs - Player Lookup → Request DTOs: accepts player DTO
rest_service/Controllers/PlayersController.cs - Event Management → Request DTOs: accepts event DTO
rest_service/Controllers/EventsController.cs - Player Lookup → Response DTOs: returns player data
rest_service/Controllers/PlayersController.cs - Event Management → Response DTOs: returns event data
rest_service/Controllers/EventsController.cs - Run Submission → Response DTOs: returns similarity data
rest_service/Controllers/RecordingsController.cs - Run Submission → Recording Records: creates runs
rest_service/Controllers/RecordingsController.cs - Recording Records → Embedded References: embeds player and event
rest_service/Entities/Recording.cs - Player Lookup → Player Records: queries player records
rest_service/Controllers/PlayersController.cs - Event Management → Event Records: queries event records
rest_service/Controllers/EventsController.cs