Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Start a new game. Open dev mode and unlock the needed research. Then attempt to build the bench. Doesn't work? Then disable all mods, start a new game and attempt to build the bench there. If this works, it's a mod that's messing up.
You should probably save this state next to make sure you don't have to repeat the process of starting a new game and unlocking the research for the next steps.
So next take your mod list and only enable half of your mods. Load up the game and attempt to build the research bench. If it does work, disable all current mods and enable the other half, then test again.
Whenever you locate the set of mods that reproduces the error, you need to further divide the set until you're left with a single mod that causes it. It's likely you won't need to actually narrow down your mod list to a single mod, as a bit of logical deduction might let you figure out the responsible mod sooner (e.g. it's unlikely a mod introducing new animals will cause this, while a mod changing how researching works is more likely).
This is the quickest way to figure out which mod causes error that I know of. It's adapted from the "Quicksort" sorting algorithm, which is one of the fastest ones in use.