Co-op is most useful in 🍂 Clean all the leaves! when every player owns a different visible job. The official description tags the experience for coop and teams, and Roblox metadata lists a maximum server size of 12. Public sources do not explain whether leaf progress, money, tools, special leaves, 100%, or badges are shared. Build the team route around territory and communication first, then treat ownership as something the current session must reveal.
Choose a session owner and a common start
Before clearing, agree whose session progress matters most if the game stores state per player. Have that player join first when practical, then let the group gather at one recognizable landmark. Confirm that everyone can see the same open areas and a compatible progress state. If one player sees a different boundary or total, solve that difference before dividing the yard.
Do not assume the largest server is the best team. Two or three coordinated players can outperform a crowd that repeats the same patch. Add players only when the map has enough distinct territory and someone can still keep a clear picture of what is finished.
Divide territory by landmarks
Use boundaries that remain understandable from either direction: a fence segment, building edge, path, prop cluster, elevation change, or transition. “Take the left side” breaks when players turn around. “Clear the perimeter from the entrance to the large landmark” gives both a start and an end.
For a small team, assign open lanes, perimeter edges, and frontier watch. For a larger team, divide each open area into bounded zones and assign one person to collect status reports. Keep assignments stable through the bulk pass. Constantly swapping territory creates the same duplicate work as everyone following the nearest cluster.
Use four practical co-op roles
The bulk cleaner takes large uninterrupted coverage and keeps lanes aligned. The edge cleaner handles corners, walls, props, and the joins between zones. The frontier watcher stays near the current locked or newly open transition and calls the moment access changes. The completion checker revisits finished boundaries and maintains the list of special-leaf landmarks.
These are jobs, not fixed character classes. Players can change roles after an unlock or tool purchase. A player with a tool that performs well on open coverage should take bulk work; a more controllable option may be better on edges. Since exact tool functions are not publicly documented, base the assignment on observed results rather than a claimed meta.
Communicate unlocks without pulling everyone away
When a new area opens, the frontier watcher should name the entrance and nearest landmark. One player or pair can orient in the new section while the rest finish the old threshold. Moving the entire group at once leaves scattered misses exactly where the map expands.
After the orientation loop, divide the new space before starting. Preserve a return route and report any suspicious special-leaf landmark. The Map Index gives the team a common vocabulary, and Area Unlock Order helps if clients do not appear to agree about access.
Handle tools and upgrades as personal until proven shared
Public information confirms buying and upgrading tools but does not say whether resources or purchases are shared. Each player should read their own displayed balance and tool state. Do not spend a teammate’s expected resources or promise that one purchase improves the whole team unless the current experience demonstrates it.
Specialization is still possible without shared upgrades. Compare which player clears a bounded patch with fewer passes, then assign that tool to the matching job. If a purchase changes only one player’s performance, adjust territory rather than treating the difference as a bug.
Track special leaves carefully
The official Leaf Collection badge confirms that all special leaves form a collection, but multiplayer credit is not publicly explained. When someone finds one, call the landmark before collecting if the timer and situation allow. Other players can observe whether the object appears for them and whether any collection indicator changes.
Record who interacted, who was present, whether the object disappeared for everyone, and which accounts later received the badge. Do not force every player to repeat a long route based on a single ambiguous observation. Keep the run moving and use Special Leaf Locations for the stable location record.
Run the final 10% as an inspection team
Near completion, stop broad free-for-all clearing. Assign old perimeters, area transitions, prop clusters, elevated spaces, and the active frontier. Each player reports either a found patch or a finished zone. The coordinator removes completed zones from the mental list so nobody repeats them.
If one player finds an ordinary leaf, the others should finish their current small zone before converging. A single discovery does not prove the rest of the map is clean. If progress changes only for some clients, keep the session owner with the final actions and note the difference for later testing.
Join-in-progress and reconnect boundaries
Roblox supports joining servers, but public game information does not define how this experience handles a late arrival. A joining player should compare open areas, total progress, tool state, and visible special leaves before taking a completion-sensitive role. Give them a self-contained zone first.
After a disconnect, rejoining the same server may not guarantee the same personal state. Avoid assigning the reconnecting player the final collectible or ending trigger until the displayed state agrees with the session owner. If a private server or reserved-server behavior differs, record that separately; public metadata does not establish it.
Co-op failure patterns
- Everyone follows the strongest tool: territory behind the group remains unchecked.
- Players call screen directions: routes become ambiguous after turning.
- The whole team enters every unlock: old thresholds collect misses.
- One person silently buys upgrades: tool roles change without the team adjusting.
- A special leaf is collected without a landmark: later players cannot reproduce the find.
- The final sequence starts while teammates are absent: badge and ending ownership becomes harder to understand.
A clean team plan
Gather at one landmark, establish the session owner, and divide the first area into bulk, edge, and frontier jobs. Call every unlock. Reassign territory after major tool changes. Keep a short list of special-leaf landmarks. At high completion, assign inspection zones and have one coordinator track them. When 100% is reached, keep the team in the session until the ending and any badge notifications have resolved.
This route uses what is officially supported—team play, leaf clearing, tools, expanding areas, 100%, and badges—without pretending the sharing model is known. Continue to Beginner Guide for the clearing rhythm or Secret Ending for completion-sensitive preparation.
Evidence status, August 14, 2026: Official metadata supports co-op/team positioning and up to 12 players. Save ownership, shared progress, shared money, tool effects, late joins, special-leaf credit, revive behavior, and badge awards need current in-game testing.