安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
2 
举报此帖
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.