Plugins and Orchestrations

This service prepares sealed evidence packages for independent review. Player and server identifiers are removed or replaced while the facts and context needed to judge the case are kept.

Redaction reduces identity exposure but does not hide that unusual events might still be recognizable indirectly. Review access remains scoped and audited.

ADK is designed to let authorized administrators select an NPC and see a short explanation of what it considered and why it chose an action. The trace could appear above the NPC or in an administrator-only panel without changing the decision itself.

For example, an administrator could see that an NPC ran into danger because fear outweighed its estimated chance of reaching cover—not merely receive the unhelpful diagnosis "AI did something weird."

Administrators can approve a setting, profile, event window, maintenance action, or other registered operation to happen later or recur on a schedule. Approval happens when the schedule is created, so the framework does not need an administrator to return every Friday evening and press the same button.

For example, a server may use PvE rules during the week, activate broader PvP on Friday evening, enable a final purge before wipe, and restore its ordinary profile when the new wipe starts.

When an administrator leaves, changes role, retires, becomes compromised, or is removed for abuse, ADK immediately ends their administrative access and starts a reason-appropriate review. Work they requested but which has not started is paused until another authorized administrator accepts, transfers, or rejects it. The review also highlights what they did during the previous 24 hours so recent changes are easy to inspect.

Scheduled work and other continuing responsibilities can be transferred to another administrator or to the server-owning organization, or cancelled where they should not continue.

The historical record still shows who originally created and approved each action. Retirement may optionally be recognized through a former-administrator service record or server-local appreciation benefits, while abuse or compromise triggers a much broader review.

A far-future administrator workspace may show what factions, NPCs, players, active battles, and likely story triggers are doing across the map. An administrator could inspect an NPC's current targets, understand why a battle is leaning one way, and deliberately nudge an event or character when the unfolding story no longer suits the server.

It is a director's control room, not an all-seeing power silently given to ordinary moderators. Every view and intervention remains permission-bound, temporary where possible, and attributable to the administrator who used it.

ADK is designed to let an administrator create an isolated test version of approved server configuration and plugin state. Software inside the test environment may behave as though it is changing the server, while production data remains unreachable.

This could be used to compare a proposed plugin version with the current one or exercise a risky configuration before deployment. Results and reports may leave the sandbox; test mutations do not flow back into production.

This service collects player feedback and game data. It creates aggregate reports for admins. The system focuses on what players do, not why. Personal details are kept private. Reports show patterns over time.

ADK is designed to add missions, faction behavior, maintenance, sabotage, and other consequences to an island power grid. When a game already supplies a suitable grid, ADK would observe and augment it instead of building a competing electrical simulation.

For example, repairing a native power station could change which monuments receive power, attract faction patrols, or create a sabotage objective. A framework-owned fallback would be considered only for hosts that lack the required native capability.

ADK's planned raid-policy service would let a server define when raids are allowed and which optional protections, online-engagement incentives, and frequency limits apply. It would explain each decision while coordinating existing damage, evidence, reward, quota, and notification systems rather than replacing them.

For example, a server might enable a gradually reduced protection curve after every eligible defender has been offline for a while. The same policy could explain the current protection, notify affected players, and preserve a timeline for later review.

Standing on an active recycler quickly harms and then kills a player rather than merely downing them. The player's carried items are immediately recycled into components with a high loss.

Someone who stops the recycler within three seconds may still save the player.

ADK's planned matchmaking service would help players find collaborators who fit their group. It uses voluntary preferences, declared needs, and playstyle signals. A raid group could ask for builders, electricians, vehicle specialists, or calmer players rather than just asking for more humans.

Players decide when they are looking and what their profiles may show. The system does not publish a listing automatically, force pairings, or turn behavior into a moral score. It explains a proposed match and requires the relevant players to accept it.

Administrators can mark areas as graveyard zones. When players die nearby, one tombstone may form from the death. Night rules might later turn that tombstone into a ghost, zombie, or species-specific continuation.

Tombstones created this way do not copy inventories. Killing the continuation does not create another grave. The system only applies these effects under specific conditions and does not change how players normally die.

A plugin may tell a longer story through several missions and events without keeping one enormous event running for an entire wipe. This service remembers which stages have been reached and which verified results unlock the next stage.

For example, finding a terminal card, meeting a trader in a moving hideout, and completing a raid can remain three separate scenarios with their own cleanup. A small progression record connects them. It does not award items, change reputation, or decide dialogue by itself; those systems confirm their own results.

ADK is designed to let a scenario describe its participants, phases, objectives, scoring, restrictions, and cleanup without rebuilding the supporting machinery for every event.

The same search, navigation, escort, or survival ability could support both a persistent world event and an isolated arcade-style minigame while keeping their consequences separate. Official scenarios may expose chosen extension points for optional objectives, presentation, rewards, or side encounters. A developer who wants deeper changes may instead fork an openly licensed recipe into a clearly separate version.

World events may be discovered through witnesses, rumours, visible preparations, or consequences instead of a global announcement. Minigame notices can be opt-in, and the same composition may represent one short local incident or a much larger seasonal story.

ADK is designed to support an anomaly that shifts between a faint spectral presence and a fully physical zombie. What players see, hear, and can affect would change with the creature’s current state, its rising rage, nearby conditions, and the tools used against it.

The orchestration would coordinate those transitions without secretly owning player health, enemy statistics, inventory, or environmental truth. A failed crossing might be interrupted and produce a bounded consequence; a successful one would create one properly accounted-for physical threat, not a duplicated ghost with paperwork problems.

ADK is designed to let past events and remembered characters leave carefully limited spectral traces. A ghostly figure could repeat fragments of an old patrol, react to a place associated with its memory, or whisper a piece of local history only when a player comes close enough to hear it.

The anomaly would coordinate approved memory, sound, and visual effects without rewriting the world's established history. Suppression effects and proximity limits could keep spectral activity rare enough to remain unsettling rather than turning every monument into a paranormal staff meeting.