Use this checklist when the mansion looks mostly clean but the current session is not complete. The key is to stop searching randomly and identify which of the three official task families remains: returned items, power-washed dirt, or repairs.
Do not begin with a full restart. Preserve the current state, staging locations, unresolved candidates, and progress displays. That information makes a structured sweep much faster than repeating every action.
Step 1: read every live indicator
Pause in a clear place and record the visible task categories and values. Current walkthrough footage shows item and washing counts in one build, but the exact totals are not permanent. Use only the values shown in your current server.
Ask which category is definitely incomplete. If the UI does not separate categories, repeat one known-valid action from each family when available and watch what changes. Do not assume the remainder is dirt simply because dirt is visually prominent.
In co-op, compare what each player sees. Shared-progress behavior is not officially documented here, so disagreement can reveal a display or synchronization problem.
Step 2: reconcile staging points
Visit every location where uncertain items were deliberately dropped. Confirm that none was mistaken for a finished return. Try the strongest remaining destination match and look for the live placement response.
Check boundaries between rooms, because an item carried during exploration may have been dropped outside its original area. Scan at floor, furniture, wall, and upper levels. Remove visual clutter only when you can return it afterward.
If one item still refuses every plausible location, record the origin and attempts before moving it again. Use the Return Items guide rather than testing every surface in the mansion.
Step 3: run a perimeter washing pass
Return to areas where washing definitely advanced progress. Trace every outer border in one direction, then check seams, corners, and places previously blocked by items. Use overlapping strips and a clean reference edge.
On PC, use R when washer rotation improves the angle. If the dirty-looking texture no longer changes, stop spraying and reclassify the remainder. Decoration, a repair state, and a clean low-contrast material can all look suspicious.
Do not use another video’s washing total as your target. Follow the current display and visible change.
Step 4: inspect repair candidates
Make a separate repair pass after clutter and broad dirt are reduced. Look for current task text, highlight, visible damage, or context prompts. Approach from a clear angle and watch for a state change.
No complete official repair list exists for this checkpoint. Do not waste the final sweep repeatedly testing every decorative defect. One careful interaction attempt plus an obstruction check is enough before moving on.
Keep a short list of unresolved candidates and revisit them only after the full boundary is covered.
Step 5: walk one fixed direction
Choose clockwise or counterclockwise and do not cross the center to chase a new clue. Finish the complete outer boundary, then inspect the interior once. Start and end at the same landmark.
At each area transition, say or note: items checked, washing checked, repairs checked, staging point clear. This creates a completion ledger without needing an invented room list.
If you discover work, complete it and resume from the same point rather than beginning the mansion again. Otherwise the easy opening areas receive repeated attention while the last boundary is skipped.
Step 6: use co-op handoffs
Each player should own an explicit area or task family. Reports should include the boundary and unresolved evidence, not only “done.” Swap areas for one final inspection so a fresh camera angle tests the original assumption.
Avoid sending all players to one suspected spot. One person tests it while the others continue their assigned boundary. If progress changes, announce the task family so everyone can narrow their search.
Before rejoining, compare displays and record any mismatch. A reconnect may solve a session issue, but it should be a measured recovery step rather than the first response.
Step 7: test server state
Choose one action known to have worked earlier. If the object or surface responds but progress does not, wait briefly and check another indicator. If several known-valid interactions stop responding, close overlays and reconnect to the official Place ID.
After rejoining, test one small interaction before committing to a full route. Persistence behavior may vary, so this guide does not promise that every prior action survives a server change.
Never use scripts, executors, or automation to find tasks. They create account and device risk and are not part of this guide.
Compact final checklist
- Correct Crystal Clean experience and current server confirmed.
- Live objective read; copied walkthrough totals ignored.
- Every item staging point revisited.
- Item placement distinguished from dropping.
- Dirty-surface perimeters, seams, and obstructions checked.
- Repair pass completed with current prompts, not guessed targets.
- Full boundary walked once in a fixed direction.
- Co-op areas reported and swapped for one fresh inspection.
- One known-valid action used to test progress response.
- Rejoin attempted only after the current state was recorded.
Completion FAQ
What is usually the last task?
There is no verified universal answer. Use live indicators to distinguish an item, dirty patch, or repair before searching.
Why does the house look clean but not finish?
Visual cleanliness may not include a misplaced item or repair, and narrow dirty borders can be hard to see. Reconcile all three task families.
Should everyone search together?
Usually not. Assigned boundaries reduce duplicate work; swap areas only for the final fresh inspection.
When should I rejoin?
After multiple known-valid interactions fail or displays clearly disagree, and only after recording the current state.