September 25 Update: Solo Quota, Shop Prices and Co-op Fixes

Which part of your run needs a recheck?

This is a dated patch digest, not a replacement for every monster or progression guide. Find the situation you actually encountered, then follow the linked system guide. A developer fix describes an intended correction; it is not a guarantee that every future session is free of a similar symptom.

Dated changes in the official announcement

The notes below are a compact source-backed change record. Use them to identify what to retest, rather than applying an old workaround automatically. The announcement supplies no complete price sheet, guaranteed monster route or new damage chart.

• Solo: no quota threshold in the first four levels of Chapter 1.
• Shops 2–5 start at higher prices, with further increases in shops 4–5. Earned gold is no longer capped on area transitions.
• Ear does not aggro while walking to a new spot and abandons unreachable destinations.
• Anchor pathfinding now follows its route more reliably.
• Mimic cauldron attack motion, dropping and headwear placement were corrected; attaching a cauldron no longer teleports it.
• Missing shops after transitions and inconsistent death/revive states between players were fixed.
• Castle 2 descending lifts no longer push crouching players below the floor. Castle vertical-lift floating and hand shaking were corrected.
• Violin rotation during camera movement was fixed.
• The invisible wall by Cracken no longer obstructs detached body parts.
• Quota marker visibility, elevator-call prompts and chapter-page navigation were corrected; tavern music follows the Music slider.

Do not silently reconcile different chapter labels

The September 25 wording refers to the first four levels of Chapter 1, while September 10 described the first four chapters as one level each. The announcements do not reconcile those labels. Read the current chapter/level selector and quota display; this wiki does not invent a replacement chapter table.

For practical planning, the on-screen target is the input that matters. Record that target before using a calculator. If your visible labels differ from either dated announcement, keep both the screenshot and the build context in a report instead of renaming levels to force the sources to agree.

A useful follow-up report

After installing the update, retry only the specific interaction that failed. Describe the expected result, the result you saw, and the steps another player can repeat. Include whether you hosted or joined, which location was active, and whether the issue survives a fresh session. Avoid deleting saves or changing unrelated system settings just because a patch mentions co-op.