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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
Is it possible to make to what you build need to be in range of a campfire to work?
Best of both worlds would be: Zip up the Config folder, move the zip elsewhere then delete it. And them once you've loaded your game, you can compare the repopulated files with those in zip file, and just fill in the settings for those mods that loaded different from how you are used to
Navigate to the Rimworld by Ludeon Studios folder (path: [Installed Drive]/Users/[your profile name]/AppData/Local Low/Ludeon Studios/Rimworld by Ludeon Studios) then either:
- delete the Config folder - you will need to reset all your game, and mod settings this way, but it is the simpler option
or
- open the Config folder and check every single file (either in Notepad, or get Notepad++ to read them easier) to see what mod it is associated with (some mods will have renamed these making this easier, but most are just numbered) and delete the ones belonging to removed mods.
Ran into the same issue when the Jewelry mod changed ownership.
Doesn't change that this isnt good for saves. Getting alot of red errors now thanks to it and may need to start a new run.
Oh well... it happens I guess. Better to have the compat.
@Monkey Magic
I had already done that. Standard practice on DLC, and big mod loadout changes...
Is it worth doing for a single mod? I'd assume not?
Hope that doesnt screw up my save