Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
we're gunna try this next, but I am just really shocked to see this core mechanic, that i've seen work in multiplayer, somehow still not working in multiplayer after at least 3 years of player feedback and development. I'd understand this a lot more if it were even something as acute as a class based ability that didn't quite work right in multiplayer...but long resting?
You just happened to be playing around a major patch. I recommend freezing your game version to ensure compatibility throughout your playthrough.
https://steamcommunity.com/sharedfiles/filedetails/?id=3077201809
https://steamcommunity.com/sharedfiles/filedetails/?id=3028880921
Oh have that returned, Earlyer we just left and re entered the camp on the rare occations the bug appeared.
If that wont work the player that not hosting could log out for a second, Not a great "fix" but it should work.
I dunno what freezing the game means but we just started a playthrough. Hadn't even gotten past the crash. If we lose this game, its not a huge deal. But if we somehow lose one halfway through act 1? (:
Edit: I just noticed the first guide literally says "freezing the game version" lol.