Global Systems
These notes describe services that outlive one gameplay tick or one local server. They cover durable persistence, identity and access, privacy and compliance, cross-server coordination through ADC, and global economic records.
Local gameplay remains locally governed. Central services coordinate approved information and continuity without silently taking control of a server's live decisions.
Preparing Logs For Storage And Sharing
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.
Saving an Answer Without Pretending It Is Truth
Most query answers disappear after use. When an approved feature needs history, this service can save a separate typed record with its purpose, source versions, age, validity, and retention rules.
For example, a weekly trend report may read seven durable daily summaries instead of keeping seven days of live query memory. Those summaries still cannot ban a player or replace their source data.
Plugin Data Without Database Code
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.
A plugin would not need database passwords, SQL, storage-file handling, backup logic, or cache management. Those remain framework responsibilities, allowing the plugin developer to concentrate on the feature rather than rebuilding persistence.
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 chosen by the player, the system could issue an independent security challenge or temporarily protect the account while the owner verifies what happened.
Suspicion would not be treated as guilt. Evidence, challenge, 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.