ADK Terminology
ADK uses a few recurring names for different parts of the framework. The distinctions matter: Brain makes framework decisions, while Pinky stays close to the game engine and performs only its narrow integration work....
About
ADK is being built by Peter Fibaek, who also uses the long-running creative name LordHellFire.
The project grew from years of interest in modded game servers and Rust plugin development. Large plugin collections can be difficult to trust because every plugin may store data, change settings, and react to the same events in its own way.
ADK explores a different model. Plugins declare what they need and request outcomes through shared framework services. The framework owns common work such as configuration, persistence, permissions, validation, queries, compatibility, and conflict reporting.
For example, if one plugin enables infinite ammunition globally while another wants one weapon to use limited ammunition, the administrator should see a clear compatibility notice and choose the intended exception instead of discovering the conflict during gameplay.
The immediate goal is one powerful plugin framework. The longer-term possibility is a reusable gameplay-logic layer that lets game engines focus more on performing approved actions than independently deciding every system rule.
Peter works full time in municipal IT while developing ADK as a long-running engineering project.
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...
How ADK Talks About Its Differences
ADK deliberately separates familiar framework building blocks from uncommon implementations and rare combinations. A feature is not called unique merely because the team has not encountered it before; usefulness, safe...
Website Privacy and Feedback
This notice covers the feedback and reaction features on Agnostic.dk. It does not describe data handling by the future ADK framework or by game servers that may eventually use ADK. Who is responsible Peter Fibaek oper...
What ADK Is Trying to Become
ADK is an experimental framework design for building safer and more structured game-server plugin ecosystems. The project starts from a simple problem: plugin systems become harder to trust as they grow. Each plugin m...
Why Plugin Systems Need Stronger Boundaries
Game-server plugin ecosystems become fragile when many independent systems can change shared behavior without explicit boundaries. At small scale, this often works well enough. A plugin reacts to an event, changes som...