Collections are a confirmed Loop [ALPHA] objective: the official description tells players to “collect collections.” The public first-party material does not define the Collection item type, total count, fixed locations, randomization, persistence, or rewards. A useful guide must therefore teach you how to verify discoveries without pretending the catalog is complete.
Treat every candidate as unconfirmed until the live interface names it or shows a registration result.
Use a Collection record card
Find candidates without losing the mission route
Complete or understand the current mission before taking deep optional branches. Choose a return landmark and search one loop at a time. When you see a candidate object or prompt, record its direction before interacting.
Do not assume a decorative object, Item, mission target, and Collection are the same category. The live prompt and result should establish what happened.
Confirm that it registered
After interaction, look for a named message, changed count, menu entry, icon, sound, or objective update. Open any current Collection view if the game provides one. An object disappearing is not enough by itself; it could have been an Item, mission object, or temporary state.
If no feedback appears, write “interaction observed; registration unverified” rather than adding it to a complete list.
Test location and Day variation
Return during another run and compare the same landmark. If the candidate is absent, do not immediately call it random; the Day, mission, server, or prerequisite may differ. Repeat and record conditions.
Because the developer says every Day can be different, publish landmark observations as dated possibilities until a pattern is well supported.
Check persistence
Compare the Collection record before and after a Day transition, death, escape, and rejoin. Test with a low-risk discovery. Do not claim permanent account collection, run-only state, or loss on death from the official phrase alone.
If a menu count persists but the world object returns, distinguish account record from world availability instead of treating one as a contradiction.
Solo Collection route
In solo, keep the mission and escape route primary. Explore only one optional branch beyond the last known landmark. If an entity cue begins, abandon the Collection attempt and preserve the route.
Record the discovery immediately because nobody else can confirm the prompt or location.
Co-op Collection route
Let one player interact while others compare their screens. Check whether the object remains visible, whether every Collection record changes, and who receives any feedback. Do not assume a shared catalog or individual ownership.
If it is not shared, rotate the interaction only when the object remains and the route is safe. Never promise that a one-player discovery credits the whole group.
Rewards and completion claims
No official public reward table or total count is established. Do not infer a reward from a simultaneous Coin or Inventory change unless the interface names the connection or a repeat confirms it.
Call an index “currently documented” until the live game or creator publishes a complete count. A partial list is useful when it is honest about scope.
Collection mistakes
- Calling every unusual object a Collection.
- Listing a location without the Day and landmark context.
- Treating disappearance as registration.
- Claiming a complete total from one run or video.
- Assuming persistence after only a Day transition.
- Assuming a co-op pickup credits everyone.
- Inventing a reward because another value changed nearby.
Collections FAQ
What counts as a Collection?
Use the live label or registration feedback. The official description confirms the system but does not define every object publicly.
Where are Collections located?
No complete fixed map is verified. Record current Day landmarks and expect variation until repeatable evidence shows otherwise.
Do Collections save?
That is unverified. Compare the current record across specific transitions and note the Alpha date.
Does one pickup count for the whole team?
No public first-party rule confirms it. In co-op, compare each player’s record after one controlled interaction.
Evidence status: Collections as a core objective are Official. Names, total, locations, randomization, registration UI, persistence, rewards, and co-op ownership need in-game testing.