How ADK Fits Together

ADK sits between game-server plugins and the game engine.

Pinky is the small bridge that lives close to the engine. It observes game events and applies approved actions, but it does not decide plugin rules.

Brain runs outside the engine. It owns framework reasoning, live data, scheduling, validation, and the final ordering of accepted changes. Plugins run within controlled boundaries and submit requests called intents instead of directly changing authoritative state.

Shared services handle work that plugins commonly rebuild for themselves, such as settings, persistence, permissions, user interfaces, searches, external communication, and diagnostics. This gives developers simpler calls and gives administrators one place to understand access and conflicts.

For example, a plugin can ask for "all players currently inside this zone." If that search becomes common, ADK may keep the answer updated continuously so every plugin can read it cheaply without changing the plugin's normal query.

Optional ADC services can coordinate approved identity, distribution, and cross-server information. A local server should still keep running when those central services are unavailable.