Loop [ALPHA] supports playing with friends. The official Not Alone badge says “Play a game with a friend,” and the official experience can host up to 30 players in a server. Neither fact establishes an ideal party size, private squad limit, shared Inventory, shared Coins, shared mission credit, revival rules, or whether every player receives EXIT credit.
Treat the first group run as both a survival attempt and a controlled comparison. Keep roles simple, speak in landmarks, and compare screens after one important interaction instead of assuming every system is shared.
Join the same official experience
Confirm the group is entering Place ID 97694772546348 by Gazing at the Moon. Use Roblox’s current friend and join controls rather than a third-party link. Once everyone loads, compare the Day, mission text, and starting state before splitting.
If players see different objectives or states, stop and determine whether someone joined late, entered another server, or is seeing a personal mission. Do not build the whole route on the assumption that one screen represents the team.
Assign three lightweight roles
One player reads the current objective and calls changes. One tracks the route and names return landmarks. One watches behind or monitors nearby cues while others interact. A smaller group can combine roles; a larger group can duplicate them, but avoid giving every player a different theory.
Swap roles when the Day changes or a player becomes uncomfortable. Roles are communication tools, not proof of hidden class mechanics.
Use landmark-based callouts
Call the entity or event if known, then landmark, direction, and state. “MineSpider, near start junction, sequence active” gives the team a route and a reason to pause. Avoid “over here,” especially in rooms that can change between Days.
Set a regroup landmark before exploring. If anyone loses contact, the group returns there rather than sending everyone through unknown branches. A regroup rule protects the mission route and reduces the chance that one uncertain cue scatters the whole party.
Test mission credit once
Choose a low-risk mission interaction and let one player perform it while everyone compares their objective state. Record whether progress changes for the actor, nearby players, or the whole group. Repeat only if the result is unclear.
Do the same for a Collection candidate. An object disappearing for one player does not prove it registered for everyone. The Missions and Collections pages show which feedback to capture.
Test Coins, Items, and Inventory carefully
For one pickup or purchase, compare every player’s Coin balance and Inventory before and after. Determine who can see the object, who can interact, whether it remains for others, and where the result appears. Do not assume a shared wallet, duplicated loot, or trade action.
The official badge text proves that Coins, Items, Upgrades, Inventory, and Flashlights exist, but not how they behave in a group. Assigning a “banker” or carrier before checking ownership can concentrate risk without a benefit.
Handle entities as a team
Only one player needs to test a suspected interaction; the rest should preserve the route and observe. If a Smiler is stunned, compare what each player saw and what action immediately preceded the state. If a MineSpider sequence begins, do not surround it while trying to measure a blast. If Standing Man appears, avoid declaring a gaze or movement rule from one death.
PopUp.exe may demand interface attention according to its badge wording. If the game allows, have one player focus on the prompt while another watches the environment. The exact operation remains unverified, so the live interface wins.
Approach the EXIT together
When someone finds an EXIT, mark the route and regroup before testing it. Compare whether its visible state is the same for everyone and whether the current mission suggests an opening condition. Decide who approaches first and what the others will do if the state changes.
After an escape, compare result screens and badge awards. The EXIT badge proves the outcome exists but not whether one crossing credits the entire group. Record late joins, deaths, and distance from the EXIT when results differ.
Death, disconnects, and rejoining
The public first-party material does not define revival, spectating, dropped Inventory, mission ownership, or rejoin recovery. Test those rules with a low-value run before relying on them. If a player disconnects, keep the last shared landmark and objective state; do not spend the rest of the run assuming they can rejoin with everything intact.
If one player dies, compare what remains for survivors and what the defeated player sees. Describe the result, not a theory about why the server handled it that way.
Co-op mistakes
- Splitting before comparing the starting mission.
- Using “here” instead of a landmark and direction.
- Assuming one pickup or objective update is shared.
- Sending every player toward an unknown entity cue.
- Starting a solo-only badge attempt with friends.
- Leaving through an EXIT before regrouping and comparing state.
- Treating a 30-player server capacity as the recommended squad size.
Co-op FAQ
How many friends should join?
The official maximum server size is 30, but no public first-party source defines an ideal squad size. Start with a group small enough to keep callouts clear.
Are Coins and Items shared?
That rule is not established publicly. Compare balances and Inventory after one controlled interaction in the current build.
Does everyone receive mission or EXIT credit?
Do not assume it. Compare objective and result screens after one interaction or escape, including who was nearby, alive, or joined late.
Does co-op invalidate solo badges?
Pure Skill and Pocket Full explicitly say solo only, so attempt them alone. Read every other badge’s own wording rather than applying that restriction universally.
Evidence status: Friend play, Not Alone, and maximum server size are Official. Party size, shared progress, resource ownership, death, rejoin, and group EXIT credit need in-game testing.