01
Chronicle
Milestones, chapters, deaths, discoveries, screenshots, and other factual moments become a readable timeline.
A character autobiography addon
Your character left a trail.
Ant Trail remembers it.
Ant Trail records the story of a character’s life — the roads walked, chapters opened, lives lived, places revisited, and adventurers genuinely encountered along the way.
Forever beta
Ant Trail v0.36.2
•
WoW: Forever launch
November 4, 2026
THE TRAILRECORDED, NOT RANKED
Chapter IVWestfall road
Life III2h 11m tracked
Handshakecrossed paths again
Not a guide. Not a leaderboard. A history.
Local firstYour character history begins on your machine.
No rankingThe story is the point, not a score.
Observable onlyNo player sweeps or hidden-data hunting.
Evidence over guessesUnknown history stays unknown.
The trailhead
Built to remember a life in the world.
Ant Trail turns ordinary play into a browseable personal history. It is deliberately autobiographical: it describes where your character has been and what happened there without telling you how to play.
02
Replay
Revisit routes your character actually walked, with active play kept distinct from known time spent logged out.
03
Handshakes
Remember legitimate crossings of paths with other adventurers without turning players into scan results.
04
Lives
Deaths become boundaries in the autobiography: one life closes, another begins, and both remain part of the story.
05
Trail map
See a character’s movement history as a personal trail through the places they actually visited.
06
Personal analytics
Look back at your own habits, routes, time, and memories without converting them into public performance rankings.
Current trail marker
v0.36.2
The current public build is distributed through CurseForge. The website keeps release details secondary to the character-history work itself.
Get Ant Trail
CurseForge is the official download road.
All public Ant Trail downloads and updates go through CurseForge. The website does not mirror addon ZIPs or walk players through a separate install path.
An Ant Trail website account is for Campfire, account safety, and future Trail services. It is not required to download the addon.
Website account
VerifiedOne identity for the trail.
Public reading stays open. Writing to the Campfire requires a verified Ant Trail account. Future private Trail storage and publishing controls will attach to that same account instead of inventing a second identity later.
A life, not a dashboard
What a public trail could eventually feel like.
This is an illustrative mock character page. Public Trail pages are not enabled yet.
Chapter opened
The road beyond Goldshire
The trail leaves Elwynn and begins to stretch west.
Handshake
Crossed paths with an adventurer again
A remembered encounter, recorded only from legitimate observable play.
Life closed
Life II ended in the Deadmines
The story keeps the loss as part of the character’s history.
Life opened
Life III begins
A new span in the autobiography starts without erasing what came before.
The campfire
Talk about bugs, rough edges, and good ideas.
Anyone can read the Campfire. Posting a bug, idea, question, or reply requires a signed-in Ant Trail account with a verified email address.
Before posting a raw file: stop. Full SavedVariables can contain far more history than a public bug report needs.
Read the safe-report guide →
0trail notes
0open bugs
0replies
Account-gatedboard mode
No trail notes match those filters.
Known tracks
Things already on the map.
Confirmed concerns and areas we are deliberately watching during development.
InvestigatingAT-001
Legacy SavedVariables migration edge cases
Older histories can contain shapes that newer builds should treat conservatively rather than guess into modern records.
WatchingAT-002
Replay chronology on unusual session boundaries
Replay timing uses active-session evidence. Legacy points without enough session identity remain explicitly uncertain rather than invented.
DesigningAT-003
Public trail sharing
A privacy-first import path is being designed around Ant Trail-owned exports before any website-side visualization is enabled.
DesigningAT-004
Website moderation
The shared Campfire launch needs spam controls, moderation tools, and a safe private path for reports that genuinely require SavedVariables.
Roadmap
Build the home before opening the gates.
The website can mature independently of the uploader. Each phase should be useful on its own.
Trailhead + Campfire
Official project home, account-gated bug reports, feedback, discussion, known issues, docs, release history, privacy, and community rules.
Shared community board
Moderated public Campfire with anti-spam, replies, statuses, search, and maintainer tools.
Manual Trail Import
User-selected Ant Trail exports can be validated, previewed, redacted, and only then published as a character page.
Live-enough Trail Sync
No implementation until the exact external data path has passed a fresh Blizzard-policy review and avoids unauthorized game/process data collection.
Development chronicle
The addon should have a history, too.
Release notes should explain why changes exist, not merely list filenames.
Replay timing correction
Replay preserves evidence timestamps while compressing known logged-out gaps out of active playback duration.
Trail-map refinement
Continued trail-map work while preserving the central rule: record the journey without becoming a route guide.
Project Bible rollup
A major documentation checkpoint consolidated the design and implementation record for future development.
Trail Upload
The gate is built. It is not open yet.
The future site is intended to accept a player-selected Ant Trail export, validate it, show a private preview, and let the player choose what supported fields become public. “Live enough” syncing remains a separately gated design problem.
Manual firstPrivate previewSchema validationExplicit publish
Guardrails
Useful without getting clever around the rules.
Ant Trail is being designed conservatively around Blizzard’s addon rules and EULA. No feature is worth building if it requires hidden data access, gameplay automation, packet interception, or process-memory reading.
Addon code stays visibleNo obfuscated gameplay addon logic.
No gameplay automationAnt Trail observes and records; it does not play.
No hidden-data miningExternal sync must not become a game/process reader.
Review again before syncThe eventual uploader needs a separate implementation-level policy check.
FAQ
Questions from the trail.
Does Ant Trail tell me where to level?
No. The design goal is historical, not prescriptive. It records and replays what your character actually did rather than selecting an optimal route.
Does the website need my Battle.net login?
No. Ant Trail website accounts are separate from Battle.net. We do not ask for your Battle.net password or use it as website authentication.
Can I upload my SavedVariables now?
No public Trail upload exists yet. For support, do not post a full SavedVariables file in the Campfire. Use the documented private recovery workflow when raw data is genuinely necessary.
Will character trails be public automatically?
No. The proposed model is private import and preview first, followed by an explicit publish step for supported public fields.
What does “live enough” mean?
The ambition is for public trails to update frequently enough to feel current without crossing Blizzard’s rules. The technical path is intentionally undecided until it can be reviewed safely.
Is Ant Trail affiliated with Blizzard?
No. Ant Trail is an independent community addon project and is not affiliated with or endorsed by Blizzard Entertainment.
The Ant Trail rule
“Remember what happened. Don’t decide how people should play.”
Autobiography over optimization. Observable encounters over surveillance. Personal history over ranking.