Anomaly Detected Journal

The Anomaly Detected Journal has an official 100% Completion badge goal for each named chapter. Roblox’s badge descriptions use the instruction “Capture all the known anomalies within the chapter journal.” That confirms five chapter-specific completion targets, but it does not explain which action captures an entry, whether progress is shared between modes, how hidden entries appear, or what happens after an update adds content. Use the live Journal as the record and this hub as the workflow around it.

Five official Journal goals

The badge identities are stable checkpoints. A badge award percentage or count is dynamic and does not tell you how to capture an individual anomaly. This guide avoids converting those public statistics into difficulty claims.

Make a clean Journal baseline

Select one chapter at a time. Record the chapter title exactly as displayed, the visible completion indicator, the names or silhouettes already revealed, and the position of any hidden slots. A screenshot can help, but write down the date and game version information visible in your session so it does not become an undated reference after an update.

Use a compact tracker with four states: visible and captured, visible but incomplete, hidden, and uncertain after the latest run. Do not assign a name to a hidden silhouette based only on a community list. If the Journal reveals a name, spelling, room, or category, copy the interface rather than a search-result title.

Choose one missing target for the next run when the interface gives enough information. If it does not, focus on a chapter-wide baseline and compare object, light, and shadow changes. The Anomalies hub provides spotting routines for the three families named by the creator.

Test what “capture” means in your session

The official badge descriptions use “capture,” but public developer text does not define the trigger. A safe way to learn is a controlled before-and-after comparison. Note the Journal state, enter the same chapter, identify and report one clear anomaly, complete or exit according to the live game’s normal flow, and reopen the Journal. Record what changed.

Repeat only when the first result is clear. If the entry updates immediately, that supports one trigger for that version. If it updates only after completion, note that. If nothing changes, do not claim the anomaly is bugged until you confirm chapter, selected entry, report feedback, and whether the session ended cleanly.

Solo is useful for this test because no teammate can act on the same event. Co-op can still work if one player performs the report and the group checks whether progress appears for each account. The public material does not define shared Journal credit, so describe the observed result with a date rather than making it a permanent rule.

Use a responsive entry record

This format works on mobile because each field remains a labeled block rather than a wide spreadsheet. Leave unknown cells blank. A short accurate record is better than a complete-looking table filled with inherited or guessed data.

Troubleshoot a missing entry

First confirm the chapter. The five Journals are separate official goals, so an anomaly observed in The School should not be assumed to fill a Residence slot. Second, confirm that the live report succeeded and that you selected the expected room and category. Third, let the run reach the next clear save or result point before checking again.

If the entry remains missing, rejoin through the official Experience page and inspect the Journal once more. A server can be on a different build shortly after a change. Compare solo and co-op only with controlled conditions, and avoid claiming that a mode blocks progress after one ambiguous attempt.

Check the corresponding chapter guide to rebuild the room baseline. Journal hunting becomes inefficient when every run uses a different feed order. Repeated observation of the same anchors is what lets a rare or subtle change stand out when it appears.

Plan completion without burnout

Work one chapter at a time and stop after attention quality drops. Anomaly spotting relies on visual memory; long sessions can make normal shadows and objects feel suspicious. Review the visible gaps, choose a small goal, and take breaks between similar runs.

Do not chase an alleged exact spawn rate. The creator has not published one, and a short personal sample cannot establish it. Your controllable improvement is coverage: consistent feeds, strong anchors, accurate reports, and a dated Journal comparison after the run.

When an update adds new contracts or anomalies, reopen every relevant Journal before assuming a previous 100% state is permanent. The official Experience says new content is in development. An expanded list would be consistent with that statement, but the timing and effect on existing completion still require current confirmation.

Frequently asked questions

Does every chapter have a Journal badge?

Yes. The official badge list contains a 100% Journal completion badge for all five named chapters.

What counts as capturing an anomaly?

The public badge text does not define the trigger. Compare the Journal before and after a clear, successful report in the same chapter and follow current game feedback.

Can Journal progress be completed in co-op?

The official public material does not state how credit is shared. Test with a controlled report and compare each player’s Journal after the run.

Is Chapter 5 Journal complete?

The badge exists and includes “Half way there” in its description, but the phrase is unexplained. Check the current Experience rather than interpreting the badge text as a release-status announcement.

Official reference

• Official Roblox badge list