Platform Features
This area collects reusable gameplay building blocks that plugins could combine instead of rebuilding alone.
What it is
Platform features are reusable gameplay building blocks that many plugins could share. They cover subjects such as NPC knowledge, combat, communication, inventory, movement, player interfaces, and the shape of connected game spaces.
ADK calls one bounded ability a capability. A capability might let an approved plugin search an area, move an item, present a menu, or request that an NPC considers a goal.
Why it matters
When every plugin rebuilds these systems, the same server can end up with several slightly different ideas of an inventory, a faction, or a safe movement rule. Shared capabilities give developers consistent pieces and give ADK one place to improve performance and safety.
A simple example
An event developer should be able to ask for a guarded delivery without writing a new pathfinder, inventory system, faction model, and user interface from scratch. The interesting part is the event; plumbing is rarely the guest of honour.
Where it stands today
The project documents many possible capabilities so the core can leave room for them. That does not mean they all belong in the first build or will all become first-party features.
Shared Connections to Outside Services
ADK is designed to maintain approved connections to services like Discord or another game and safely share them between separately authorized callers. A caller might be a plugin or an ADK framework service, but each receives only its assigned routes, actions, data, and limits.
Plugins do not get login details or unrestricted network access, and an internal service does not become trusted merely because ADK owns it. Every caller passes its own permission and policy checks before using the shared connector. This lets developers reuse reliable connection handling without quietly installing a side door to the internet, which is generally considered poor interior design.
Coordinating Crafting
This service handles one crafting task at a time. It checks the recipe, holds the exact ingredients, follows current rules, creates the output through normal inventory steps, and prevents duplicates by fixing uncertain results.
Shared Crafting Recipes
This service stores validated recipe definitions using stable item meanings rather than game-specific names. Plugins can add recipes and metadata requirements. A recipe is available only to consumers whose required fields are present, so one plugin cannot disable unrelated crafting just because it needs extra information.
Vehicle-Specific Mounting Rules
ADK has one general attachment service for placing approved equipment on suitable objects. This vehicle service adds the rules that matter specifically when the parent object moves: weight, balance, collision, power, controls, and what the game engine can safely keep attached.
For example, the general service may know that a searchlight fits a standard hardpoint. This service decides whether mounting it on a small boat would block the driver, upset the boat's handling, or require a power connection the boat does not have. Plugins can reuse the same attachment method without each inventing their own suspicious little welding department.
Recording Simulation Events for Review
ADK's planned forensic replay service would preserve an authorized, time-based reconstruction of selected simulation events. Reviewers could follow what the framework observed, which decisions were made, and how an incident unfolded while visible gaps remained explicitly marked.
The replay does not claim to be a complete history, expose unrestricted player data, or assign guilt automatically. It is evidence for an authorized reviewer—not a tiny robotic judge wearing a powdered wig.