Separate looted currency and preserve growing realm state in atomic chunks
Core tests / core (push) Successful in 49s
Core tests / core (push) Successful in 49s
This commit is contained in:
@@ -21,3 +21,5 @@ Recovery Results retains up to 100 attempts. Native follow-up checks position, m
|
||||
Bot Performance reads the native `playerbots pmon tick` JSON export every five minutes. Enable `AiPlayerbot.PerfMonEnabled = 1` in the installed module configuration; on an already-running server, toggle the native profiler once only if it is currently disabled. Deploy `ale/azerothai_outcomes.lua` alongside the existing bridge and recovery scripts. The collector reads only fixed container paths. Timings are converted from microseconds to milliseconds. Operation timings overlap; they are not CPU percentages. Cumulative means are explicitly labeled, and only the top 20 operations and 144 snapshots are retained in D1. No new chat/model calls are made by diagnostics.
|
||||
|
||||
Visitor access remains read-only. The same components render both monitors; diagnostics expose aggregate evidence and managed character names, excluding raw database identities, credentials, command sources and private chat. Native counter/result tables are included in the existing full auth database backup, and all D1 diagnostic tables are covered by the existing D1 backup.
|
||||
|
||||
Currency looted is tracked independently through native player event 37, in copper, and displayed as gold/silver/copper. Item event 32 remains item quantities only. Coin totals exclude quest rewards, sales, trades, and existing wallet balances; no historical currency is inferred. The first sample establishes a baseline, then the last-24-hour view reports observed gains. Both admin and visitor use the same read-only measurements.
|
||||
|
||||
Reference in New Issue
Block a user