36) FIXED IN 1.02: Etates General event bug.

[C.N.]

Etates General event bug.

There seems to be a bug in the Etates General event:

################################
# Calling the Etates General   #
################################

character_event = {
	id = 1959
	picture = "event_intrigue"

	trigger = {
		condition = { type = is_independent }
		condition = { type = has_vassal }
	}

	mean_time_to_happen = {
		months = 180
		modifier = {
			condition = {
				type = not
				value = {
					type = gold
					value = 1
				}
			}
			factor = 0.1
		}

	}

	action_a = {#Don't Call them
		effect = { type = prestige value = 5 }
	}

	action_b = {#Crave small contribution
		effect = { type = gold value = last_month }
		effect = { type = prestige value = -10 }
	}
	action_c = {#Crave large contribution
		effect = { type = gold value = last_month }
		effect = { type = prestige value = -50 }
	}
}

As you can seen, you get the same gold amount for both the b and the c choice. Maybe option c should have last_year instead?

 

[FrEDa]

There seems to be a bug in the Etates General event:

################################
# Calling the Etates General   #
################################

character_event = {
	id = 1959
	picture = "event_intrigue"

	trigger = {
		condition = { type = is_independent }
		condition = { type = has_vassal }
	}

	mean_time_to_happen = {
		months = 180
		modifier = {
			condition = {
				type = not
				value = {
					type = gold
					value = 1
				}
			}
			factor = 0.1
		}

	}

	action_a = {#Don't Call them
		effect = { type = prestige value = 5 }
	}

	action_b = {#Crave small contribution
		effect = { type = gold value = last_month }
		effect = { type = prestige value = -10 }
	}
	action_c = {#Crave large contribution
		effect = { type = gold value = last_month }
		effect = { type = prestige value = -50 }
	}
}

As you can seen, you get the same gold amount for both the b and the c choice. Maybe option c should have last_year instead?

I've had 3 of these and I'm quite sure I noticed a difference in at least one of those (the one I checked)..

 

[unmerged(23737)]

I've had 3 of these and I'm quite sure I noticed a difference in at least one of those (the one I checked)..

Maybe but i'm fired that event manually and the b and c option costs the same ammount of money. So i think CN's idea is a good solution.

 

[jacob-Lundgren]

had the event also and b and c are the same amount of money.

 

[C.N.]

I've had 3 of these and I'm quite sure I noticed a difference in at least one of those (the one I checked)..

You played v1.0 then?

 

[Real]

Same bug in my game, I change C to last_year, but seems to me quite powerful.

 

[Cat Lord]

Thanks for reporting it.

Cat

 

[Nikolai II]

Same bug in my game, I change C to last_year, but seems to me quite powerful.

Reduce prestige hit of option b to -5 (i.e. loose 15 prestige as compared to option a) and you will loose plenty more prestige by option c.

 

[Cat Lord]

As you can seen, you get the same gold amount for both the b and the c choice. Maybe option c should have last_year instead?

Maybe last_year is too much as it is roughly 12 times the previous amount, for only 5 times the prestige cost.

We can use last_month multiple times, though...

I prefer the prestige cost being higher than the gold multiplier, btw.

Something like:

	action_b = {#Crave small contribution
		effect = { type = gold value = last_month }
		effect = { type = prestige value = -10 }
	}
	action_c = {#Crave large contribution
		effect = { type = gold value = last_month }
		effect = { type = gold value = last_month }
		effect = { type = gold value = last_month }
		effect = { type = prestige value = -50 }
	}

Cat

 

[Nikolai II]

Maybe last_year is too much as it is roughly 12 times the previous amount, for only 5 times the prestige cost.

Then skip prestige cost completely for option b. After all, if you call the estates it would only be expected that you will ask for some money...

Then you could add a 10 point piety hit and/or a small chance for trait 'greedy' to option c and you should be all set

 

[unmerged(6777)]

Dumb question but...

Has anyone tried using arithmatic operators in an event? I haven't so I don't know if it would work, but I'm thinking that instead of

	action_c = {#Crave large contribution
		effect = { type = gold value = last_month }
		effect = { type = gold value = last_month }
		effect = { type = gold value = last_month }
		effect = { type = prestige value = -50 }
	}

you might be able to use

	action_c = {#Crave large contribution
		effect = { type = gold value = last_month*3 }
	}

I don't know if that would work but it would be nice if you could use at least basic operators (+-*/)

 

[unmerged(27947)]

Has anyone tried using arithmatic operators in an event?

I just tried it, and unfortunately neither multiplication nor addition worked, so probably none of the others do either. Multiplication just resulted in a result of 0, and addition had no effect at all.

 

[unmerged(23737)]

Dumb question but...

Has anyone tried using arithmatic operators in an event? I haven't so I don't know if it would work, but I'm thinking that instead of

	action_c = {#Crave large contribution
		effect = { type = gold value = last_month }
		effect = { type = gold value = last_month }
		effect = { type = gold value = last_month }
		effect = { type = prestige value = -50 }
	}

you might be able to use

	action_c = {#Crave large contribution
		effect = { type = gold value = last_month*3 }
	}

I don't know if that would work but it would be nice if you could use at least basic operators (+-*/)

I've tried it already and it didn't laead to any error messages , but the operators(* or +) won't work.
It leads to 0 Gold!

EDIT: Again too late!

 

[kurtbrian]

Fixed In 1.02