Questions using the spouse tag.

[Cniht]

I've got a quick question as I'm trying to add some marital events to spice the 'homefront' up a bit. Like letting your wife run things if you're a ruler and other things. Good and bad events.

Yet I want to be sure on how to use the spouse condition correctly.

To get the even to fire with my Spouse as the target character it would look something like this?

##################################################
#Send your wife to the nunery! #
##################################################
character_event = {
	id = 11000

	picture = "event_intrigue"

	trigger = {
		condition = { type = religion value = catholic }
		condition = { type = gender value = male }
		condition = { type = kingdom }
		condition = { type = is_married }
		condition = { type = spouse }
		condition = { type = age value = 30 }
		condition = {
			type = not
			value = {
				type = age
				value = 100
			}
		}

PS: Ugh one of these days i'll figure out the button to put so I don't lose my indentation [EDIT: I figure out for you ; Cat]

Ok I think I figured it out as a csc switcher, however I still have a question if once changed is it global, like I change it once and then never have to change it again? Or do I have to add 'for' infront of everything with spouse afterward when judging effects.

 

[unmerged(21937)]

How about this:

trigger = {
       condition = { type = spouse value = { type = ruler } }
       condition = { type = age value = 20 }
       condition = { type = not value = { type = age value = 60 } }
}

As this condition fires the event for the ruler's spouse, so any effects you put in affect the ruler's spouse if you don't put any targeting.

 

[Cniht]

Thanks I just put an update of code above which I think I've gotten to work, but your method is much cleaner.

Scratch that Neither mine nor your's seem to give the desired result. Mine loads but it does not augment things correctly because it defaults back to the king as the main person not the spouse. What you presented I cannot get to load.

 

[Cat Lord]

PS: Ugh one of these days i'll figure out the button to put so I don't lose my indentation

It's the button with a #

It creates the tag

:)

  Cat

 

[Cniht]

It's the button with a #

It creates the tag

:)

  Cat[/QUOTE]

Thanks but any help with the CSC problem above? lol.

 

[Cat Lord]

condition = { type = spouse value = { type = ruler } }

is not a valid syntax.

	trigger = {
		condition = { type = religion value = catholic }
		condition = { type = gender value = male }
		condition = { type = ruler }
		condition = { type = is_married }
		condition = {
			type = spouse
			condition = {
				type = and
				condition = { type = age value = 30 }
				condition = { type = not value = { type = age value = 100 } }
			}
		}
	}

This trigger will check you are a catholic male ruler, married, and your wife is between 30 and 100.

Cat

 

[Cat Lord]

This trigger will check you are a catholic male ruler, married, and your wife is between 30 and 100.

Which means that if she manages to get over 100 without this event firing, you won't be able to send her to the covent. You don't really need this check

Cat

 

[Cniht]

Yes that I gather, however the problem is with the effects. I'm trying to make the spouse the primary target of the effects instead of labeling her constantly through the 'for =' part of most commands. It appears 'for =' doesn't work with a lot of the commands it is documented to work with.

 

[Cat Lord]

Yes that I gather, however the problem is with the effects. I'm trying to make the spouse the primary target of the effects instead of labeling her constantly through the 'for =' part of most commands. It appears 'for =' doesn't work with a lot of the commands it is documented to work with.

Like what ? I don't think it's true anymore.

In your case you want to use:

type = death value = spouse

as an effect for this event (to get rid of your spouse definitely).

Cat

 

[Cniht]

Like what ? I don't think it's true anymore.

In your case you want to use:

type = death value = spouse

as an effect for this event (to get rid of your spouse definitely).

Cat

effect = { type = fertility for = spouse value = -5 }
          effect = { type = piety for = spouse value = 100 }

Both of those two are giving me hell when I use them with the ruler as the main target.

type = fertility for = [target char] value = V Note: Additive

The above is from the events doc.
However now that I look at it, piety is not labeled that way. However, I was going to solve this by doing a work around of making the spouse the primary target.

perhaps a random courier event with the condition of her spouse being a king?

PS: The event wasn't really to get rid of her. It has a mean time of firing in 120 months. This would make it on average fire within a 10 year period. 30-50 being the benchmark. The 100 was just so i'm positive it will fire to check right now. Fertility lowered, piety up, chaste added, and a chance at various clerical based education traits. (martial priest etc) by 40-50 she's done with the baby times, so losing fertility isn't really that important, but I wanted to add it for a possible hit if the event fires pre 40. Also it lets me play with tags and know what works and what doesn't.

 

[unmerged(21937)]

condition = { type = spouse value = { type = ruler } }

is not a valid syntax.

Would this be a valid syntax if I change "value" after "type = spouse" to "condition"? Just want to know if I need to use things like that in my own scripting...

 

[Cat Lord]

Would this be a valid syntax if I change "value" after "type = spouse" to "condition"? Just want to know if I need to use things like that in my own scripting...

	trigger = {
		condition = { type = religion value = catholic }
		condition = { type = gender value = female }
		condition = { type = is_married }
		condition = { type = age value = 30 }
		condition = {
			type = spouse
			condition = { type = ruler }
		}
	}

This will trigger for catholic, female, married character, over 30, if they are the wife of a ruler.

Cat

 

[unmerged(21937)]

This will trigger for catholic, female, married character, over 30, if they are the wife of a ruler.

You could have said that changing value to condition was the correct fix, because it obviously was with a look at the script you gave. Besides isn't is_married somewhat pointless in that because if you have spouse you are married?

 

[Cat Lord]

You could have said that changing value to condition was the correct fix, because it obviously was with a look at the script you gave. Besides isn't is_married somewhat pointless in that because if you have spouse you are married?

Strictly speaking yes, but it may save you CPU time by not going any further checking for the CSC condition (I don't know how it is coded).

Cat

 

[Cniht]

You could have said that changing value to condition was the correct fix, because it obviously was with a look at the script you gave. Besides isn't is_married somewhat pointless in that because if you have spouse you are married?

Well I'm not sure how the CK code works but I'd be very scared to use the spouse command without checking the is_married first. Not sure how the variables are set up if someone is not married, but it could be just a junk value which would have some very strange results.

 

[MegaPIMP]

hmmm, did you know that two females that are married get children? Hehehe, be careful with that tag