Wash The House officially describes you and your friends working as cleaners. Co-op can finish independent work in parallel, but only when players know who owns each area and how unresolved items, dirty patches, and repairs are handed off.
Server capacity is not the same as an ideal team size. Shared progress, payout credit, upgrade ownership, and task attribution were not documented publicly for this checkpoint, so test them with one small action before building a specialized team plan.
Choose area roles or task roles
Area ownership gives each player a room or bounded zone and all three task families inside it. This preserves local memory, minimizes travel, and makes “done” easy to audit.
Task ownership assigns item return, washing, or repairs across several areas. It can exploit a washer-focused upgrade or a player skilled at object matching, but it adds travel and handoff cost.
Begin with area ownership for an unfamiliar group. Switch to task roles only when the current layout, personal upgrades, and communication make specialization measurably faster.
Define exact boundaries
Use landmarks: doorway to stair, left wall to window, or one clearly visible zone. “Upstairs” or “this side” is too vague when several players move quickly.
Each owner should begin and finish at the same boundary. Report three states separately: items, washing, repairs. A room that looks clean may still have an unplaced object or repair.
Avoid changing ownership mid-pass unless the handoff includes what was checked, what remains, and where unresolved objects were staged.
Coordinate item returns
Keep uncertain items near the area where they were found. If another player recognizes a destination, report both the staging location and candidate spot. Do not silently carry an object through a teammate’s completed zone.
One player can act as a staging resolver after local easy returns are done. Their handoff needs object description, origin, destinations tried, and whether any prompt appeared.
Confirm placement rather than drop. On controller, RT is pickup/place and LT drops; on PC, E picks up and G drops while placement follows current context.
Divide power washing
Split a large surface at a visible seam or landmark. Each player uses overlapping passes within their own band, not across the other’s center. Call out the boundary before spraying.
At the end, swap edges for one inspection. A fresh angle helps find thin dirty borders. Do not have the whole team repeat every broad surface.
If one player has better washer-related upgrades, test whether specialization actually saves more than the travel it creates. Personal versus shared effects must be confirmed in the current build.
Handle repairs and final reconciliation
Area owners inspect current repair prompts after clutter and broad dirt are cleared. Record candidates that show visible damage but no interaction. A second player gives each unresolved candidate one fresh check.
Before completion, every owner reports: boundary, item staging clear, washing perimeter checked, repair pass checked, and visible progress result. Compare displays if the team sees different totals.
If progress remains, assign one player per task family for the final sweep rather than sending everyone to the most obvious room.
Test money and upgrade sharing
Complete one small known task and compare balances. Buy or inspect one upgrade and observe who receives the effect. Do not assume a teammate’s Earnings level increases every player’s money or that one purchase changes the whole server.
If upgrades are personal, match roles to existing strengths. If money is individual, agree whether players pursue personal progression or optimize only the current clear.
Avoid Robux purchases based on team pressure. Read the current Roblox-controlled prompt and decide independently.
Co-op communication script
Use short, evidence-rich calls:
- “Kitchen boundary checked: items complete, washing edge near door remains, no repair prompt.”
- “One item staged at the entrance; two destinations tried, neither accepted.”
- “Progress changed after the left-wall wash; start the next scan from that wall.”
- “My display differs; pause and compare before rejoining.”
These reports preserve information without a long discussion and prevent duplicate work.
Co-op FAQ
What is the best team size?
No official ideal size was verified. Use enough players to own distinct boundaries without creating communication and duplicate-work overhead.
Is progress shared?
The public description does not explain shared progress or money. Test one small action and compare displays and balances.
Should one player only wash?
Specialization can help when upgrades and layout support it, but area ownership is simpler for an unfamiliar team.
What if two players find the same task?
The current owner completes it while the other returns to their boundary. Announce the progress family so the team can narrow the remainder.