• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

Duuk

Reformed Badboy
23 Badges
Oct 16, 2001
6.137
1.403
  • Majesty 2
  • Europa Universalis III: Collection
  • Crusader Kings II: Holy Knight (pre-order)
  • Cities: Skylines
  • 500k Club
  • Victoria 2: Heart of Darkness
  • Victoria 2: A House Divided
  • Victoria 2
  • Rome Gold
  • Victoria: Revolutions
  • Europa Universalis III Complete
  • Majesty 2 Collection
  • Hearts of Iron Anthology
  • Europa Universalis III Complete
  • Heir to the Throne
  • Europa Universalis III Complete
  • Europa Universalis III
  • Deus Vult
  • Crusader Kings II: Sword of Islam
  • Crusader Kings II: Sons of Abraham
  • Crusader Kings II: The Republic
  • Crusader Kings II: Legacy of Rome
  • Crusader Kings II
Can the Rich get Richer and the Poor get Poorer?

The events that make a province richer/poorer should have a check to be sure that the province isn't at max/min wealth.

IE: I'm sick of seeing that Wolgast is set to RICH when it's been RICH for 20 years.

:D
 
Upvote 0
I don't agree. I like it being random. I hate mechanism that uniformised the game. I'd rather resort on BOOLEAN randomness.

What do other think ?

Cat

PS: I am not sure there IS a min/max, in fact (apart from 0 for min)
 
The randomness is fine. I think his complaint is that the province is already at Rich, and you get an event that sets it to.....Rich. The event fired when it was not needed, and you get more message spam for an event type that *always* gives popups.

My opinion is that the province should be ineligible for a +1 prosperity event if already at max. I have never seen a province that was struggling get an event fire that sets it to struggling, but looking at the event files it is possible.
 
I agree with you...it is an annoyance. I will recommend changes be looked at for 1.03.

In the interim, you could add in the folowing into the "bad" events:
Code:
	trigger = {
		condition = {
			type = not
			value = { type = has_province_effect value = { struggling = yes } }
		}
	}
and to be "fair" you sjould also add this into the good events:
Code:
	trigger = {
		condition = {
			type = not
			value = { type = has_province_effect value = { rich = yes } }
		}
	}
 
Thank you for the info on how to fix it. Looked for something like this in "event effects.txt" but was blind. Of course, now that you have posted it I find it! :D

I will make the changes for myself locally, and hopefully everyone else gets them for 1.03.
 
Fixed in 1.03