Dressmaker Characters: All 10 Major Commission Lines

Meet the people behind the commissions

Dressmaker uses customer requests to give individual dresses a purpose. This character reference covers ten names whose major commission lines are confirmed by public Steam achievement descriptions: Prudence, Edith, Priya, Fiona, Dorothy, Vivian, Adora, Alice, Rose and Marie. The index is intentionally gathered on one page. A search for a name before or after Dressmaker title should lead to the same coherent record rather than several near-identical pages.

This Dressmaker guide confirms the existence of those character lines, not an exhaustive set of personally tested requests. We have not completed every character story or verified every numerical condition. Where a specific brief matters, use the wording and values shown in your own installation. A Dressmaker character name helps identify the context; it is not enough information to generate a reliable garment recipe.

Use the character checklist without spoilers

The checklist above lets you mark a major commission line complete according to your own playthrough. It stores that choice locally in this browser. It does not connect to Steam, unlock achievements or inspect a save file. A checked name means only that you marked it complete here. You can change a mark whenever you need to correct your notes, and the count updates with your selections.

Achievement names can hint at Dressmaker story developments, so the checklist hides them until you opt in. Revealing a name does not reveal a verified sequence of commission conditions. If you prefer to discover every story detail inside Dressmaker, leave the option off and use the character names as a simple progress index. Visit the achievement page when you want a broader checklist, including the public crafting challenges.

Prudence and Edith: follow the current request

Prudence and Edith both have major commission lines confirmed by Steam. Their names also appear in the research handoff’s game-related search queries, which makes them useful navigation points. That search interest does not tell us what every player is struggling with, and it does not supply missing story or scoring data. We therefore avoid assigning a fixed wardrobe preference, personality summary or final-order formula without adequate evidence.

If a Dressmaker request from Prudence or Edith is difficult, begin with the same concrete record: exact brief, edition, build, garment state and the customer response. Separate minimums from upper limits. Then compare finished values rather than relying on a sketch. The commission checker accepts either Dressmaker character as context while leaving the actual requirements entirely under your control. It never silently inserts a supposed universal recipe for the selected customer.

Dressmaker: priya, Fiona and Dorothy: keep progress and requirements separate

Priya, Fiona and Dorothy are also confirmed by the public major-commission achievement descriptions. A progress checklist can tell you which character line you believe you have finished, but it cannot tell you what a particular active request requires. Those are different pieces of information. Preserve the current commission’s wording even if you have completed several earlier requests from the same character.

For Dressmaker searches that combine a character name with “quality,” “failed” or “stuck,” the useful next step is usually a specific diagnosis rather than another broad character biography. Record whether the problem concerns a requirement, a missing order, controls or a suspected bug. Our troubleshooting guide separates those paths. A Dressmaker question becomes easier to answer when it includes the condition that is not behaving as expected.

Dressmaker: vivian, Alice and Marie: names do not establish hidden rules

Vivian, Alice and Marie have the same type of official evidence for major commission lines as the other listed characters. A lower presence in one exported query sample does not mean their stories are unimportant or that nobody searches for them. The index covers all ten supported names rather than allowing a small trend sample to determine which characters deserve a record.

A Dressmaker achievement name can suggest a theme, but it is not a reliable source for inventing a full biography or outfit requirement. We keep those boundaries visible. If you are helping another player with Vivian, Alice or Marie, share the actual request and Dressmaker version alongside your suggestion. A Dressmaker design that worked for one order is useful as an example only when its conditions match the task being discussed.

Dressmaker: rose: understand the warning about upper limits

The handoff includes a community discussion about a player whose bars looked full but whose result was not accepted as expected. Replies point toward the importance of upper limits in a particular request. This is a useful prompt to inspect requirement direction. It is not proof that every Rose commission uses the same conditions, nor that every rejection involving Rose has that explanation.

Before changing a Dressmaker garment, check whether each relevant attribute is supposed to be at least or at most a stated value. A maximum is not improved by exceeding it. The checker can compare your entered observation with the exact limit, but it cannot identify the limit from the character’s name. If the Dressmaker values still seem inconsistent after that review, record the precise customer response and consult the version-aware troubleshooting steps.

Dressmaker: adora: report a quality problem precisely

The research includes player reports about difficulty reaching a quality requirement in a late Adora commission. Those reports establish that players encountered a frustrating symptom. They do not, on their own, establish its root cause, affected builds or a universal fix. This companion therefore does not offer a “guaranteed Adora solution” or present an untested workaround as an official rule.

If your Dressmaker quality appears stuck, note the current value, required value, build, selected components and what changed between attempts. Keep construction observations separate from calculations. A useful Dressmaker bug report explains the smallest sequence that reproduces the issue and whether unofficial modifications are installed. If a later official patch addresses the same situation, its wording and version should take precedence over an older community speculation.

Dressmaker: major commissions, side activity and completion

The phrase major commissions appears in the official achievement descriptions for these character lines. It should not be silently expanded into a claim that you have completed every possible interaction, every future update or all optional creative activity. Likewise, completing a garment is not identical to finishing a whole character story. Use the terminology carefully when you record your progress or compare notes with someone else.

Dressmaker also includes independent making and a shop-window path described by official materials. Those activities are relevant to enjoying the workshop but do not automatically establish a character milestone. Check your Steam achievement state when you want confirmation from the platform. The local Dressmaker checklist is a convenient reminder, not an authoritative account of what your game or Steam has awarded.

Dressmaker: keep your own commission record useful

A strong character note identifies the person and the particular request, then records the edition, build, requested limits and final observations. Add the exact response when a result is surprising. If you share a screenshot in a public community, consider cropping unrelated personal details and include enough interface context to distinguish a sketch from a completed garment. This site does not require uploads or private account information for its tools.

The Dressmaker commission guide explains how to turn that note into a structured check. The updates page helps you compare the report with known interface changes. As more verified evidence becomes available, a character reference can grow with versioned examples and reproducible cases. Until then, this Dressmaker index aims to be useful precisely because it keeps confirmed names, player observations and unknown task details separate.