Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
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