Kestrel Player Portal

This keeps unfinished admin forms as drafts. A copy in the browser protects against accidental refreshes or navigation, and a server version tied to an account lets the same person continue from another browser. Drafts never apply changes or actions on their own.

This gives each administrator a small page with the controls and links they use most. Items can show up automatically, or admins can add or remove them. It cuts down on menu digging without changing permissions or making dangerous actions easier to do by accident.

This optional service adds safe links between related administration records. An administrator can move from a player in a case list to that player’s information page, or from a schema to its configuration page, without making every page preload all related data. Web links may open in a new tab so unfinished input remains in place.

ADK is designed to let existing dashboards and server-management platforms use approved information and clearly defined actions without receiving the broad command access of RCON. External suppliers may build adapters against versioned ADK information and operations.

ADK checks identity, permission scope, expiry, and current safety before the system that owns an action decides whether anything changes. For example, a dashboard may read plugin health or request a plugin unload. It cannot send arbitrary command text, read secrets, or write directly to game or framework storage.

This service offers several guided setup tracks for common server goals. It explains the administrator’s real choices and adapts each lesson to the settings they select. Completing a tutorial therefore produces a useful configuration instead of a disposable tutorial example. Tutorial mode can be disabled at any time.

Kestrel presents one consistent pattern for approvals, conflicts, migrations, permission grants, configuration choices, and other administrative decisions. The service shows what will happen, records that a request is pending, and waits for the owning framework service to report the real outcome.

For example, disabling a schema can show which plugins will degrade before the administrator confirms it. The screen changes only after the responsible service accepts or rejects the request.

Kestrel is ADK’s deployable administration and web subsystem. One Kestrel deployment may serve one local framework or many tenant-isolated remote frameworks. Its web boundary renders approved projections, collects authenticated requests, and submits structured intents, but HTTP handlers never change Warehouse, Pinky, plugin state, host settings, files, or processes directly.

Example: A dashboard sends an authenticated request through Kestrel, which submits an intent instead of changing Warehouse or Pinky state directly.

Kestrel shows queue pressure, stale information, degraded services, active fallbacks, and the plugin or subsystem responsible. Diagnostic buttons submit approved requests and remain pending until the owning service confirms what happened.

For example, an administrator may start five minutes of detailed sampling for one misbehaving plugin, but the page cannot execute arbitrary code or expose unrelated player information.

This service presents approved faction economy summaries, shortages, reservations, obligations, and alerts. It does not own the resources or let a dashboard manufacture them.

For example, an administrator may see that ammunition reservations exceed verified stock, but a correction still needs a previewed, audited request accepted by the economy owner.

A hosting company can run one Kestrel portal for many separate ADK game servers. Administrators and players select the server they are allowed to use, while every framework still decides its own permissions and changes. Public per-server Kestrel instances may receive a secure browser handoff; private instances can remain behind an authenticated framework connection.

For example, one hosting dashboard can list twenty Rust servers without giving an administrator of Server A access to Server B.

This service builds consistent admin settings pages from declared metadata. Plugins describe their options, grouping, permissions, and help text without each developer writing a separate web interface.

For example, declaring a bounded difficulty setting can automatically produce the appropriate control in Kestrel while the resulting change still passes the normal security and authority checks.

This service gives players a web browser view of personal, server, privacy, support, and companion-audio info. It lets players submit structured requests. It does not let players control gameplay or system settings.

ADK can infer much of a plugin's manifest from its declared functions and schemas. This developer tool shows those inferences, asks only about choices the code cannot prove, and previews how the plugin behaves when permissions or host capabilities are missing.

For example, it can explain that a spatial query implies location-read access, then simulate pathfinding being unavailable to verify the plugin's declared fallback.