Commissions reference
How client requests are structured, what each one asks for, and which requirements are confirmed rather than community-reported.
REFERENCE INDEX · CHECKED SEPTEMBER 28, 2026
Every system this site tracks, grouped by the task you are trying to finish.
This index is the map for the whole reference. It is organised by what you are trying to do — look something up, run a decision, check whether something changed, or trace where a claim came from — rather than by page type. Each entry says what you get for opening it.
How client requests are structured, what each one asks for, and which requirements are confirmed rather than community-reported.
Fabric entries with the attributes they contribute, plus a clear label for any value that is not published in the checked source.
Garment patterns and the shapes they produce, so you can match a pattern to a commission brief before you cut anything.
Accessory entries and what they add to a finished outfit, with the same source labels used everywhere else on this site.
The milestone list with its global unlock context, useful as a checklist for progression rather than a reward table.
Test a saved or custom commission against a budget, minimum attributes and your outfit values, and see which constraint fails.
Why no ranking is published yet, the metric and roster a published order will require, and how to compare two options without one.
The dated record of confirmed changes, kept separate from community reports that have not been reproduced.
The confirmed empty state for redemption codes, what would have to be true before a code is listed, and what to watch instead.
Every public record with its source type, scope and check date, so you can trace a value back to what supports it.
Task-based walkthroughs for the parts of the game that need more than a table, such as preparing for a commission.
The verified store, news and achievement surfaces, the status of any community board, and how to judge an unofficial space.
Who publishes the site, how it is funded, and the editorial rules that decide what gets published and what stays out.
The whole loop in order, for a first session that ends with a delivered garment.
A repeatable way to read a request and decide what to sew before spending materials.
Which values to write down, in what order, and how to re-check them later.
Bodice or skirt, grain alignment, and the layout order that avoids wasted cloth.
Trade cost against the attributes a request names, without guessing missing values.
The assembly order, and where to pause and check instead of sewing straight through.
Test one variable at a time and record the result instead of trusting a formula.
When an accessory helps, when it wastes money, and how to verify the change.
The two income routes, and how to treat a community price estimate honestly.
A triage order for problems, from user error to a confirmed bug worth reporting.
Two things get published: values that a named source supports, and explanations of systems that can be reproduced by a reader. Everything else stays unpublished. Notes collected during research, half-finished tables and community figures that nobody has reproduced are not turned into pages, because a published page looks authoritative whether or not it is correct.
Where a value is missing, the page says it is not published in the checked source rather than estimating it. That is why some entries read as incomplete: the incompleteness is the finding. Alongside each claim sits a source type — official or community-reported — and the date it was checked, so a reader can weigh it instead of trusting the design.
A new page has to earn its place. It is added when a topic can be checked against a source, when it answers a question a reader is actually asking, and when it is not already covered somewhere in the groups above. Cosmetic pages that repeat existing content are skipped on purpose.
Each group grows at its own speed: the game reference grows as values are verified, the tools group grows when a decision cannot be explained in prose, and the status group grows every time an update ships. If a topic you need is missing, send it through the contact page and describe the task, not just the title.
Every system this site tracks: commissions and their requirements, the fabric, pattern and accessory references, the achievement list, the commission checker, the ranking method, the dated status log, the codes status and the source records behind each claim. Pages are grouped by the task you are trying to finish.
It means a claim is tied to a named source type — official or community-reported — and carries the date it was checked. Numbers that no checked source publishes stay marked as unknown rather than estimated. A page will say an item is not published in the checked source instead of filling the gap.
Send it through the contact page and describe the task you are trying to complete rather than a page title, because that is what decides whether a new page is worth writing. The index only grows when a topic can be checked and something is not already published in the checked source.