Skip to content
Completion ArchiveMilestones, records and spoiler control
CurrentPatch 1.17.00

Collectibles & Knowledge Checklist

A region-by-region method for auditing supported knowledge, collectible and discovery records without invented totals.

Evidence
Tested & verified
Verified
2026-08-08
Spoilers
Minor spoilers

Use the Collectible Catalogue as the canonical record list and the Completion Companion as your saved checklist.

  1. Finish the active story or regional prerequisite.
  2. Reveal the local map and services.
  3. Filter the catalogue to one region and one category.
  4. Clear records with verified locations first.
  5. Revisit quest-linked records after the relevant quest state changes.
  6. Mark inaccessible records as blocked.
  7. Keep provisional names, routes and rewards in Research.
  8. Export a tracker backup after each region.

For each region:

  • supported knowledge records checked;
  • supported collectible records checked;
  • discoveries and services revisited after progression;
  • quest-linked entries compared with the completed journal;
  • missing entries rechecked after save and reload;
  • provisional records excluded from the complete count.

A useful record contains:

  • stable canonical ID;
  • visible in-game name;
  • category and region;
  • prerequisite state;
  • precise route or interaction;
  • completion signal;
  • reward or effect only when verified;
  • patch and platform;
  • reproducible source.

A map screenshot without the required world state is a candidate, not a complete route.

  1. Confirm the relevant quest is truly complete.
  2. Install the current verified patch.
  3. Save to a new slot and reload once.
  4. Revisit the knowledge interaction or associated character.
  5. Compare the in-game list with the canonical record.
  6. Check Current Known Issues.
  7. Record the exact missing name, category, quest state and platform.

Do not start a new game or delete a save merely to test a missing list entry.

Names can change between patches or localisations. Before adding a new entry:

  • compare location, interaction and reward;
  • check accepted aliases;
  • keep the stable ID when only the displayed name changes;
  • retire an ID only through the migration record;
  • never reuse a retired ID for different content.

Check a record only when the accepted in-game trigger is visible. Discovery of a candidate location, a community map marker or a patch-note name does not by itself prove collection.

  • Every supported region has been reviewed.
  • Quest-linked records were checked after their prerequisites.
  • Patch 1.16 knowledge-list repairs were retested where relevant.
  • Renamed entries retain stable identity.
  • Unknown totals remain unclaimed.
  • The catalogue and Completion Companion backups agree.