NPC Continuity and Legacy

Local NPCs keep their identity when a server is wiped. This default behavior helps create recognizable characters over time. Server owners can choose how long NPCs last. Options include temporary, long-lived, retired, reset, or purged classes. NPCs do not become global or premium characters.

ADK reduces simulation detail when an NPC is far from observation without freezing that character’s life or running full combat and pathfinding every frame. The NPC could continue through coarse, scheduled activities such as travelling, resting, or shopping while ordinary owners still account for time, risk, goods, and money.

Before the NPC becomes observable again, ADK would reconcile location, identity, lifecycle, and safe physical placement. The character should wake into one consistent life—not teleport between contradictory versions of itself merely because nobody was watching.

ADK’s planned NPC identity system keeps noticing someone separate from knowing who they are. An NPC would gather limited visual and contextual evidence before identifying an unknown person. Concealment could weaken that evidence without becoming guaranteed invisibility.

For example, an NPC might notice a person moving in poor light without recognizing them. A clearer view, familiar equipment, or recognizable behavior could provide enough evidence to identify them later.

This service tracks basic NPC history and possible future roles after death, retirement, or family events. It does not copy memories, items, or skills to new characters. ADC controls this process. The system only saves simple background data. It never makes cloned character copies. Successor ideas must follow approval steps.

This service manages how NPCs live and end their lives. It tracks when they die, return, retire, or are removed from the game. It does not manage their memories or abilities.