A PC-and-console campaign suddenly rejects familiar mods. A compatibility badge may not tell the full story.
Don't delete the save yet. Larian requires everyone in modded cross-play to use identical mods and identical versions. “Available on console” doesn't prove that a PC mod and its console counterpart are currently on the same build.
On October 10, 2026, a player reported that console friends could no longer join a campaign that had previously worked. Even mods labelled for console use were rejected. Someone suggested a mismatch after a PC-side update. That is a possibility, not a verified explanation for this case.
Same mod name is not enough
Keep existing saves untouched. Compare both the enabled mod lists and their version numbers. The game's verification window may offer to download, enable, update or downgrade mods. Read those options before changing anything.
If it still fails, try a separate new lobby without mods. If that fails too, investigate connectivity or cross-play settings. The adventuring party is ready; apparently the mods showed up in different timelines.
Bottom line: a failed join doesn't mean the campaign has been erased. Match the versions first. Neither the exact cause nor a successful fix for the October 10 report has been confirmed.
Sources (no story spoilers)
