Support persistent residents with normal resurrection and closer companions
Core tests / core (push) Successful in 2m54s
Core tests / core (push) Successful in 2m54s
This commit is contained in:
@@ -36,9 +36,14 @@ and only when fresh and at their class starting level.
|
||||
5. Recreate only the world container with `docker compose up -d --no-deps ac-worldserver`.
|
||||
6. Restart the ALE relay to load priority delivery for permanent-death events.
|
||||
|
||||
The guard is enabled by installing its Lua file, independently of the dashboard
|
||||
hardcore toggle. Remove the guard and recreate the world before intentionally
|
||||
switching back to non-hardcore play. Do not erase the registry to recycle deaths.
|
||||
The installed guard reads `acore_auth.azerothai_realm_rules.hardcore`, synchronized
|
||||
from the dashboard setting by the operations agent (normally within one minute).
|
||||
When disabled, future deaths use the native playerbot resurrection behavior:
|
||||
identities, memories, gear, and party membership survive. Dead active residents
|
||||
still occupy their faction slots, so a recoverable death cannot spawn a replacement
|
||||
or bypass the 50-bot cap. Historical permanent retirements remain retired.
|
||||
For an immediate mode switch, update the dashboard first and synchronize the
|
||||
native rule before declaring the transition complete. Do not erase the registry.
|
||||
|
||||
## Verification and recovery
|
||||
|
||||
|
||||
Reference in New Issue
Block a user