Medieval Dynasty Hunting Set Won’t Craft in Co-op? Check Each Player and the Patch

Start with the build that the official fix names

The official announcement archive dates Patch 2.7.0.4 on the Public Branch to October 7, 2026, and names the exact co-op symptom: clients unable to craft the Hunting Set even if the host had it. This makes branch/build comparison the first useful check—not a promise that every similarly worded failure has the same cause.

1. Ask host and affected client to read their exact game version and branch from their own Steam installation; record both values before changing the shared world.
2. If either player is not on the Steam PC Public Branch covered by the note, do not assume the fix is present. Check that platform's current official release notes or in-game build first.
3. If both are on the relevant Public Branch but one is older than 2.7.0.4, update through Steam's normal channel, then retry the same recipe once.
4. If both already show 2.7.0.4 or a later Steam Public Branch build and the symptom remains, continue to the player-specific DLC, recipe and ingredient checks rather than repeatedly reinstalling.

References: Render Cube: Medieval Dynasty official Steam announcements

Separate the host’s DLC from the client’s own access

The official patch note says it fixed a client crafting issue even when the host had the Hunting Set. It does not say that the host's DLC automatically provides another account with ownership or entitlement. Treat each player's access as its own observable check and avoid claiming a specific Steam Family Sharing or console entitlement rule unless the relevant platform's current documentation confirms it.

References: Render Cube: Medieval Dynasty official Steam announcements · Render Cube: Hunting Set DLC announcement

Use a controlled retry and capture a useful report

Avoid changing multiple variables in the shared session. Record the build, platform, player role, DLC access and exact recipe state; change one thing and retry. This helps distinguish a known patch-level issue from missing local prerequisites without risking saved progress.

1. Verify the item is one of the Hunting Set's documented items: the DLC announcement describes two outfits and four weapons made from legendary-animal materials/trophies.
2. Record separately for host and client: platform/storefront, game version/branch, whether the recipe appears, whether the DLC is listed for that player, and which ingredient is shown missing.
3. After an update, fully close and reopen both clients before testing again; keep the same save/session and change no unrelated settings for that retry.
4. If unresolved, post a concise, redacted report in the official support channel. A Steam community discussion may show similar reports, but treat player replies as unverified and do not post account data or private save files.

References: Render Cube: Hunting Set DLC announcement · Medieval Dynasty Steam Community Discussions

If the patch and prerequisites match but the client still fails

A matching Steam Public Branch number narrows the explanation; it does not prove that every recipe state or entitlement is correct. Keep the report narrow enough for another player or support agent to reproduce, and avoid risking the shared village to chase an unverified theory.

1. Save a written note of the exact build, host/client role, DLC display state, recipe visibility and missing-material message before another change.
2. Repeat the same recipe check once in a fresh session after both clients restart; do not delete the shared save, dismantle buildings or transfer rare trophies as a diagnostic shortcut.
3. If the client still differs from the host, use the publisher's support route with a redacted description. In community threads, label the case as a player report and include platform/build so older advice is not mistaken for a confirmed current fix.

References: Render Cube: Medieval Dynasty official Steam announcements · Medieval Dynasty Steam Community Discussions

Before you play

• Record host and client platforms, storefronts, versions and branch before editing a save.
• Compare against the October 7, 2026 Steam Public Branch 2.7.0.4 note; verify console versions separately.
• Check DLC access and recipe visibility for each player independently; host purchase is not proof of guest entitlement.
• Read the exact missing-ingredient prompt before moving inventory or changing storage.
• Retry once after normal update/restart, then escalate with redacted version and role details.

Frequently asked questions

Sources & revision notes

Editorial revision: November 6, 2026; not a gameplay test date. The reference notes identify source limits and version differences.

1. Render Cube: Medieval Dynasty official Steam announcements (Official)

   Official Steam announcement archive checked November 6, 2026. The visible dated Public Branch posts include patches 2.7.0.3 (September 25) and 2.7.0.4 (October 7), plus the Wild Game update post (September 22). These notes establish what those posts say, not the current build installed on every platform.

2. Render Cube: Hunting Set DLC announcement (Official)

   Official Steam product/announcement information checked November 6, 2026. The DLC description says it adds two outfits and four weapons crafted using legendary-animal spoils; ownership and content availability should be checked separately for each co-op player and storefront.

3. Medieval Dynasty on Steam (Official)

   Official Steam product page checked November 6, 2026. Used only to identify the Steam PC product, not to infer console branch parity.

4. Medieval Dynasty Steam Community Discussions (Community)

   External user-generated discussions. Posts may be outdated, anecdotal, or platform-specific; they are not official support or GamerWin-verified solutions. No discussion text is copied.