# evast9919/lazer-sandbox architecture

> Architecture diagram of the GitHub repository evast9919/lazer-sandbox, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-05-23). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/evast9919/lazer-sandbox
- Repository: https://github.com/evast9919/lazer-sandbox

## Overview

1. **What this repo is**
   - This is a **custom osu!lazer ruleset/plugin** called *Sandbox*. It is not a standalone app; it plugs into the osu! client as a game mode and also contains a matching test project for visual and component tests.

2. **Top-level split: runtime vs tests**
   - The repository is divided into:
     - `osu.Game.Rulesets.Sandbox`: the production ruleset and game content.
     - `osu.Game.Rulesets.Sandbox.Tests`: a test harness with many `TestScene*` scenes.
   - For an architecture diagram, treat the test project as a **separate validation/runtime sandbox** that exercises the same UI and gameplay components under test scenes.

3. **Ruleset integration boundary**
   - Core integration points are:
     - `SandboxRuleset.cs` as the ruleset entry point.
     - `SandboxInputManager.cs` for input handling.
     - `Beatmaps/SandboxBeatmap.cs` and `SandboxBeatmapConverter.cs` for converting osu! beatmaps into this ruleset’s hit objects.
     - `Difficulty/SandboxDifficultyCalculator.cs` for rule-specific difficulty/star computation.
     - `Judgements/SandboxJudgement.cs` and `Objects/SandboxHitObject.cs` / `Objects/Drawables/DrawableSandboxHitObject.cs` for gameplay object lifecycle.
   - This is the main boundary between osu!lazer’s generic framework and Sandbox-specific behavior.

4. **Gameplay model**
   - The ruleset appears to define a generic “sandbox hit object” abstraction and then render/score it via a drawable layer.
   - The flow is: **converted beatmap → sandbox hit objects → drawable hit objects → judgement/scoring**.
   - That pattern is important because it separates **data representation** from **on-screen behavior**.

5. **Screen-level product structure**
   - The repo bundles several distinct experiences under the ruleset:
     - `MainRulesetScreen.cs` for the main sandbox landing page.
     - `FlappyDonScreen.cs` for a Flappy Bird-style mini-game.
     - `NumbersScreen.cs` for number-based gameplay/visualization.
     - `VisualizerScreen.cs` for music visualizer experiences.
     - `RulesetsScreen.cs` for managing downloadable/available rulesets.
   - A useful diagram would show these as **feature screens hosted inside the ruleset shell**.

6. **Shared UI framework**
   - Common UI and overlay pieces live under `UI/` and are reused across screens:
     - `SandboxOverlay`, `SandboxCheckbox`, `SandboxSettings`, `SandboxSettingsSection`, `ColourPickerDropdown`, `SettingsDropdownContainer`.
     - `InteractiveContainer`, `StoryboardContainer`, `TrackController`, `SandboxPlayfield`, `DrawableSandboxRuleset`.
   - These form a shared UI layer that sits above the underlying gameplay/rendering components.

7. **Reusable visual/graphics primitives**
   - `Graphics/` contains reusable containers such as `ContentFitContainer` and `InnerShadowContainer`.
   - The `Resources/Shaders` folder shows custom rendering effects:
     - inner shadow,
     - rounded bars,
     - shared ruleset utility shader code.
   - These are cross-cutting rendering primitives used by multiple screens and widgets rather than isolated game logic.

8. **FlappyDon subsystem**
   - The FlappyDon feature is implemented as a self-contained mini-game:
     - `Components/Bird`, `Obstacles`, `PipeObstacle`, `PipeSprite`, `GroundSprite`, `BackgroundSprite`, `Backdrop`, `FlappyDonGame`, `FlappyDonScalingContainer`.
   - This subsystem has its own composition root (`FlappyDonScreen`) and asset set, so it should be diagrammed as an internally contained game mode within Sandbox.

9. **Numbers subsystem**
   - The Numbers feature is similarly isolated:
     - `DrawableNumber` renders individual numbers.
     - `NumbersPlayfield` manages arrangement/playfield behavior.
     - `NumbersScreen` hosts the experience.
   - This is a lighter-weight feature module, likely focused on animated rendering and interaction rather than full rhythm gameplay.

10. **Visualizer subsystem**
   - The visualizer is the most layered feature area:
     - `VisualizerScreen` hosts it.
     - `Components/LayoutController` switches between layouts.
     - `Layouts/TypeA` and `Layouts/TypeB` define alternate presentation modes.
     - `Visualizers/Circular` and `Visualizers/Linear` define different audio-reactive renderers.
     - `MusicHelpers/` provides beatmap/rate/intensity/amplitude plumbing.
     - `Particles`, `ParticlesDrawable`, and settings sections control additional effects.
   - Data flow here is: **music/beatmap state → music helper providers → layout/controller → drawable visualizer components**.

11. **Rulesets browsing / online integration**
   - `Screens/Rulesets` includes update/download UI:
     - `DrawableLatestRulesetUpdate`, `RulesetDownloadType`, `RulesetPanel`.
   - The `Online/` folder contains `GetLatestReleaseRequest` and `GitHubRelease`, indicating the ruleset can query GitHub releases to detect or present updates.
   - This is the repo’s only clear external-service boundary besides osu!lazer itself.

12. **Configuration and extension layer**
   - `Configuration/SandboxRulesetConfigManager.cs` centralizes ruleset-specific settings storage.
   - `Extensions/` contains shared utilities for math, noise generation, osu! integration helpers, and projectile helpers.
   - These are support libraries that reduce coupling across the feature screens and gameplay components.

13. **Assets and content**
   - Content is bundled with the ruleset:
     - sound samples in `Resources/Samples`,
     - textures for FlappyDon, icons, and visualizer assets,
     - custom shaders.
   - The asset pipeline is therefore an important runtime dependency, not just static decoration.

14. **Testing architecture**
   - The test project mirrors the runtime structure with `TestScene*` classes for:
     - game integration,
     - graphics containers,
     - UI components,
     - visualizer behaviors,
     - FlappyDon and ruleset object tests.
   - This suggests a **component-driven architecture** where most features are testable in isolation as drawable scenes, which is common in osu! framework projects.

15. **How to draw the system**
   - A good architecture diagram would show:
     - **osu!lazer host** at the top,
     - **SandboxRuleset** as the integration layer,
     - branches for **gameplay objects**, **shared UI**, **feature screens**, **visualizer/music helpers**, and **online release lookup**,
     - and a separate **test harness** mirroring those feature areas.
   - The key architectural idea is that Sandbox is a **multi-feature ruleset plugin** with a shared UI/graphics foundation and several self-contained mini-applications under one ruleset.

Main entry points: [`osu.Game.Rulesets.Sandbox.Tests/RulesetTestScene.cs`](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox.Tests/RulesetTestScene.cs) (Test harness), [`osu.Game.Rulesets.Sandbox/SandboxRuleset.cs`](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/SandboxRuleset.cs) (Sandbox ruleset), [`osu.Game.Rulesets.Sandbox/Screens/Main/MainRulesetScreen.cs`](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/Main/MainRulesetScreen.cs) (Main screen), [`osu.Game.Rulesets.Sandbox/UI/DrawableSandboxRuleset.cs`](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/UI/DrawableSandboxRuleset.cs) (Shared UI)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_runtime["Runtime Ruleset"]
  node_host_ruleset["Sandbox ruleset<br/>osu!lazer plugin<br/>[SandboxRuleset.cs]"]
  node_input_manager["Input manager<br/>input layer"]
  node_beatmap_converter["Beatmap converter<br/>conversion"]
  node_sandbox_beatmap["Sandbox beatmap<br/>beatmap model<br/>[SandboxBeatmap.cs]"]
  node_difficulty_calc["Difficulty calc"]
  node_sandbox_hitobject["Hit object<br/>gameplay model"]
  node_drawable_hitobject["Drawable object<br/>gameplay view"]
  node_judgement["Judgement<br/>scoring"]
  node_shared_ui["Shared UI<br/>ui toolkit"]
  node_screens_shell["Screen shell<br/>screen base<br/>[SandboxScreen.cs]"]
  node_main_screen["Main screen<br/>landing screen"]
  node_flappy_screen["FlappyDon<br/>mini-game screen<br/>[FlappyDonScreen.cs]"]
  node_numbers_screen["Numbers<br/>feature screen<br/>[NumbersScreen.cs]"]
  node_visualizer_screen["Visualizer<br/>audio-visual screen"]
  node_rulesets_screen["Rulesets<br/>update screen<br/>[RulesetsScreen.cs]"]
  node_online_updates["Online updates<br/>release lookup"]
  node_config_manager["Config manager<br/>configuration"]
  node_graphics_primitives["Graphics primitives<br/>render helpers"]
  node_visualizer_core["Visualizer core<br/>visualizer subsystem"]
  node_flappy_core["Flappy core<br/>mini-game subsystem<br/>[FlappyDonGame.cs]"]
  node_numbers_core["Numbers core<br/>numbers subsystem"]
end

subgraph group_tests["Test Harness"]
  node_test_harness["Test harness<br/>test project"]
  node_test_ui["UI tests<br/>component tests"]
  node_test_graphics["Graphics tests<br/>component tests"]
  node_test_flappy["Flappy tests<br/>mini-game tests"]
  node_test_numbers["Numbers tests<br/>feature tests"]
  node_test_visualizer["Visualizer tests<br/>feature tests"]
end

node_host_ruleset -->|"creates"| node_input_manager
node_host_ruleset -->|"uses"| node_beatmap_converter
node_host_ruleset -->|"uses"| node_difficulty_calc
node_host_ruleset -->|"hosts"| node_shared_ui
node_host_ruleset -->|"opens"| node_screens_shell
node_beatmap_converter -->|"produces"| node_sandbox_beatmap
node_sandbox_beatmap -->|"contains"| node_sandbox_hitobject
node_sandbox_hitobject -->|"renders as"| node_drawable_hitobject
node_drawable_hitobject -->|"scores via"| node_judgement
node_shared_ui -->|"composes"| node_graphics_primitives
node_shared_ui -->|"reads"| node_config_manager
node_main_screen -->|"uses"| node_shared_ui
node_main_screen -->|"navigates to"| node_flappy_screen
node_main_screen -->|"navigates to"| node_numbers_screen
node_main_screen -->|"navigates to"| node_visualizer_screen
node_main_screen -->|"navigates to"| node_rulesets_screen
node_rulesets_screen -->|"queries"| node_online_updates
node_flappy_screen -->|"hosts"| node_flappy_core
node_numbers_screen -->|"hosts"| node_numbers_core
node_visualizer_screen -->|"hosts"| node_visualizer_core
node_visualizer_core -->|"uses"| node_config_manager
node_visualizer_core -->|"uses"| node_graphics_primitives
node_test_harness -->|"exercises"| node_host_ruleset
node_test_harness -->|"includes"| node_test_ui
node_test_harness -->|"includes"| node_test_graphics
node_test_harness -->|"includes"| node_test_flappy
node_test_harness -->|"includes"| node_test_numbers
node_test_harness -->|"includes"| node_test_visualizer

click node_host_ruleset "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/SandboxRuleset.cs"
click node_input_manager "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/SandboxInputManager.cs"
click node_beatmap_converter "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Beatmaps/SandboxBeatmapConverter.cs"
click node_sandbox_beatmap "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Beatmaps/SandboxBeatmap.cs"
click node_difficulty_calc "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Difficulty/SandboxDifficultyCalculator.cs"
click node_sandbox_hitobject "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Objects/SandboxHitObject.cs"
click node_drawable_hitobject "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Objects/Drawables/DrawableSandboxHitObject.cs"
click node_judgement "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Judgements/SandboxJudgement.cs"
click node_shared_ui "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/UI/DrawableSandboxRuleset.cs"
click node_screens_shell "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/SandboxScreen.cs"
click node_main_screen "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/Main/MainRulesetScreen.cs"
click node_flappy_screen "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/FlappyDon/FlappyDonScreen.cs"
click node_numbers_screen "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/Numbers/NumbersScreen.cs"
click node_visualizer_screen "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/Visualizer/VisualizerScreen.cs"
click node_rulesets_screen "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/Rulesets/RulesetsScreen.cs"
click node_online_updates "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Online/GetLatestReleaseRequest.cs"
click node_config_manager "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Configuration/SandboxRulesetConfigManager.cs"
click node_graphics_primitives "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Graphics/ContentFitContainer.cs"
click node_visualizer_core "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/Visualizer/Components/LayoutController.cs"
click node_flappy_core "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/FlappyDon/Components/FlappyDonGame.cs"
click node_numbers_core "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/Numbers/Components/NumbersPlayfield.cs"
click node_test_harness "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox.Tests/RulesetTestScene.cs"
click node_test_ui "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox.Tests/UI/TestSceneSandboxOverlay.cs"
click node_test_graphics "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox.Tests/Graphics/TestSceneInnerShadowContainer.cs"
click node_test_flappy "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox.Tests/FlappyDon/TestSceneFlappyDonGame.cs"
click node_test_numbers "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox.Tests/NumbersGame/TestSceneNumbersPlayfield.cs"
click node_test_visualizer "https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox.Tests/Visualizer/TestSceneParticles.cs"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_host_ruleset,node_input_manager,node_beatmap_converter,node_sandbox_beatmap,node_difficulty_calc,node_sandbox_hitobject,node_drawable_hitobject,node_judgement,node_shared_ui,node_screens_shell,node_main_screen,node_flappy_screen,node_numbers_screen,node_visualizer_screen,node_rulesets_screen,node_online_updates,node_config_manager,node_graphics_primitives,node_visualizer_core,node_flappy_core,node_numbers_core toneBlue
class node_test_harness,node_test_ui,node_test_graphics,node_test_flappy,node_test_numbers,node_test_visualizer toneAmber
```

## Components

### Runtime Ruleset

Production ruleset, gameplay model, shared UI, and feature screens.

- [Sandbox ruleset](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/SandboxRuleset.cs): osu!lazer plugin · Ruleset entry point wired into the osu! client. · `osu.Game.Rulesets.Sandbox/SandboxRuleset.cs`
- [Input manager](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/SandboxInputManager.cs): input layer · Ruleset-specific input handling and binding. · `osu.Game.Rulesets.Sandbox/SandboxInputManager.cs`
- [Beatmap converter](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Beatmaps/SandboxBeatmapConverter.cs): conversion · Converts osu! beatmaps into Sandbox hit objects. · `osu.Game.Rulesets.Sandbox/Beatmaps/SandboxBeatmapConverter.cs`
- [Sandbox beatmap](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Beatmaps/SandboxBeatmap.cs): beatmap model · Ruleset-specific beatmap representation. · `osu.Game.Rulesets.Sandbox/Beatmaps/SandboxBeatmap.cs`
- [Difficulty calc](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Difficulty/SandboxDifficultyCalculator.cs): difficulty · Computes Sandbox-specific difficulty and star values. · `osu.Game.Rulesets.Sandbox/Difficulty/SandboxDifficultyCalculator.cs`
- [Hit object](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Objects/SandboxHitObject.cs): gameplay model · Core Sandbox gameplay object abstraction. · `osu.Game.Rulesets.Sandbox/Objects/SandboxHitObject.cs`
- [Drawable object](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Objects/Drawables/DrawableSandboxHitObject.cs): gameplay view · Visual and interactive rendering for Sandbox hit objects. · `osu.Game.Rulesets.Sandbox/Objects/Drawables/DrawableSandboxHitObject.cs`
- [Judgement](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Judgements/SandboxJudgement.cs): scoring · Ruleset judgement and score resolution. · `osu.Game.Rulesets.Sandbox/Judgements/SandboxJudgement.cs`
- [Shared UI](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/UI/DrawableSandboxRuleset.cs): ui toolkit · Reusable overlays, playfield containers, settings, and interaction helpers. · `osu.Game.Rulesets.Sandbox/UI/DrawableSandboxRuleset.cs`
- [Screen shell](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/SandboxScreen.cs): screen base · Common screen base classes for the ruleset experience. · `osu.Game.Rulesets.Sandbox/Screens/SandboxScreen.cs`
- [Main screen](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/Main/MainRulesetScreen.cs): landing screen · Main Sandbox landing page and entry hub. · `osu.Game.Rulesets.Sandbox/Screens/Main/MainRulesetScreen.cs`
- [FlappyDon](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/FlappyDon/FlappyDonScreen.cs): mini-game screen · Self-contained Flappy Bird-style feature screen. · `osu.Game.Rulesets.Sandbox/Screens/FlappyDon/FlappyDonScreen.cs`
- [Numbers](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/Numbers/NumbersScreen.cs): feature screen · Number-based gameplay and visualization screen. · `osu.Game.Rulesets.Sandbox/Screens/Numbers/NumbersScreen.cs`
- [Visualizer](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/Visualizer/VisualizerScreen.cs): audio-visual screen · Audio-reactive visualizer experience with layouts and effects. · `osu.Game.Rulesets.Sandbox/Screens/Visualizer/VisualizerScreen.cs`
- [Rulesets](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/Rulesets/RulesetsScreen.cs): update screen · Ruleset browsing and release/update presentation. · `osu.Game.Rulesets.Sandbox/Screens/Rulesets/RulesetsScreen.cs`
- [Online updates](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Online/GetLatestReleaseRequest.cs): release lookup · GitHub release request and release metadata handling. · `osu.Game.Rulesets.Sandbox/Online/GetLatestReleaseRequest.cs`
- [Config manager](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Configuration/SandboxRulesetConfigManager.cs): configuration · Central storage for ruleset-specific settings. · `osu.Game.Rulesets.Sandbox/Configuration/SandboxRulesetConfigManager.cs`
- [Graphics primitives](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Graphics/ContentFitContainer.cs): render helpers · Reusable visual containers such as content fitting and inner shadows. · `osu.Game.Rulesets.Sandbox/Graphics/ContentFitContainer.cs`
- [Visualizer core](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/Visualizer/Components/LayoutController.cs): visualizer subsystem · Layout controller, music helpers, particle effects, and visualizer renderers. · `osu.Game.Rulesets.Sandbox/Screens/Visualizer/Components/LayoutController.cs`
- [Flappy core](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/FlappyDon/Components/FlappyDonGame.cs): mini-game subsystem · Bird, obstacles, sprites, and scaling container for FlappyDon. · `osu.Game.Rulesets.Sandbox/Screens/FlappyDon/Components/FlappyDonGame.cs`
- [Numbers core](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox/Screens/Numbers/Components/NumbersPlayfield.cs): numbers subsystem · Drawable number and playfield logic. · `osu.Game.Rulesets.Sandbox/Screens/Numbers/Components/NumbersPlayfield.cs`

### Test Harness

Validation project with drawable and component test scenes.

- [Test harness](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox.Tests/RulesetTestScene.cs): test project · Separate validation runtime with drawable scene-based tests. · `osu.Game.Rulesets.Sandbox.Tests/RulesetTestScene.cs`
- [UI tests](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox.Tests/UI/TestSceneSandboxOverlay.cs): component tests · Test scenes for overlays and interaction containers. · `osu.Game.Rulesets.Sandbox.Tests/UI/TestSceneSandboxOverlay.cs`
- [Graphics tests](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox.Tests/Graphics/TestSceneInnerShadowContainer.cs): component tests · Test scenes for graphics containers and rendering effects. · `osu.Game.Rulesets.Sandbox.Tests/Graphics/TestSceneInnerShadowContainer.cs`
- [Flappy tests](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox.Tests/FlappyDon/TestSceneFlappyDonGame.cs): mini-game tests · Test scenes for FlappyDon gameplay and background components. · `osu.Game.Rulesets.Sandbox.Tests/FlappyDon/TestSceneFlappyDonGame.cs`
- [Numbers tests](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox.Tests/NumbersGame/TestSceneNumbersPlayfield.cs): feature tests · Test scenes for numbers drawable and playfield behavior. · `osu.Game.Rulesets.Sandbox.Tests/NumbersGame/TestSceneNumbersPlayfield.cs`
- [Visualizer tests](https://github.com/evast9919/lazer-sandbox/blob/main/osu.Game.Rulesets.Sandbox.Tests/Visualizer/TestSceneParticles.cs): feature tests · Test scenes for visualizer particles, layout, and settings behavior. · `osu.Game.Rulesets.Sandbox.Tests/Visualizer/TestSceneParticles.cs`

## Connections

- Sandbox ruleset → Input manager: creates · The ruleset installs its input layer.
- Sandbox ruleset → Beatmap converter: uses · Ruleset integration includes beatmap conversion.
- Sandbox ruleset → Difficulty calc: uses · Ruleset integration includes difficulty calculation.
- Sandbox ruleset → Shared UI: hosts · The ruleset renders the shared UI and playfield layer.
- Sandbox ruleset → Screen shell: opens · Main navigation lives under the sandbox screen shell.
- Beatmap converter → Sandbox beatmap: produces · Conversion yields Sandbox beatmap data.
- Sandbox beatmap → Hit object: contains · Beatmaps are composed of Sandbox hit objects.
- Hit object → Drawable object: renders as · Gameplay objects are materialized as drawable hit objects.
- Drawable object → Judgement: scores via · Drawable objects resolve judgements and scoring.
- Shared UI → Graphics primitives: composes · Shared UI builds on reusable rendering containers.
- Shared UI → Config manager: reads · UI surfaces consume centralized ruleset configuration.
- Main screen → Shared UI: uses · Landing page is built from shared UI pieces.
- Main screen → FlappyDon: navigates to · Main screen exposes the FlappyDon experience.
- Main screen → Numbers: navigates to · Main screen exposes the numbers experience.
- Main screen → Visualizer: navigates to · Main screen exposes the visualizer experience.
- Main screen → Rulesets: navigates to · Main screen exposes ruleset browsing and updates.
- Rulesets → Online updates: queries · Ruleset browsing can check GitHub releases.
- FlappyDon → Flappy core: hosts · FlappyDon screen composes its mini-game subsystem.
- Numbers → Numbers core: hosts · Numbers screen composes its playfield subsystem.
- Visualizer → Visualizer core: hosts · Visualizer screen composes layout, music, and effect logic.
- Visualizer core → Config manager: uses · Visualizer settings are driven by ruleset config.
- Visualizer core → Graphics primitives: uses · Visualizer renderers rely on shared graphics helpers.
- Test harness → Sandbox ruleset: exercises · The test project validates the production ruleset behavior.
- Test harness → UI tests: includes · UI scene tests cover overlay and interaction components.
- Test harness → Graphics tests: includes · Graphics scene tests cover rendering primitives.
- Test harness → Flappy tests: includes · FlappyDon scenes validate the mini-game subsystem.
- Test harness → Numbers tests: includes · Numbers scenes validate drawable and playfield behavior.
- Test harness → Visualizer tests: includes · Visualizer scenes validate layouts and effects.
