Craft Pot [DS, ROG, SW, DST]

Craft Pot [DS, ROG, SW, DST] on Your Don't Starve Together Server

Craft Pot turns the crock pot into a cooking assistant: a slider next to the pot lists every known recipe — including modded ones — and hovering shows the required ingredients plus the resulting hunger, health, and sanity values. As you drop ingredients in, the mod predicts which dishes are still possible, highlights completed recipes in green, and flags ambiguous outcomes in teal. It works with any four-ingredient pot, including Warly's portable one, and offers full controller support.

Since Craft Pot is a purely client-side mod, each player decides individually via the Steam Workshop whether to use it — there's nothing to configure on your server.

Tip: Especially handy for newcomers in co-op sessions, cutting out most of the guesswork around cooking without any host-side setup.

Plan the rollout and operation

Craft Pot reduces external lookups and suits groups with new cooks or many recipe mods. Check that the panel recognizes ingredients from every installed content mod and that controller users can reach the same information. Decide whether live filtering fits the intended difficulty; on a discovery-focused run it can remain optional. If results are wrong, test Craft Pot with only the affected content mod before changing the shared world.

For rollout, a clean client profile on the matching DST version is enough. Back up personal settings, enable only this mod, and connect to the existing world. Check the interface, hotkeys, cave travel, reconnecting, and combinations with other client mods. Because the server does not require the feature, a player should still be able to join without it. Publish the Workshop ID as a recommendation rather than a hidden requirement. After a DST update, test from a fresh profile first; stale interface files or saved options are easier to isolate locally than inside a large collection. If problems appear, the affected player can disable the mod and add other convenience extensions back one at a time. Pure client functionality does not require a world rollback or changes to cluster.ini.