Owned and duplicates mean different things
Owned records whether the blueprint is in your collection. Dupes Owned records extra copies, beyond that owned entry. A blueprint you have learned does not automatically give you a spare to trade.
WORKED EXAMPLE · NOT LIVE INVENTORY
- Learned; no spare copies
- Owned: Yes · Dupes: 0
- Learned; two spare copies
- Owned: Yes · Dupes: 2
- Still missing
- Owned: No · Dupes: 0
Do not enter three duplicates because you learned one blueprint and have two extras. The duplicate count is two. A positive duplicate count implies ownership in UAG, so setting duplicates while trying to keep an item “missing” creates a contradictory record.
Build an accurate starting collection
- Open Blueprint Tracker and compare its entries with your current in-game collection.
- Mark a learned blueprint as Owned. Enter only the extra copies you actually have.
- For an item you still need, leave Owned off and set a priority if you want to focus on it.
- Save the change and check the resulting missing list before moving to Raid Planner.
Use Save Owned / Dupes Only when you are correcting the collection without reporting a new loot location. You do not need to create a drop report just to adjust an old count.
After trading away a spare, reduce its duplicate count. If you still know the blueprint, keep Owned on. This preserves the distinction between having learned the recipe and having a physical copy available for another exchange.
Review a photo import before accepting it
A photo is a way to propose collection changes. Treat the review screen as a checking step. Glare, cropped edges, camera movement and similar-looking cells can make a proposed match uncertain.
- Use a clear, evenly lit image of the relevant in-game grid. Keep cell borders visible.
- Review the proposed blueprint names and ownership changes, rather than accepting solely because the image looks tidy.
- Correct mismatches manually before confirming the update.
- Return to the tracker and compare a few known owned and missing entries with the game.
If the result is confusing, correct the individual entries instead of repeatedly importing the same unclear image. An import is not a live connection to your ARC Raiders account, and it cannot establish how many spare copies you hold without your checking them.
Separate collection edits from drop reports
A useful drop report explains a real acquisition. Choose the acquisition type that fits what happened. A blueprint obtained through a quest, gift or trade should not be reported as a raid loot drop with an invented map location.
For a genuine raid drop, record the details you actually know. A remembered map is better than a made-up precise pin. Community observations can help other raiders assess possibilities, but they are not an official guarantee or a measured drop rate.
Keep the collection count and the report consistent. Finding a spare can increase Dupes Owned; learning your first copy can change Owned. Saving a report should reflect that event rather than resetting the whole collection.
When the missing list looks wrong
Check the blueprint’s Owned flag first, then its duplicate count and priority. Raid Planner and Favourite Loadout use your saved collection, so an accidental ownership change can remove an item from those wanted lists.
If you are signed out, loading or seeing an error, wait for a confirmed saved collection before treating a blank screen as an empty collection. Refreshing is useful for loading a saved state; it is not a reason to overwrite your progress.
Use a full season reset only after reading its confirmation carefully. It is broader than clearing one mistaken blueprint. For a single correction, edit that entry or use its individual clear action and then recheck the result.
Put the guide into practice
The guide is public. Your personal collection, planner and loadout are managed in the app after signing in.
Open Blueprint tracking in the app ↗