In 00_species_traits.txt, a trait looks like:
trait_adaptive = {
cost = 2
opposites = { "trait_nonadaptive" "trait_extremely_adaptive"}
modifier = {
pop_environment_tolerance = 0.10
}
}
If I want to add a new habitability trait with a mod, I need to make the trait, and then find every other habitability trait and change its opposites variable.
I'd like to be able to define static constants at the top of the file like
@species_trait_category_habitability = { "trait_nonadaptive" "trait_adaptive" "trait_extremely_adaptive" }
and then change each of the traits in question to have
opposites = @species_trait_category_habitability
(In 00_scientist_traits.txt, @categorybonus looks kind of like a static constant like I'm looking for, but the @ syntax failed when I tried it.)
This way, if I wanted to add a new habitability trait, I would just need to change the static constant up top to fix the opposites function. I think this would also be easier to read and interpret.
Having the ability to do this would probably also make some other parts of modding easier.
This example doesn't make it look like too much of an issue, but if I wanted to add a scientist expertise trait for repeated techs or something, the list of expertise traits is 12 long already, and I don't want to have to keep changing that.
This would make a trait its own opposite, but my best guess at how opposite checking is internally coded suggests that should not be a problem.
Is this possible, and is there a place I can go to look for answers to syntax questions like this?
trait_adaptive = {
cost = 2
opposites = { "trait_nonadaptive" "trait_extremely_adaptive"}
modifier = {
pop_environment_tolerance = 0.10
}
}
If I want to add a new habitability trait with a mod, I need to make the trait, and then find every other habitability trait and change its opposites variable.
I'd like to be able to define static constants at the top of the file like
@species_trait_category_habitability = { "trait_nonadaptive" "trait_adaptive" "trait_extremely_adaptive" }
and then change each of the traits in question to have
opposites = @species_trait_category_habitability
(In 00_scientist_traits.txt, @categorybonus looks kind of like a static constant like I'm looking for, but the @ syntax failed when I tried it.)
This way, if I wanted to add a new habitability trait, I would just need to change the static constant up top to fix the opposites function. I think this would also be easier to read and interpret.
Having the ability to do this would probably also make some other parts of modding easier.
This example doesn't make it look like too much of an issue, but if I wanted to add a scientist expertise trait for repeated techs or something, the list of expertise traits is 12 long already, and I don't want to have to keep changing that.
This would make a trait its own opposite, but my best guess at how opposite checking is internally coded suggests that should not be a problem.
Is this possible, and is there a place I can go to look for answers to syntax questions like this?
