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. :/