Interactive diagrams

Each diagram is authored as a small JSON spec in docs/diagrams/src and rendered with Archify. Drag to pan, scroll to zoom, and try the guided views across the top of each one.

Framework layers and the dependency rule

InteractiveClick a box to see the source files behind it (pinned to a commit).Open full screen ↗

From a wire packet to a plugin event

InteractiveNetwork-thread parsing, then the main-thread fan-out to plugins.Open full screen ↗

Plugin lifecycle

InteractiveDiscovery, construction, disable/enable, constructor failure and retry.Open full screen ↗

Ecosystem — from pull request to players

InteractiveCI, the release gate, the CDN, NuGet and the launcher.Open full screen ↗

Two ways to install — launcher or manual

InteractiveWhat each path puts in your game folder.Open full screen ↗

Two build paths — CI stubs or your own game

InteractiveBuild without the game like CI does, or against your client to test in game.Open full screen ↗

What proves a change — local, CI, release gate

InteractiveWhat CI proves, what it cannot, and the in-game release gate.Open full screen ↗

Editing a diagram

Edit the JSON under docs/diagrams/src/, then run docs/diagrams/build.sh --svg to re-validate every diagram, re-render the interactive versions and refresh the committed SVGs. See docs/diagrams/README.md.