AllTheThings, usually called ATT, declares interface 16001 among the targets in its author’s master-branch TOC. This is direct evidence of a Forever development target, but it does not identify a verified published Forever package or certify its collection data. Confirm the exact release you plan to install before relying on it.
ATT's core purpose is to organize what you have collected and what remains. Its project describes a main collection window, a zone minilist, filters and extra tooltip information. Those general capabilities explain the addon; they do not prove complete coverage of Forever's quests or collections.
Decide what you want to collect
ATT is useful in concept when your question is about completion: which listed quests, appearances or other collectibles you are missing, and which entries you want to pursue next. It is different from an addon whose primary job is choosing your next leveling objective.
The general project tracks categories including quests, appearances, mounts, pets, toys and titles, along with achievements in supported game versions. Do not read that list as a statement that every one of those game systems exists in the same form in Forever.
Choose one collection goal before configuring a large database view. A focused list of entries relevant to the activity you are doing is easier to evaluate than a percentage covering many unrelated categories.
Author source metadata shows target interfaces; verify the packaged release and its data separately.
Confirm the file rather than the recommendation
The author’s TOC uses a version placeholder rather than a concrete release number and loads game-dependent database paths. Those declarations explain the intended target; they do not establish which database or fixes are included in a particular download.
A claim that ATT has a Forever build still needs to resolve to an actual release. Check these fields together:
| Field | What you need to establish |
|---|---|
| Project identity | The AllTheThings project you intended to use |
| File game flavor | Forever is explicitly included |
| Game version | The package targets the applicable Forever version |
| Release version and date | The actual file, rather than a guide's update date |
| Database notes | What Forever content is included or still incomplete |
A file may support several branches, so a multi-flavor package is not inherently wrong. The missing piece is a clear Forever declaration for that same file.
Do not select a build by cumulative downloads or by a screenshot of a familiar collection window. Those signals identify a popular project or an interface example, not the right data for your current game.
Use filters to make the lists useful
After obtaining an explicitly supported package, start with ATT's main collection window and the filters available in that release. The general project provides a movable, resizable window and a zone-oriented Auto Minilist.
Use the main window for planning and a smaller list for the place where you are currently playing. Avoid treating every missing entry as an immediate task. First decide whether it belongs to the category and content you actually want to complete.
If a list seems empty, inspect the active filters before concluding there is no content left. If it seems impossibly broad, narrow the category before using the total as a completion goal. These checks keep a display choice separate from a database problem.
Keep completion, eligibility and data coverage separate
A collection tracker can show that an entry is missing without proving you can obtain it immediately. Likewise, an absent entry does not prove the item or quest is absent from the game.
Use three distinct questions when evaluating a result:
- Completion: does the addon show the entry as collected or unfinished for the character or collection view you selected.
- Relevance: does the entry belong to the game branch and content you are trying to complete.
- Coverage: does this package actually contain current information about that entry.
Check the live item's or quest's own information before planning a long trip around an uncertain database row. Familiar Classic content can have changed in Forever, and an imported database does not settle every difference.
Inspect quest chains and tooltips with care
ATT's general project can expose extra context on tooltips. It also describes popping a quest into its own chain window when the entry has the necessary parent-quest links.
That last condition matters. A chain view depends on the relationships entered in the database. Do not infer a complete Forever prerequisite sequence from an incomplete or older quest-chain example, and do not use a Retail quest-chain screenshot as confirmation of a Forever feature.
Use a supported chain view to inspect its listed relationships, then compare the quest you intend to do with your current game state. If the relationship data is absent, stop at the known entry rather than guessing the missing steps.
Build a small collection session from the list
Once a supported package and a relevant list are established, choose a collection goal small enough to inspect directly. For example, use one selected quest entry or one group of items associated with content you intend to visit. This is a planning method, not a claim that every possible collection category has complete Forever data.
Read the entry before treating its missing mark as a task. Identify the content it belongs to and the information the addon provides about obtaining it. If that context is absent, retain the name for a later check instead of guessing a vendor, location or prerequisite.
After completing the activity, compare the actual outcome with the same entry and filters. Keep the view consistent so you can distinguish a changed collection state from a changed list. Switching filters or profiles at the same time as checking progress makes the result harder to interpret.
A small session also keeps the collection display useful when some data remains uncertain. You can work on entries you understand without assuming the entire database must already be complete or that every listed percentage is a meaningful goal for your character.
Read an unexpected result before resetting anything
A surprising collection total can come from several different questions being mixed together. Before changing files or resetting settings, identify what the screen is showing.
| Unexpected result | First comparison to make |
|---|---|
| An entry disappears from a list | Compare the current filters and selected category |
| A familiar item is marked missing | Compare the exact entry with what you actually obtained |
| A zone list seems much shorter than expected | Check its scope before treating it as a complete quest inventory |
| A quest chain stops early | Inspect whether the necessary parent links are present |
| A list includes unfamiliar systems or content | Confirm the package's branch and the selected database context |
These comparisons do not diagnose a particular bug in advance. They identify the information you need to avoid an unnecessary reset. A clear description of one incorrect entry is more useful than a claim that the addon has lost everything when the selected view has not been checked.
If a completed action is not reflected, retain the exact item or quest and the state displayed afterward. Do not repeat a long activity solely to make a percentage change until you understand whether the entry belongs to the current game and whether the tracker has suitable data for it.
ATT's general goal is to make collection information easier to inspect. Use that visibility to make decisions about specific entries, while leaving unresolved data unresolved. A tracker is most useful when it reduces uncertainty about your next activity rather than turning an unexplained total into an obligation.
Retain useful details when something looks wrong
The project advises completely closing and reopening the game if errors appear after an update; changing addon files while the game is running can cause problems. Preserve the exact release version and the entry involved before making further changes.
For an incorrect collection result, a useful report includes the item or quest name, active filters, the expected state and the state actually displayed. That gives a maintainer something specific to inspect.
Use the author’s declared target as a starting point, then confirm the release and its collection coverage. Do not build a completion plan around an unverified version number or a percentage whose contents you have not checked.