Routes & saves
Official materials confirm three endings at about ninety minutes each. This Drag'n Wash endings guide explains how to plan routes and saves with Official versus Community labels kept clear.
Last reviewed:
Answer first
What you can rely on before any spoiler detail.
Official: Drag'n Wash has three endings, and each ending is about ninety minutes. That is the planning backbone for every replay.
Practical path: finish one discovery clear, keep a hub save from before late branches, then specialize comfort attention on one dragon route per replay. Community discussion commonly orients those routes around Ryan, Alexander, and Conrad.
Exact dialogue trees and trust percentage tables are not published here. Follow on-screen prompts, keep named saves, and use the table below for route focus and risk notes.
This page discusses ending structure, route focus, and late-game save behavior.
If you want a completely blind first clear, stop after the Quick Answer and finish one ending on your own. The rest of the page stays free of explicit sexual detail, but it does talk about multiple endings, credits behavior, softlock risks, and which character routes players commonly chase.
High-level focus only. Official rows are store facts; Community rows are player-oriented planning notes.
Read the Source label column before you treat a cell as hard rule. Official timing and ending count come from store copy. Route names and softlock patterns come from itch comments and player planning habits.
You do not need a proprietary trigger spreadsheet to use this table. Prioritize one route’s comfort arc, finish washes thoroughly, and protect a file before the visit that feels like a lock-in.
| Ending / Route focus | What to prioritize | Save point | Known risk | Source label |
|---|---|---|---|---|
| Any first clear | Learn wash scouting + prompt order | Copy before late branch / credits | Credits continue can loop | Official timing + Community save notes |
| Ryan-focused replay | Ryan washes, chat, and requests | Named pre-late Ryan backup | Missed dirt stalls comfort beats | Community route focus |
| Alexander-focused replay | Alexander visits completed cleanly | Named pre-late Alexander backup | Split attention across visitors | Community route focus |
| Conrad-focused replay | Conrad comfort + prompted request order | Backup before late Conrad visits | Request-order softlock reports | Community softlock notes |
| Completionist weekend | One dragon per replay from a hub save | Hub + active + pre-credits slots | Overwriting the only clear file | Official 3×~90 min structure |
Because each ending is near ninety minutes, one overwritten file can cost an evening. Build a simple slot map before late branches.
Keep one early “hub” save after you understand the wash loop but before major route locks. Keep one active slot for your current ending attempt. When a visit clearly pivots toward a specific dragon’s late arc, copy that file to a named backup before you continue.
Community: using continue after finishing a slot can dump you straight into credits again. Do not rely on a finished file as your branching point. Also avoid experimental credits options such as unstuck kobold, which itch comments link to softlocks. During normal play, Unstick Kobold on the pause menu is the documented recovery tool from the official Kobold Hotfix.
High-level route advice is stable even when dialogue lists are not. Pick the dragon whose presence you want to prioritize, keep their washes thorough, and answer their comfort prompts as they appear. Split attention across every visitor evenly if you are still on a discovery clear; specialize once you are ending hunting.
Ryan draws a lot of search interest. Conrad is often discussed with later-visit caution around request order. Alexander appears in the same cast discussions. Keep expectations soft: these are orientation notes for planning, not long-form official bios.
If a personal request appears, complete it in the prompted sequence. The Kobold Hotfix addressed a known level-8 Conrad request-order softlock, and community troubleshooting still warns that skipping ahead of the visit’s request can softlock later visits. That advice is about order and prompts.
When you specialize, say the focus out loud when you name the save file. A slot labeled “Ryan pre-late” or “Conrad pre-request” is easier to trust at midnight than a generic autosave. That tiny labeling habit is as important as any Drag'n Wash endings tip about comfort priority.
This plan respects the official three-ending structure. If a patch changes branch timing, prompt-following and save hygiene still work.
Players who only want one favorite route still benefit from the same Drag'n Wash endings discipline: name your slots, copy before late branches, and never treat a credits file as a flexible hub.
Keep the plan boring and repeatable. A calm Drag'n Wash endings weekend is three named backups and three focused visits, not one heroic overwrite.
Finish a first ending while learning clean-bar scouting, request order, and credits behavior.
Reload the pre-branch backup instead of continuing a credits-locked file.
On each replay, prioritize one character’s comfort arc and keep washes complete.
Slow down on later visits and credits menus; keep a backup before experimental choices.
Keep labels honest while you plan Drag'n Wash endings. Official means store-page facts: three endings, about ninety minutes each, wash/chat/request loop, adult-only framing, and full controller support on Steam categories.
Community means itch-comment troubleshooting and player route habits: Ryan, Alexander, and Conrad as common focus names; clean-bar leftovers on tails and necks; credits continue quirks; credits unstuck warnings; and Conrad request-order softlocks.
Mixing those layers is how guides overclaim. Use Official numbers for time budgets. Use Community notes for risk checklists. When a patch lands, re-check Options and pause-menu recovery first—Unstick Kobold on pause is documented in the official Kobold Hotfix—then decide whether an older softlock report still applies.
If you only need one takeaway: budget three short-novel routes, protect a hub save, and treat prompt order as part of the critical path whenever Conrad’s later visits appear.
Primary references used for this page. Official store facts and patch notes are separated from itch comment troubleshooting.
Prefer these pages when a patch changes options, softlock behavior, or mod install steps. Label community comments as player reports until an official note confirms them.
Common questions
Official description lists three endings, each about ninety minutes.
Plan separate Drag'n Wash saves before late branches. Continuing a finished slot can dump you into credits, so finished files are poor branching points.
No. Focus on comfort with a chosen route, follow in-job prompts, and keep backups. Exact lists go stale across patches.
Pick the dragon you care about most after your discovery clear—Ryan, Alexander, or Conrad—and protect a named pre-late save.
Community reports flag credits unstuck kobold choices and later Conrad visits where personal requests are completed out of the prompted order.
Continue exploring
