安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
C:\Program Files (x86)\Steam\steamapps\common\Stellaris\common\traits <vanilla files
common/traits/04_species_traits.txt <paste below into mod this mod file
check for auto modding files in the other files modified listed above
trait_auto_mod_biological = {
cost = 3
auto_mod = yes
category = normal
allowed_archetypes = { BIOLOGICAL LITHOID }
initial = no
randomized = no
species_potential_add = {
hidden_trigger = { exists = from }
from = {
has_technology = tech_gene_expressions
}
}
species_possible_remove = {
always = yes
}
species_possible_merge_remove = {
always = yes
}
potential_crossbreeding_chance = 1.0
slave_cost = {
energy = 1000
}
assembly_score = {
base = 2
}
custom_tooltip_with_modifiers = automodding_trait_biological_tooltip
}
You may have a mod conflict. Or try unsubscribing and resubscribing - possible an old file is conflicting, but I doubt it because trait files are full-override only.
In what circumstances are you seeing it duplicate? And do you mean the species trait, leader trait,. or both?
See this screenshot: https://www.screencast.com/t/k3yBI1RN
after 3.6, cybernetic pops can choose there own versions of machine traits, but can only add/remove if they are in cybernetic ascension empire, and merge-add/remove is not allowed. this problem also blocks removing cybernetic trait(or merge-remove), one of changes of this mod.
@Raegorn - every trait changed due to changes PDS made to gene-modding. It's now up-to-date. However, this mod does not make any changes to assimilation. Instead of assimilating, use gene-modding to apply templates (this was common gameplay before 3.2).
Now that I think of it, I don't recall having that problem before 3.4 so I wonder if it's a new bug or if a mod could have messed things up.