Global Systems
This area covers optional services that could coordinate approved information beyond one local server.
What it is
Global systems are the optional parts of ADK that could help information survive beyond one moment, one restart, or one game server. They include saved records, accounts and access, privacy tools, approved cross-server coordination through ADC, and selected long-running economic information.
Why it matters
Some features need continuity, but central services should not quietly become the ruler of every connected server. Local administrators remain responsible for local gameplay and decide which approved information may cross the boundary.
A simple example
A player could ask a central service to help send a privacy request to several servers they visited. Each server owner would still review the local request and remain responsible for the lawful result. The central service helps carry the paperwork; it does not arrive wearing a crown.
Where it stands today
These services are designs for later stages. The first local framework must not depend on an always-available central service, and no public page should be read as a promise that such a service is operating today.
Saving and Sharing Logs
Live logs use compact numeric references so they do not slow down gameplay. When logs are archived, this service rewrites them into a stable format.
It can replace local player and server references before approved information is shared with ADC. Removing names helps, but the service also checks whether timing or unusual behavior could still identify someone.
Keeping Query Results for Later Use
Some game queries only last as long as they are needed. When a feature needs to keep a record of a query result, this service can save that information.
It stores the result with details about where it came from and how long it should be kept. It does not make the saved result the final truth. The original data still controls what happens in the game.
This service builds typed records with purpose, source versions, age, validity, and retention rules for approved features that need history. Those summaries still cannot ban a player or replace their source data.
Letting Plugins Store Data Easily
Plugins can describe what data they need and use simple functions to read or change it. The framework decides how that data is stored—whether in memory, files, a journal, or a database.
Plugins do not need to handle passwords, SQL commands, file backups, or caching. These tasks stay with the framework so plugin developers can focus on their feature instead of managing storage.
ADK is designed to let plugins describe the information they need and use standard functions to read or change it. The framework would decide whether that information belongs in memory, files, a journal, or a database.
From Suspicion to Recovery
ADK's planned Account Compromise Guardian would help a player react when an unfamiliar session, unusual location, or major playstyle change suggests that somebody else may be using the account. Depending on the protection mode the player chose, it could issue an independent security challenge or temporarily protect the account while the owner verifies what happened.
Suspicion would remain suspicion rather than becoming automatic guilt. Evidence, challenges, temporary protection, local enforcement, and case history have separate owners so one uncertain signal cannot quietly become punishment. The design does not promise that a platform or game provider will reverse a ban.
Signals That An Account May Be In Different Hands
ADK can compare a current play session with the account owner's established patterns. A new network, unusual play time, very different playstyle, failed security challenge, or approved device-context signal may raise concern. None proves who is using the account by itself.
For example, playing from a travel laptop may look unfamiliar but remain legitimate. A new country, radically different behavior, incompatible session timing, and an unanswered independent challenge together are much stronger evidence.
Clear Prices And Temporary Access
Developers may publish a base price and may grant gifts, trials, review copies, or temporary promotions through the same entitlement system. ADK records what was offered and which kind of access was granted without pretending every paid product is a subscription.
The payment provider handles supported currencies, conversion, tax collection, and payment processing. ADK does not maintain its own exchange-rate market for the first commercial version.