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
This sounds like its probably steam screwing up the files because none of the patches related to Project Rimfactory change things in that way. They simply patch the drones to add the new worktypes.
Sometimes steam fixes the issue itself after a while. However if it doesn't and you can't manage to get it to download properly by resubscribing or verifying the game integrity you can download a copy of my mods from the GitHub linked in the description.
@Nathaan the hacker
I've never heard that one before. It sounds like its unrelated though if it did all worktypes including vanilla ones.
I haven't specifically tried removing a patched in worktype but it should work the same as one loaded normally through a Def. Once its in, its in then the game complains if you try to remove it. Its one of the only Def types I know of that will error if you try to remove it via a patch. You might be able to get around that via some coding but that's beyond my abilities.
When this comes up it's typically I want to have nothing added and only enable the ones I like. The game doesn't take kindly to trying to disable worktypes after they've been added so the only option is to load them if you enable them. That's how all the current optional ones are done. When enabled the patch adds the new worktype and runs the patches to change priorities or worktypes.
It's been requested a number of times in the past. The first issue is it'd make XML Extensions a hard requirement which I don't really want to do. The second problem is it would require quite a lot of time and effort to rework things to make it more modular. So in short its probably not going to happen.
There are existing options to disable some, but not others.