If it is an Tradition, you only need to set the ai_will_do Value to 0.
Oh yeah I have done that too, but the mod add's more like tradition slots from the vanilla 5 to 100.
can_pick = {
is_ai = no
}if statements or inside of list builders (e.g., every_living_character). When you're writing things like decisions, or traditions, they usually have some specific thing that is similar to limit, which might be can_pick like here, or is_valid or is_valid_showing_failures_only.Like I mentioned in another reply, it add's more traditions from the vanilla 5 that you can choose it adds a 100. Heres the whole thing. Could it be that I can't make it player only because it's a culture modifier?
Making it player only should be possible on anything that lets you use a trigger, it shouldn't matter if it's culture related.
martial_custom_male_only = {
type = martial_custom
parameters = {
martial_custom_male_only_combatant = yes
}
culture_modifier = {
culture_tradition_max_add = 100
}
can_pick = {
is_ai = no
} ###################### <------------------------ This line shouldn't exist
trigger_if = {
limit = {
has_game_rule = default_gender_equality
}
always = yes
}
custom_tooltip = {
text = martial_customs_trigger_maleonly_malepref_or_equal
trigger_if = {
limit = {
has_game_rule = full_gender_equality
}
OR = {
scope:character = { has_realm_law = male_only_law }
scope:character = { has_realm_law = male_preference_law }
scope:character = { has_realm_law = equal_law }
}
}
}
custom_tooltip = {
text = martial_customs_trigger_maleonly_or_male_pref
trigger_if = {
limit = {
has_game_rule = inversed_gender_equality
}
OR = {
scope:character = { has_realm_law = male_only_law }
scope:character = { has_realm_law = male_preference_law }
}
}
}
}
ai_will_do = {
value = 1
}
}At first I thought it did haha because the AI wasn't doing anything but, then they started, guess I'll have to put more blood, sweat and tears into it thank you for the help tho.
If you attach the .txt file for traditions, or a .zip file of the mod I can take a look at it today.
Yeah here you go, nothing fancy the main mod thingy is in traditions --> pillars. Thank you again.
Oh oh oh—okay, I see what happened. I misunderstood what you were trying to do.
martial_custom_male_only, martial_custom_equal, or martial_custom_female_only. That means the AI is getting access to this as well, without ever having to pick it. So if you give this is_ai = no it won't stop a culture from getting it on game start, it will only prevent the AI from ever changing it later._player at the end (e.g., martial_custom_male_only_player), just to differentiate them from the base game's martial traditions, then if you want a tradition to exist for only the player when the game starts, you're going to want to create an effect in game_start_after_lobby on_action (which can be found in common\on_action\game_start.txt). Currently, there are two effects in there called game_rule_full_gender_equality_effect and game_rule_inversed_gender_equality_effect. I would put the effect you create after those, as it will still allow the gender equality game rules to work, which will allow the player's mod tradition to appropriately reflect the game rules they chose. every_player = { # Check every player
culture = {
switch = { # Check their martial tradition and change it to the appropriate player-only one
trigger = has_cultural_pillar
martial_custom_male_only = {
set_culture_pillar = martial_custom_male_only_player
}
martial_custom_female_only = {
set_culture_pillar = martial_custom_female_only_player
}
martial_custom_equal = {
set_culture_pillar = martial_custom_equal_player
}
}
}
}is_ai = no to the can_pick block in the tradition itself.