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
I thought every mod was loaded into ram and only then processed one by one
thats why 1k+ modlists need super huge amounts of ram for the loading to even begin
or at least thats what I thought
if it aint so Ill go back to subribing to all the small ones
I am just curious if there is any benefit other then ease of install/ management to the "all in one" mods I see
I am just worried that all my super tiny mods will bloat my RW more then one giant mod that compiles funtionality (even tho they tend to be an amalgamation of "stolen" mods more often then not)
Than you for your concise answer!
would there be any benefit to you doing a "all in one" version that includes all dlc?
Minify that: A minify for mods, that lets the player choose what the think should be minifiable or not... We can balance it ourselves and fix weird interactions that could occur by just disabling that thing that we added to the minifiable list.. This could be done with a designator on the orders menu, like a "Minify that" button, which makes a colonist go and minify that... And add it to the list so that from now on, youve got the usual minify buttong on that def..
Id love this, please save me from minify everything <3