Anomaly Detected officially lets friends monitor surveillance feeds together, and Roblox game data lists a maximum server size of eight. The cap does not tell you the ideal team size, feed permissions, shared penalties, or progress rules. A strong co-op group begins by looking at the live contract, then divides visible responsibilities so no feed is assumed to belong to “someone else.”
Set up the lobby
Confirm the exact chapter and mode before assigning jobs. Ask every player to read the current controls on their device. Shift, L2, and double tap are the creator-published zoom inputs; other actions should come from the live prompts.
Test what each player can see and control. Do not assume everybody shares a camera, report menu, Journal state, or result screen. Public developer text confirms monitoring together, but leaves those operational details to the current game.
Choose a voice or text channel that does not cover important UI. Keep volume comfortable even though headphones are recommended. Agree that urgent callouts interrupt casual conversation.
Assign feeds after loading
Count and name only the feeds shown in the current contract. Assign each complete feed or a clear contiguous group to one watcher. Give the watcher a backup who knows the names but continues covering their own area until asked.
Avoid splitting by anomaly type. If one player watches only for lights and another only for objects, both must repeatedly inspect every feed and can still leave motion unclear. Feed ownership keeps location and baseline together.
In a small group, one person can hold several roles. The point is clarity, not filling all four labels.
Use concise anomaly callouts
A useful callout is “chapter, feed, anchor, change.” For example, “Residence, feed label, left lamp, normally steady and now flickering.” Use the real labels and features in the live game. Avoid “there,” “look,” or “something changed,” which forces every player to abandon coverage.
The owner should describe the baseline before the confirmer acts. The confirmer asks one question and uses zoom if needed. The reporter repeats the selected room and category, submits once, and announces the feedback.
After success, everyone resumes from the next planned feed. After failure, the owner reassesses the evidence while the rest of the team continues watching. Do not turn one doubtful report into a full-group debate that leaves every camera unattended.
Split attention without duplication
Each watcher should use the same method: wide geometry, object anchors, light behavior, independent motion, then one targeted close check. The official description names misplaced objects, flickering lights, and moving shadows, so the group can share that vocabulary without claiming a complete taxonomy.
Mark feed boundaries clearly. If player one covers feeds one through three and player two covers four through six, both should know who owns the wrap point. Adjust the example to the actual count; the creator publishes no universal feed total.
If a player has a smaller mobile screen or a less comfortable control, assign feeds with stronger silhouettes rather than assuming identical performance across devices.
Recover from disconnects and confusion
When somebody leaves, say their feed group aloud and assign it immediately. The backup confirms takeover; other players should not silently duplicate the same group. If the team loses track, pause conversation, state each owner and current continuation point, then resume.
If two people report at once, re-establish one reporter. If report permissions differ, adapt to the current interface and keep the caller responsible for precise evidence. If the Journal results differ between accounts, record the chapter, action, party state, and each outcome instead of declaring a universal shared-credit rule.
Co-op Journal and Veteran goals
Each chapter has official Veteran and Journal badges, but public metadata does not explain co-op credit. Compare every player’s Journal before and after one controlled report. Reach the same result point and record whether progress appears for owner, reporter, or all players.
Prepare for Veteran with a normal co-op run using the exact same roles. Read the current Veteran description and change only what the attempt demonstrates. A larger lobby will not compensate for poor ownership or vague callouts.
Use Veteran Mode and the Journal Guide for the related workflows.
Common co-op mistakes
- Treating eight players as the required or best team size.
- Assigning anomaly families instead of clear feed ownership.
- Letting several people submit one guess.
- Using different names for the same room.
- Failing to transfer feeds after a disconnect.
- Assuming Journal or completion credit is shared without checking each account.
Frequently asked questions
How many players can join Anomaly Detected?
Roblox game data lists a maximum server size of eight. The ideal team size is not published.
Should one person report everything?
Use one agreed reporter if the current interface permits it. Otherwise keep one clear owner for each report decision.
Is co-op progress shared?
Official public material does not define completion or Journal credit. Compare current results for each player.