Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan









Especially when the extent of your modding knowledge is XML Patches
I thought I didn't even have to bother with that, and I can just ignore the version warning?
I'm updating my modpack atm (1000+ mods) to 1.4, and I was going to test all the broken and not updated mods in one sitting, so I'll let you know if it works. Unless you update before then
If that works, party hard. If not it means defs have changed between versions, something's changed in the tent mod this depends on or values have been changed which C# code depends on. However, this mod doesn't have any C# as can be seen by there not being an assembly folder so there's a good chance the lazy fix is all you need.
Is there any way I could check?
I'm thinking of getting into modding so I can fix mods myself lol