An independent guide to Sort Them Ducks

Who runs this site

Sort Them Ducks Guide is run by Yawen Guides, a small independent guide project. We are not connected to the game’s developer or publisher, and we do not offer paid support.

How the guides are made and updated

Guides are compiled from the developer’s official patch notes and announcements, the Steam store and achievement pages, and other public sources such as community findings. Every guide lists the sources behind its answer, so you can check the original wording yourself.

When the developer publishes a patch, hotfix or official announcement that changes how something works, we review the affected guides and update them. The date each page last changed is shown in the “Recently updated” list on the home page and in the sitemap.

Found an error?

If a step is wrong, out of date or unclear, please tell us through the contact page. Include the page address, what you saw in the game and your game version if you know it. We check reports against the sources and correct the guide when the evidence supports the change.

What the site covers

Start with the how-to-play guide for the sorting loop, then use the egg route, category reference and achievement pages for a specific goal. Troubleshooting pages separate a missing collectible from a completion requirement so a player can choose the relevant next check.

This is an unofficial fan guide. It is not the game developer, publisher, Steam or an official support service. The official store and developer announcements are linked from the guides where they provide the evidence.

How we check sources, and what we have not tested

Each guide lists the sources used for its answer. A developer statement, a Steam achievement description and a community finding are different kinds of evidence; community findings should not be read as a guarantee from the developer. Achievement conditions that Steam leaves blank are labeled as third-party documented wherever they appear.

Dates in source notes, such as “read 21 October 2026” or “checked August 20, 2026”, record when the material was reviewed. A source-check date is not proof that every step was retested in the current game build. Unless a page explicitly describes its own testing, treat its steps as a summary of the linked sources rather than hands-on test results. Suggested routes and orders, such as the egg route or an upgrade order, group documented information into a practical sequence; they have not been timed or benchmarked against alternatives unless the page says so.

Patch notes describe fixes for the build they were written for. They are historical evidence, not a promise that a current problem or an already damaged save can be repaired. Game patches can change locations, counters and unlock conditions. Compare the version and wording in your game with the cited announcement before repeating a long route. If the page does not establish a detail, treat that detail as uncertain rather than an official rule.

Limits of the guidance

No page promises that an achievement will unlock or that a troubleshooting suggestion will repair a particular save. Keep your own progress and use the developer’s official support channels for account or game defects. Do not post passwords, authentication codes or private account information in public discussions.

Read the privacy policy for information about advertising and analytics, and the disclaimer for affiliation and content boundaries.