Open Recat013 opened 7 months ago
I'm having this exact issue on v17. The only work around I've been able to find was inviting my friend to a new game on the character creation screen (with the same mods etc), then once they've joined successfully, I go to "Load Game" and load into the world that they were unable to join previously.
Has there been much update with this issue?
I have attempted solutions to common problems
Yes
I have checked that my game version is supported
Yes
OS
Windows 11
Platform
Steam
Description
For a few weeks now, when I start up a new game, I get this error line in the Script Extender console.
Osiris Error: 2 error(s), 0 warning(s) in compilation.
Now, normally I would call that a mod issue and look for which mod is causing it. And I've done that. However, I've tested several different mods - including mods that were updated since patch 20 or 21, and the error is always there with any single mod, or a set. Usually, either 2 or 6 errors are reported. The console does not specify what the errors actually are.
Mod content seems to work fine despite this error. However, I can no longer play modded multiplayer, which had been working just fine with a couple friends before. We can start multiplayer with no mods but the script extender enabled, we can both get into our own modded worlds, but we cannot join each others' even with the same mods, or single mod, installed.
Indications
The fact that it happens with any mod, including ones that are very recently updated and also ones that don't claim to require the script extender.
Diagnostic Files
BG3 Diagnostic Data.txt
Steps to Reproduce
Expected Behavior
The other player should be able to join the world and multiplayer begins.
Actual Behavior
The other player connects successfully (checked through network logs) and is kicked back to the main menu at 0% loading. The network log contains an error stating that the host must first take a long rest. This, obviously, is not possible on a brand new save on the character creation screen, and taking a long rest on an existing save did not resolve the issue either.