Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
Link to revied version:
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2977126988
If Original mod author does not want to have that mod up, gonna delete it. If original mod author wants to use that mod to update his own version, they can do it without notifying me.
That can be attempted, but I fail to see how it would resolve the mod disabling itself when it is enabled and not auto-enabling for a server.
To be sure, I suspect this is an issue with Barotrauma itself more than it is the mod, as I've had the same issue (also unresolved) with Xanmonsters many moons ago in the time long before. I'm just grasping at straws here.
Last update has added feature to disable artifacts effects while in artifactcontainer
Tried manually removing/redownloading all mod files and reinstalling barotrauma, but the issue persists.