Dressmaker Troubleshooting and reporting a useful bug

What should you record before trying a fix?

A clear report is more useful than repeated random changes. Note whether you use the full Steam release or the itch.io prototype, the version visible in the game, your operating system and what you were doing immediately before the problem.

A report you can copy

Edition and version:
Operating system:
What I expected:
What happened:
Steps to reproduce:
Does it happen again after reopening the game?
Screenshot or relevant save attached:

Back up a save before experimenting with files. This wiki has not verified a universal save path, so it does not publish one by guesswork.

Are prototype bugs still relevant?

The prototype’s 0.5.5 changelog fixed a flounce-sleeve sprite and the ruffle-skirt grainline/name. It also noted an ordering issue for existing ruffle skirts. That is historical information about a specific prototype patch, not evidence that the full release has the same bug.

What about a Mac warning on the prototype?

The itch.io page explains that the prototype was not notarized and includes Mac opening guidance. Read the instructions on the official page for the exact downloaded edition; do not generalise that note into a claim about the Steam build.

Where should a report go?

The official community Discord is linked by the developers. Their August devlog asks players to include a save with bug reports. Use a private support route for files containing personal information.

Review Steam release vs itch.io prototype, PC and Mac system requirements and Sewing guide: a calm practice routine before diagnosing the cause.

Sources: prototype page, 0.5.5 changelog, August developer log.

Which issues have official patch records?

Compare Build 403 patch: bell, lace tags and payment fixes payment, trim and tutorial fixes with Build 410 patch: sketchbook, spools and panel hints rotation, placement hints and tutorial soft-lock fixes. Use the Missing panels and a dress that will not finish for an unfinished dress.