安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
Well, at least that save was a fun run while it lasted.
In descriptions of moddb versions it's always clarified what they are and aren't compatible with.
Moddb good, steam bad.
Warband engine is rather inflexible when it comes to updates, it's not, say, Skyrim or FO4 which are made to be as mod- and update-friendly as possible.
So whenever you're considering updating an M&B mod while still playing it you have to carefully read the changelog and think twice. We try our best to make updates compatible but sometimes it's just not possible (but at the same time the update has to be released because it fixes critical bugs).
You're too optimistic.
You should rather ask "how can I know there won't be any problems?". It's programming, it's complicated, and the realistic truth is that updates "fix some bugs, add others". And existing progress is especially vulnerable to such updates.
You should never auto-update anything hoping it will be fine, you should always assume the opposite, and only update things when you're more or less certain (after reading the changelog and any other notes left by the devs regarding the update). Auto-updates is the first thing you should find & disable after installing ANY software.