Legacy SavedVariables migrations
Older histories may lack modern schema fields. Recovery should preserve known evidence and avoid inventing precision.
Trail condition
What works now, what is being watched, and what remains intentionally gated.
Current snapshot
Chronicle, Lives, Chapters, trail history, Replay, and related historical presentation remain the core of the addon.
World Map integration now handles current Forever behavior more safely, including controller/gamepad UI mode.
The shared Supabase backend is connected with row-level security, verified-account posting rules, rate limits, replies, and private abuse reports. Public registration remains closed until transactional email and bot protection are verified.
No external game reader exists. Manual import is the conservative first design; near-live sync has not been approved or implemented.
Known Tracks
Older histories may lack modern schema fields. Recovery should preserve known evidence and avoid inventing precision.
Legacy or interrupted sessions need careful treatment when session identity is incomplete.
Manual import, validation, private preview, field redaction, and explicit publish are the current design direction.
Server-side anti-spam and private report submission are in place. Maintainer review tools and a private support path still need to be finished before the community gate fully opens.
Website readiness
Campfire writes are account-gated. Database row-level security, abuse limits, and private reports are active; registration remains closed until email verification delivery and bot protection are verified in production.
Deliberate gates
Live-enough syncing is not a synonym for “background game reader.” The implementation method is the policy question. Until an exact design is reviewed, the website should never imply that Ant Trail continuously reads or intercepts the WoW client.
Found something?
Use the Campfire for reproducible bugs, confusing behavior, feature ideas, and questions. For a raw SavedVariables recovery case, preserve the untouched source and use a private support route rather than posting it publicly.