CDCoop

Beta notes

Before you test.

The beta is an experimental testing build. These notes are for people who already received it.

Updated 14 October 2026

What has been tested?

Early two-PC sessions on 10 October connected players through Steam and displayed a remote character with equipment. Those tests also showed jitter, mount problems, differences between the players' worlds and a later session stall.

Fixes and further multiplayer work have continued since those sessions. An offline check or a launcher update does not establish that a whole playthrough works. Shared quests, combat, travel and persistent progress still need full multiplayer validation.

Before starting a session

  • Use the instructions that came with your specific beta build. Older testing instructions can differ from the current launcher.
  • Both players need a supported Steam game installation and matching, current mod builds. A game update can make an older beta incompatible.
  • Keep an independent backup of important saves. Separate mod progress is a development goal; the beta is not a guarantee of save or cloud isolation.
  • Choose a short, repeatable test rather than committing an important campaign to the beta.

Using the current beta launcher

  1. Start Steam and sign in. Open the launcher supplied with your build under the same Windows account.
  2. Use Choose game to select CrimsonDesert.exe inside the game's bin64 folder if the location is missing or has changed.
  3. Use Check updates and wait for verification to finish. The launcher checks the launcher and mod updates separately.
  4. Use Play once it is available, then follow your build's session instructions. If the launcher reports a compatibility problem, keep the message for your report.

Play requires a successful online update check. An unavailable service or unverified files can leave it blocked even when the game itself works. Do not skip the check or combine files from different builds.

What to pay attention to

Compare what each player actually sees: character movement, enemies, mounts, time of day and the result of the same interaction. Record whether the problem starts on joining, after travel, during combat or when someone leaves.

Keep the first test focused. If progress differs between players or a save warning appears, stop that test and report the exact message before continuing.

For update errors, crashes and reporting steps, see Beta support. For public release information, see Availability.