DRESSMAKER CORE TOOL · YOUR OWN VERIFIED NUMBERS
Dressmaker Commission Checker
Test an outfit against a budget and attribute limits using only values you enter.
Published commissions and material stats are still being checked. You can test a community record manually; the checker labels every result as incomplete when an input is missing.
Enter requirements to begin
Cost: Unknown
Attributes use the labels shown in your game or source. Unknown values are never treated as passing.What the checker does
The checker is a comparison tool, not a source of game data. You supply a budget, a cost, minimum attributes, maximum limits and the values you believe your outfit reaches. It then reports which rows pass, which rows fail and which rows it cannot judge because a field was left empty.
Two modes exist. A saved commission fills the budget and requirement fields from a published database record, and custom entry lets you type the figures yourself. Both modes run the same comparison and neither one changes the numbers you entered.
What it will not do
It never invents missing data. If a fabric, pattern, accessory or commission record is not published, the checker does not guess a cost, an attribute or a requirement to fill the gap. The selectors are empty while the datasets are empty, and that is the intended behaviour rather than a bug.
A blank attribute never counts as a pass. Unknown is treated as unknown, and the row is reported as unchecked. The tool also refuses to call a combination successful when only one side of a comparison has been entered, so a missing budget or a missing cost cannot produce a pass.
How to read a result
Each row names the attribute, the value you entered and the value it was compared against. A pass means your figure cleared the threshold in this test. A fail means it did not. An unchecked row means the comparison could not run, which usually points at a typo in a label rather than a problem with the garment.
Fix the typos first, then look at the failures. A row that fails by a wide margin is worth a material change. A row that fails by a point is worth re-measuring in the game, because small differences often come from the input rather than the pattern.
Verified records and community numbers
A verified record belongs in the database and comes with a source and a check date. Those are the entries listed in the source register and on the commission pages. A community-reported number is a player's observation: useful for a test, not published as a requirement.
Keep the two apart when you write a result down. A passing check against a community number confirms that the report is self-consistent, not that the game uses it. When the corresponding database page fills in, the saved record and the report can be compared directly. The fabric list and the pattern list are the pages that will carry those values.
Frequently asked questions
What does the checker actually compare?
It compares the numbers you enter. A budget against an outfit cost, minimum attributes against your outfit values, and maximum limits against the same values. Every comparison uses your own figures, because the published commission and material sets are still being checked.
Why is a blank attribute never a pass?
An empty field means unknown, and unknown is not evidence. If you leave an attribute blank the checker reports that row as unchecked instead of passing it, so a missing value can never be mistaken for a garment that meets the requirement.
Does the checker use official game values?
It uses only what is loaded into it. Saved commission records and material data come from published database entries once those are verified, and the datasets are currently empty. Until then every result is based on values you type in yourself.
Can I use a community-reported number here?
Yes, but the result stays a test rather than a verified answer. Enter the community figure, keep the source link, and treat the outcome as a check on that report. A community number never becomes a published record just because the checker accepted it.
Why are the saved commission selectors empty?
The commission, fabric, pattern and accessory datasets are published but not yet populated, so the selectors have nothing to offer and the tool falls back to custom entry. Typing values by hand still works, and the selectors fill in automatically as records are verified.