It's a small detail that is bothering me, look at this:
All 3 of these triggers are meant to be used on pops/leaders to check their species.
Additionally, it would be nice to have a
Which translates to:
Then it could just be:
Code:
is_lithoid = {
species = {
is_archetype = LITHOID
}
}
is_organic_species = {
species = {
OR = {
is_archetype = BIOLOGICAL # original trigger did not include pre-sapient classes
is_archetype = LITHOID
}
}
}
is_robotic_species = {
species = {
is_robotic = yes
}
}
is_organic_species and is_robotic_species make that clear enough, so why use is_lithoid instead of is_lithoid_species? I'd rather have is_lithoid be usable in the species scope directly.Additionally, it would be nice to have a
consumes_food or is_biological_species trigger for pop upkeep. To avoid things like that:
Code:
# Biological Upkeep
upkeep = {
trigger = {
is_organic_species = yes
is_phototrophic = no
is_lithoid = no
}
food = @living_standard_food_normal
}
Code:
# Biological Upkeep
upkeep = {
trigger = {
species = {
OR = {
is_archetype = BIOLOGICAL
is_archetype = LITHOID
}
}
NOT = {
species = {
is_archetype = LITHOID
}
}
is_phototrophic = no
}
food = @living_standard_food_normal
}
Then it could just be:
Code:
# Biological Upkeep
upkeep = {
trigger = {
is_biological_species = yes
is_phototrophic = no
}
food = @living_standard_food_normal
}