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.