Anomaly Detected has five official Journal 100% Completion badge goals, one for each named chapter. Every badge description says to capture all known anomalies within that chapter Journal. The public sources do not explain the exact capture trigger, hidden-slot behavior, solo versus co-op credit, or whether new content changes a previous percentage. A controlled before-and-after method answers those questions in the live game without guessing.
Choose one chapter collection
Use the exact official chapter names: The Residence, The Neighbourhood, The School, The Hospital, and The Mall. Do not combine their entries in one anonymous checklist. A visual may resemble something from another setting, but the official goals are chapter-specific.
Open the target Journal before joining a contract. Record visible entry names, silhouettes, completion indicators, hidden positions, and any explanatory text. Add the UTC date. If the game displays a version or update label, include it.
Select a contract for the same chapter and confirm the mode and party. Public badge descriptions do not say that Veteran or co-op is required for capture, so begin with the cleanest conditions available to you.
Create an entry record
Use one card per currently visible or tested entry:
- official chapter title and current feed label;
- Journal name only when the live game reveals it;
- stable room anchor and normal state;
- visible anomaly change;
- report room and category chosen;
- success, failure, or ambiguous feedback;
- Journal state after the run;
- device, party state, mode, and UTC date.
Leave unsupported fields blank. A hidden silhouette is not permission to copy a name from an old list. A community walkthrough can suggest what to test, but the row becomes In-game verified only when the current Experience and Journal support it.
Test the capture trigger
The word “capture” could refer to seeing, reporting, completing, or another game action; the badge API does not decide. Test one variable at a time. Take a before screenshot, make one high-confidence report, note its feedback, and check the Journal at the next normal result or save point.
If the entry appears, record the observed sequence without claiming every entry follows it. Repeat with another clear anomaly before treating the behavior as consistent. If it does not appear, verify that the selected contract and Journal chapter match.
In solo, only your action can create the result, which makes the test easier to interpret. In co-op, compare each player’s Journal separately and record who spotted, reported, and received progress. Do not convert one group result into a permanent shared-credit rule.
Track missing entries efficiently
Choose one missing state for a session. Repeatedly changing chapters makes it harder to connect an anomaly to the correct collection.
Improve capture coverage
The official game loop is memorize, spot, and report. Journal hunting still begins with room baselines. Use a fixed feed order, two or three anchors per view, and the three official example families: misplaced objects, flickering lights, and independently moving shadows.
Use Shift, L2, or double tap to zoom on a named doubt. Describe the normal and changed states before reporting. Better comparisons increase the chance that a real entry is recognized and reduce time lost to guesses.
Do not chase exact probability claims. The developer publishes no rates. Your controllable variable is complete, consistent observation across all feeds in the selected chapter.
Handle updates and Chapter 5 carefully
The official description says new contracts and anomalies are in development. After a content change, reopen the Journal before assuming 100% means the same set. Preserve older records with their dates rather than silently rewriting history.
Chapter 5’s Journal badge includes “Half way there.” The phrase is not explained by the badge API. It does not prove that only half the entries are capturable or that the chapter is unfinished. Use the live Journal and creator-controlled announcements for current status.
Troubleshoot safely
If an entry remains missing, rejoin through the official place, verify chapter and account, repeat one clear report, and reach a clean result point. If the behavior reproduces, record the exact steps and share a concise bug report through the X Core Studios group without exposing private account data.
Do not install an extension, executor, modified client, or “Journal unlocker.” Progress is server-controlled, and account-compromising tools cannot create legitimate completion.
Frequently asked questions
How do I complete a Journal?
Capture all known anomalies for that chapter according to its official badge goal. Use the live Journal to identify current entries and verify the capture sequence.
Does a successful report always add an entry?
The public sources do not define that rule. Compare before and after a controlled successful report.
Can new updates change completion?
New anomalies are officially in development, so recheck the current Journal after updates. The exact effect on prior progress is not published.