• 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.

pashkevich

Private
27 Badges
Sep 6, 2019
12
3
  • Arsenal of Democracy
  • Hearts of Iron IV: La Resistance
  • Europa Universalis III
  • Europa Universalis III: Chronicles
  • Divine Wind
  • Stellaris
  • For the Motherland
  • Semper Fi
  • Hearts of Iron III: Their Finest Hour
  • Hearts of Iron III Collection
  • Heir to the Throne
  • Hearts of Iron IV: No Step Back
  • Hearts of Iron IV: By Blood Alone
  • Battle for Bosporus
  • Hearts of Iron IV: Expansion Pass
  • Hearts of Iron IV: Expansion Pass
  • Hearts of Iron IV: Death or Dishonor
  • Hearts of Iron IV: Together for Victory
  • Hearts of Iron IV: Cadet
  • Crusader Kings II
  • Victoria 2: Heart of Darkness
  • Victoria 2: A House Divided
  • Victoria 2
  • Victoria: Revolutions
  • Hearts of Iron III
  • Europa Universalis IV
  • Darkest Hour
While I think its not,cuz engine is can't read it, and it not read any arguments like OR or anything else. Anything i do with it (_RANDOMLEADER_BASEFIRE_ in defines) doesn't matter for game and it just instead pull number from engine's core, or crash if I put wrong paranthesis.
 
No. The mechanics would not work with randomized leader stats.

Unlike later EU games, FTG does not allow leaderless armies - which means any time you recruit or split an army, a new random leader is generated. If these random leaders had randomized stats, you would simply split and re-combine until you got one with max stats. And it would be a very boring experience. Best if we skip the drudgery and always generate one with max stats.
 
  • 1Like
  • 1
Reactions:
I should mention that you CAN create randomized leaders through events or decisions. Example:
Code:
command = { type = general value = 4 } # creates a general with stats up to 4/4/4/2
When creating leaders this way, the _RANDOMLEADER_BASE(stat)_ defines are used as the minimums and the value in the command is used as the maximum. Siege values for generals and conquistadors are randomized up to half of the value in the command.
 
  • 1
Reactions:
I should mention that you CAN create randomized leaders through events or decisions. Example:
Code:
command = { type = general value = 4 } # creates a general with stats up to 4/4/4/2
When creating leaders this way, the _RANDOMLEADER_BASE(stat)_ defines are used as the minimums and the value in the command is used as the maximum. Siege values for generals and conquistadors are randomized up to half of the value in the command.
Thanks for an advice, I tried to tweak defines.txt, but that maybe even better in terms of balance.
 
I should mention that you CAN create randomized leaders through events or decisions. Example:
Code:
command = { type = general value = 4 } # creates a general with stats up to 4/4/4/2
When creating leaders this way, the _RANDOMLEADER_BASE(stat)_ defines are used as the minimums and the value in the command is used as the maximum. Siege values for generals and conquistadors are randomized up to half of the value in the command.
when I use it as decision, its don't spawn any general, though sometime its tell "spawn general 4 at terra incognito" and anyway doesn't spawn general.