DRESSMAKER DATABASE / COMMISSIONS · CHECKED SEPTEMBER 28, 2026
Dressmaker Commission Requirements
Read a commission as a budget plus the attribute limits the customer asked for.
What a commission record contains
A commission row describes one request in four parts: the NPC who asks, the budget attached to the request, the attribute values the customer wants held between a minimum and a maximum, and the date the source behind those numbers was last read. The row is a reading aid, not a walkthrough. It states what the request appears to demand so you can decide what to sew before you spend materials.
Once rows exist, the index lists them as cards below this section. Until then the page shows an empty state, because a commission table filled with guessed numbers would be worse than no table at all.
The four-step reading loop
Every request can be worked through in the same order, whether or not a record for it has been published yet.
- Read the request. Write down the budget and every attribute limit the customer states. Treat anything the interface does not show as unknown rather than as zero, because a missing limit is not the same as a limit of zero.
- Plan the garment. Pick a pattern and a fabric that can plausibly meet those limits, then note the cost of each part. The fabric reference and the pattern reference list the fields this site expects to verify for that comparison.
- Check the numbers. Enter the request values and your candidate outfit into the commission checker. It compares the two sets and shows where the garment falls below a minimum or crosses a maximum.
- Deliver and review. After a delivery, compare what the game reported with what the checker predicted. A mismatch is useful evidence: it means a field in this reference is wrong or incomplete, and it gives the next check something specific to look at.
How a record is encoded
Budget is stored as a single number unless the source itself states a range. Attribute expectations are stored as pairs of limits, a floor the outfit should reach and a ceiling it should stay under, because a request can reject a garment that overshoots as easily as one that falls short.
The checked date travels with the row so a reader can judge how stale a number is. A row is only published when its source type is recorded alongside it: official announcements and community reports are labelled differently, and neither is presented as the other.
Why nothing is published yet
At the September 28, 2026 check, no traceable source listed a named NPC request together with its budget and its attribute limits. Community discussion covers commissions in general terms, but a general statement cannot become a row without inventing the specifics. The empty state is the result of the check, not a missing feature.
How evidence becomes a published record
A candidate record starts as a note: what was seen, where, on what date, and which fields the source actually stated. It is promoted only when the NPC, the budget and at least one attribute limit can all be pointed to in that source. Anything else is left out of the row and reported as unpublished when a record page is generated.
Rechecks are logged against the same snapshot date as the rest of the site. The source register lists the posts, Steam pages and community guides currently in scope, so you can see which ones have been read and which are still waiting.
Frequently asked questions
What is a commission in Dressmaker?
A commission is a customer request: an outfit the player is asked to make, with a budget and a set of attribute expectations attached to it. This reference stores each request as a structured record so the numbers can be compared instead of remembered.
Why is the commission index empty?
Each row needs a dated source that states the NPC, the budget and the attribute limits together. No checked source has supplied that full set for a named request yet, so the index stays empty instead of filling the gap with estimates.
How do I check a request I already have?
Open the commission checker, enter the budget and the minimum and maximum attribute values shown in the request you are holding, then enter the values of the garment you built. The checker compares the two sets and reports a pass or a fail against your input.
Where do the budget numbers come from?
A budget is published only when a source states it: an official post, a Steam announcement, or a community report that can be reopened and read. A figure seen once in an unlinked screenshot is treated as unknown and stays out of the table.
Does the checker solve a commission for me?
No. The checker does arithmetic on numbers you type, and it does not search for an outfit or promise a delivery outcome. Treat its output as a test of one candidate garment, not as a finished answer to the request.