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

PAW

Captain
17 Badges
Feb 9, 2011
403
21
  • Crusader Kings II
  • Victoria 2: Heart of Darkness
  • Victoria 2: A House Divided
  • Iron Cross
  • Heir to the Throne
  • Hearts of Iron III
  • Divine Wind
  • Europa Universalis III Complete
  • Europa Universalis III: Chronicles
  • East India Company
  • Darkest Hour
  • Hearts of Iron Anthology
  • Europa Universalis III Complete
  • Europa Universalis III Complete
  • Victoria 2
  • 500k Club
  • Hearts of Iron IV Sign-up
Hello,

Trying to understand how cost works for ships & land units under development.

I am setting up a 1900 start for Grand Campaign & want to know how cost = 0.1
works?

I noticed after 1 day on land units the IC flips from 0.1 to 5.7 - so not sure why?

Will test Naval Units next.

PAW
 
@PAW From event commands:

Code:
- cost = x.xx             # Sets starting cost.
Note that this cost will be changed automatically for players to match correct cost and for the AI if it is higher then the correct cost!
If set to negative (-0.2), then the cost will be fixed for players too (set to 0.2) and for AI countries this unit will be inserted on top of the build queue instead of being appended at the bottom.
 
Divisions that are set at cost = 0.1 normally change to the normal cost of that divisions after the turn of the day in game time. The developer uses cost = 0.1 when they want the division to cost the normal amount of IC but don't necessarily know what this is as it can vary depending on technology and policies.
 
I have not been able to get the negative to work.

cost = -0.2 crashes
cost = (-0.2) crashes
cost = 0.2- acts like positive

Can anyone tell me the syntax for doing a negative.

Thx,
PAW
 
I have not been able to get the negative to work.

cost = -0.2 crashes
cost = (-0.2) crashes
cost = 0.2- acts like positive

Can anyone tell me the syntax for doing a negative.

Thx,
PAW
It appears that part of the documentation is outdated. Try using unitcost = no. For example:
Code:
    division_development = {
       [...]
        cost  = 1.1
        unitcost = no
       [...]
    }