Safe Plugin Runtime

These notes explain where plugin code runs and how ADK keeps one plugin from interfering with another plugin or the game server.

The runtime gives plugins approved capabilities, time limits, memory limits, and clear failure handling. A plugin can request useful work without receiving unrestricted access to the rest of the system.

Plugin Execution Host

The Plugin Execution Host is the Brain service that runs plugin code under control of the scheduler. It gives plugins approved inputs and output channels. It does not let plugin code change system state or act as host authority. The host handles failures and keeps the core system safe.

Plugin Execution Boundary

Plugins run with limited access to the framework. They may only receive approved inputs and send approved outputs. Plugin code cannot change Warehouse state directly. It cannot control host objects or interact with other plugins. The framework handles scheduling. Pinky enforces this boundary during plugin execution. This keeps plugin behavior safe and predictable.