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
Although it's designed for that, it can be used in anything where checking conditions is appropriate. Again, mess with that, and you will change the condition.
From what I can tell it's a simple string comparison.
I don't understand what you mean by that. Is it generally no longer necessary? Or not relevant for the function of MEM?
Where can I find out which variables there are in total and which worlds they cover. I could not find anything in the wiki and the Google search.
Anyway, a habitable planet class would have district_set parameter which is a simple string. uses_district_set is a condition that can be checked against the planet to compare its argument against this parameter. If they match, return true.
It's primarily used in districts to make sure they appear on the right planets. After it was implemented MEM could abandon overwrites for districts and employ simpler system of setting sets for custom planets that match existing ones.