安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
If however, you install another mod that does the same and that happens to place its species at the same spot then it'll cause conflicts, as the
portraits = {
"human"
"humanoid_02"
"humanoid_03"
"humanoid_04"
"humanoid_05"
"xevil"
would get overwritten by
portraits = {
"human"
"humanoid_02"
"humanoid_03"
"humanoid_04"
"humanoid_05"
"other race added by another mod"
or vice versa, depending on your loadorder.
A mod that does that for example would be the morjan humanoid mod, you'd have to decide which one you want and couldn't play with both.
And there is always a possibility that someone else makes a great looking humanoid mod and it would be a shame if people would be forced to decide on which one they want.
Putting this mod into its seperate phenotype however ensures that the only way to cause conflicts would be if someone releases a species mod with the exact same phenotype, which is far less likely.
As for the part of being playable by the AI, I know mods that add their own phenotype for their races like silfae's and still appear as AI empires, but I still have to figure out where the difference to my mod lies.
Their species_classes.txt is the same as mine (apart from the names and stuff) and the other txt files just define graphical things like bodytypes, hairs and clothing for different jobs. :/