About

ADK is being built by Peter Fibæk, who also uses the long-running creative name LordHellFire.

Where the idea came from

The project grew from years of interest in modded game servers and Rust plugin development. Large plugin collections can be difficult to understand because every plugin may save data, change settings, and react to the same event in its own way.

The approach

ADK explores a model where plugins declare what they need and request outcomes through shared framework services. The framework would handle common work such as settings, saved data, permissions, validation, searches, and conflict reporting.

For example, if one plugin enables infinite ammunition while another gives one special weapon limited ammunition, the administrator should see the disagreement and choose the intended exception. “Whichever plugin ran last” is not much of a design philosophy.

The ambition

The immediate goal is one useful plugin framework for one supported game. If that succeeds, the same foundations could later support more games and more ambitious systems: living worlds, adaptable NPCs, linked events, and administration tools that understand how features affect one another.

The honest status

ADK is still being designed. The project has extensive notes, contracts, research, and examples, but no usable framework or working game integration yet. The public site explains what is intended and why; it is not a product catalogue wearing a hard hat.

Peter works full time in municipal IT while developing ADK as a long-running engineering project.