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

HOI4 Dev Diary - Modding and Traits

Hi everyone! Todays dev diary will be a 3 meal course. First we are going to be talking about the new admiral traits in Man the Guns, then we will be showing off some new modding toys, and finally there will be an extra dessert in the form of more modding stuff posted here in the modding forum. Hope it’s to your tastes :)

Admiral Traits
With Man the Guns following Waking the Tiger and focusing on the naval aspects of the game we knew we wanted to give Admirals more progression and traits as well as new skills. Going over all the traits is going to be spoiling a bunch of upcoming stuff as well, so you will need to be patient with the details on some of that ;)

We have expanded the single skill level of Admirals in a similar way to how we did Generals in WTT, so there are now 4 traits to better reflect their skills and personality: Attack, Defense, Manoeuvring and Coordination. Attack and Defense are pretty straight forward. Maneuvering is the more tactical skill that will matter for fleet positioning and movement while Coordination is the more organizational skill and affects missions and other things outside combat more. We’ll be covering these in more detail once we start breaking down fleets, task forces and combat.

Admirals will now get access to more earnable traits as well as personality traits. Some personality traits carry over from Generals, like Career Officer as well as new ones like Battleship Adherent. There are also assignable traits you can unlock and tailor your admirals. Finally there are terrain traits which are earnable and help in different naval terrain (see future diary for details). As admirals level up they gain 3 points across their skills for each level, more likely in their strong points. Every second level they also unlock the slots needed for assigned traits similar to how it works for generals. The assignable traits and admiral screen will be in Man the Guns while the base stuff like personality traits and earnable traits will be in the free patch. So just like with Waking the Tiger’s general traits.
commanders.jpg


Here is the whole trait tree:
traits.jpg


As you can see most traits will have dependencies on having earned traits first.

There are stuff like Ironside if you want to focus on powerful capital ships, Air Controller for carrier abilities as well as things like Blockade Runner, Concealment Expert and Silent Hunter for raiders. There are also paths for improving the use of lighter ships under Flyswatter and Fleet Protector. This matters because light ships are going to get a whole lot more necessary for your fleets and naval operations.


Modding!
Hello everyone! @shultays here. I am a programmer in HoI4 team and I have exciting updates for all our modders and for the players that enjoy their mods! In this dev diary I will introduce a couple new scripting features that will be especially appealing for our modders. It is a bit early for such tech dev diary but we wanted some feedback on those features, and also have enough time to iterate on such feedback.

I will give short descriptions and small examples here, more in-depth stuff can be found in my other post that I made in modding forums.

Arrays

The people with programming experience are already familiar with the concept of arrays. For those who are not, arrays are basically containers of data. In HoI4, they are containers of variables (and things that can be stored as variables, such as states and countries).

Array support is an extension on the existing variable system. You can store arrays anywhere you can store variables (countries, states, unit leaders or globally). You can access individual array elements using existing effects & triggers that changes or compares variables (the syntax for accessing an element is array_name^index) or you can use them in the effects/triggers that accepts variables. And there are many additional effects and triggers to interact with arrays, like effects that can add/remove elements or triggers that can check for every or any elements.

Let's give an example:

Code:
#create an example array with 3 countries, named "array_example"
add_to_array = { array_example = GER }
add_to_array = { array_example = ITA }
add_to_array = { array_example = TUR }

# calculate total pp of these 3 countries
set_temp_variable = { sum_pp = 0 }
for_each_scope_loop = {
    array = array_example
    add_to_temp_variable = { sum_pp = political_power }
}

if = {
    # do they have more than 100 pp?
    limit = { check_variable = { sum_pp > 100 } }
 
    # remove 33 pp
    for_each_scope_loop = {
        array = array_example
 
        add_political_power = -33
    }
 
    #pp spent, now do business
}

Here I assumed Germany, Italy and Turkey made some kind of pact and I want to run an effect if they have more than 100 pp in total. This effects builds an array of 3 countries using add_to_array effect, calculates the sum of their pp by iterating on this array using for_each_scope_loop effect and removes 33pp from each if the sum is > 0 again using for_each_scope_loop.

This is just one example to usage of arrays. There are many more ways to interact with arrays, which can be found in my other post.

In addition to arrays that you can create or change, the game will also support "game variable arrays". Similar to "game variables", in various scopes you will be able to access such constant arrays which are built using in game data. For example accessing "enemies" array in country scope will let you access enemies of a country. If you loop through enemies, you will loop every for every enemy of that country. Current list of game variables and arrays can be found in my other post, please check it if you are interested and feel free to post your suggestions.

Meta-Effects and Meta-Triggers

This is something we borrowed from EU4, but the implementation and the usage is different. Meta-effects and meta-triggers will let modders to use non-dynamic effects/triggers (the ones that do not accept modifiers and can only use static tokens or constant values) as if they were accepting variables. It is hard to explain and so let's give an example! Consider following code

Code:
add_equipment_to_stockpile = {
    type = infantry_equipment_2
    amount = eq_amount
}

In this effect, amount is dynamic and can be set using a variable (here it is being set to eq_amount variable). However this effect does not let scripters to use a variable as equipment type. You can not store infantry_equipment_2 in a variable and use it here.

But with meta-effects anything is possible! Meta-effects will let scripters to use variables & scripted localization within their effect to build effects as if they were texts and run them. Now let's make previous effect accept equipment type and equipment level as variables stored in eq_type and eq_level.

Code:
set_temp_variable = { eq_type = 1 }
set_temp_variable = { eq_amount = 10 }
set_temp_variable = { eq_level = 2 }

meta_effect = {
    text = {
        add_equipment_to_stockpile = {
            type = [EQ_TYPE]_[EQ_LEVEL]
            amount = eq_amount
        }
    }
    EQ_LEVEL = "[?eq_level|.0]"
    EQ_TYPE = "[This.GetEquipmentName]"
}

# scripted localization
defined_text = {
    name = GetEquipmentName
    text = {
        trigger = {
            check_variable = { eq_type = 0 }
        }
        localization_key = "infantry_equipment"
    }
    text = {
        trigger = {
            check_variable = { eq_type = 1 }
        }
        localization_key = "artillery_equipment"
    }
    # give all equipment an index here
}

Here we created a meta_effect that takes two arguments. These arguments will be used replacing the parameters ([EQ_TYPE] and [EQ_LEVEL]) inside the meta effect. EQ_LEVEL will be replaced by [?eq_level|.0] which is the integer value of eq_level (in this case 2.000 becomes 2). EQ_TYPE is a bit more complicated, it is being replaced by a scripted localization. This scripted localization will check eq_type variable and depending on its value it will return the key token for the equipment. If it is 0, it will return infantry_equipment. If two, it will return artillery_equipment.

So the final result is [EQ_TYPE] is being replaced by "artillery_equipment" and [EQ_LEVEL] is being replaced by "2" and in the end our effect will be built as:

Code:
add_equipment_to_stockpile = {
    type = artillery_equipment_2
    amount = eq_amount
}

which will give you 10 artillery_equipment_2! Now you might think that this is extremely convoluted way of giving 10 artillery_equipment_2. But it will be possible to use and replace meta_effects in the scripted_effects or scripted_triggers, so this convoluted parts will be only written once.

Dynamic Modifiers

Currently our modifiers can only contain static values and you can't use variables in them. With dynamic modifiers, it will be possible add such modifiers to country and states. To keep things simple, we limited adding and removing dynamic modifiers only through effects, although some QoL improvements may be added in future.

Their declaration is similar to static modifiers, except that they will accept variables as modifier values.

Code:
dynamic_modifier_example = {
    political_power_factor = pp_factor_variable
}

And after declaring a dynamic modifier like that, you can run following effect to add this modifier to current scope.

Code:
set_variable = { pp_factor_variable = 0.15 }
add_dynamic_modifier = { modifier = dynamic_modifier_example }

This example will add "dynamic_modifier_example" dynamic modifier to the country of the scope. This modifier will give country pp gain factor equal to "pp_factor_variable" stored that in country. In this example we stored, 0.15 so the country will get 15% more pp gain. When you change the value of pp_factor_variable later through another effect, the bonus the country gets will also be updated.

Additionally you can define a scope while adding dynamic modifiers. In that case the modifier will fetch the variables from the scope that you specified. This will also let scripters to add multiple instances of same dynamic modifier that is targeting different countries (or states) so you can use them as if they were relationship modifier.

While adding modifiers, you can specify a duration as well, which makes them automatically removed after certain number of days. And it is possible to define a trigger, which will also remove the modifier when the trigger is false.

It will be possible to give dynamic modifiers icons. In that case they will show up in GUI. For example dynamic modifiers that are added country will show up if they were "national spirits" if an icon is defined.

dynamic mods.png


In this example Turkey has two dynamic modifiers in it. And we defined an icon here so it shows up in national spirits list. Both of these dynamic modifiers are same but one is targeted at Italy and the other one is target at France and value of "Fuel Capacity" is being read from those scopes (and root is Turkey, you can use targeted variables if you want). Also the effect that added those modifiers defined a duration, and these modifiers will be removed in two days because of that.

More Scripted-GUI features

Modders are being extremely creative with this feature and I am delighted to see all those new cool mods that is being developed or in the workshop. Other than fixing some unfortunate bugs and insights in the live version, we are also adding "dynamic lists" support for scripted GUIs.

Dynamic lists will let modders to create their own lists and fill those lists using an array they specify. In an older dev diary, I showed this sneak peek:

output.gif


This one is actually implemented using arrays. Each cell here is dynamically created using an array of 64 elements and value of each element represents the cell state. Each cell element is being built using the scope and the value of the the array element.

Another, more down to earth, example:

output.gif


Bottom list is populated using allies of the country (using “allies” game array in country scope). For Germany, this array has two elements, Italy and Turkey and thus it creates two entries in the bottom list. While building the elements of the bottom list, it changes scope to each entry in the element (if the element is not scopable, there are ways to access the value & index of the element, which are also being shown in the example)

Top list is built using an array that is stored in country scope and initially it is empty. Pressing “Add Item” button at top calls an effect that adds random country to that array, which also updates the list itself.

The medium flags that are being shown as a grid is also another dynamic list. This example is given to show that the lists inside lists also possible.

And that is all from me for now. If you are interested more on those topics, check the in-depth topic on modder's forum and please give feedback.
 
Last edited:
  • 1Like
Reactions:
But when I hear green water I think of a lake covered with algae.
But that's just me. If it's the right term, please use it.
Shallow waters can appear greenish on sattelite pictures.
GulfMex_WaterTypes.png


Edit: I also found a definition by the US Navy from 2010. But these terms can have changed during the Cold War.
A number of common, non-doctrinal terms also describe aspects of the maritime domain.
Blue water refers to the open ocean; green water refers to coastal waters, ports and harbors; and brown water refers to navigable rivers and their estuaries.
https://www.marines.mil/Portals/59/Publications/Naval Operations Concept 2010.pdf
 
Last edited:
Will the land officer (generals and field marshals) version of Career Officer be changed to conferring a 10% experience bonus instead of the 10% cheaper promotion too?
 
Lots of potential naval pics for this DD - I'm going to go with this one, what traits would one give this character? ;).

Marc_Mitscher_g236831.jpg

Marc Mitscher on USS Lexington :p
 
Shallow waters can appear greenish on sattelite pictures.
GulfMex_WaterTypes.png


Edit: I also found a definition by the US Navy from 2010. But these terms can have changed during the Cold War.
https://www.marines.mil/Portals/59/Publications/Naval Operations Concept 2010.pdf
Thanks.
I did some further "research" (aka google and wikipedia) and it seems that the term "Green water navy" is fairly new (~2005) and that in period speech "Brown water navy" would be correct.
I notice that you've added a color code to the Navy's mission area. You've added green to the traditional blue and brown.
From an interview with Adm. Michael G. Mullen: https://www.navy.mil/navydata/cno/mullen/speeches/mullen051013.txt

This source is referenced here (sorry for German link, I'll translate the important part): https://de.wikipedia.org/wiki/Hochseemarine
Traditionell unterschied die angelsächsische Militärwissenschaft zwischen einer blue-water navy und einer brown-water navy, die sich auf Einsätze in der Küstenregion beschränkt. Die United States Navy entwickelte die zusätzliche Kategorie der green-water navy.[2] Durch diese Neueinteilung ersetzte die green-water navy in der Doktrinendiskussion die brown-water navy, während die US Navy die Begrifflichkeit brown-water navy auf eine Einsatzfähigkeit in Binnengewässern wie Flüssen und Seen reduzierte.
Traditionally anglo-saxon military science differentiated between blue-water navy and brown-water navy which was limited to operations in coastal waters. The US navy developed an additional category of green-water navy. With this reclassification the green-water navy replaced the brown-water navy in discussions of military doctrines whereas the US navy reduced the term of brown-water navy to the operational areas of inland waters like rivers and lakes.

(The English version of the article Hochseemarine would be https://en.wikipedia.org/wiki/Blue-water_navy where the same information can be found:
Traditionally a distinction used to be made between a coastal brown-water navy operating in the littoral zone to 200 nautical miles (or 370 kilometres) and an oceangoing blue-water navy. However, the United States Navy created a new term, green-water navy, to replace the term 'brown-water navy' in US Navy parlance.[13][14] Today, a brown-water navy has become to be known as a predominately riverine force.
)

/edit: So with these information I conclude that "green water navy" is not only a new term but applies only to US doctrines. Of course this has a great influence on all other navies since the US navy is today the biggest navy we have and thus its definitions are more or less valid for all (NATO) navies. But we are talking WWII here, and there was no "green water" back then.
 
Last edited:
Thanks.
I did some further "research" (aka google and wikipedia) and it seems that the term "Green water navy" is fairly new (~2005) and that in period speech "Brown water navy" would be correct.

From an interview with Adm. Michael G. Mullen: https://www.navy.mil/navydata/cno/mullen/speeches/mullen051013.txt

This source is referenced here (sorry for German link, I'll translate the important part): https://de.wikipedia.org/wiki/Hochseemarine

Traditionally anglo-saxon military science differentiated between blue-water navy and brown-water navy which was limited to operations in coastal waters. The US navy developed an additional category of green-water navy. With this reclassification the green-water navy replaced the brown-water navy in discussions of military doctrines whereas the US navy reduced the term of brown-water navy to the operational areas of inland waters like rivers and lakes.

(The English version of the article Hochseemarine would be https://en.wikipedia.org/wiki/Blue-water_navy where the same information can be found: )

/edit: So with these information I conclude that "green water navy" is not only a new term but applies only to US doctrines. Of course this has a great influence on all other navies since the US navy is today the biggest navy we have and thus its definitions are more or less valid for all (NATO) navies. But we are talking WWII here, and there was no "green water" back then.

Yeah, reading historically the division of blue and brown for ocean or coastal navies is well established since the Victorian times. I am pretty sure I never have come across any mention of "green" navies when reading WW2 literature.
 
Last edited:
BTW, what exactly does "Lancer" mean?
It's mutually exclusive with the other submarine trait "silent hunter".
Thus it is safe to assume that lancer is the combat version, i.e. if you want to use submarines to fight against a surface fleet.

The name is fitting as it suggests the charging role of cavalry. The sub won't try to go undetected, but instead charge into "melee" distance.

Japan is the perfect nation for that trait due to her double range torpedoes.

I will obviously pick that trait as Germany, too. Megalomanic plans for a thousand U-Boot fleet with pimped torpedoes.
Lancer Doenitz will lead a doom stack into battle that shall sink the entire RN!
 
The Japanese torpedo was called a "Lance" too, so I'm pretty sure it's a bonus for the torpedoes under this admiral (probably both for Destroyers and Submarines).

Also:
Will the land officer (generals and field marshals) version of Career Officer be changed to conferring a 10% experience bonus instead of the 10% cheaper promotion too?
Anyone?
 
Referencing everyone correctly pointing out the more recent applications of Brown/Green/Blue:

While "Green" wasn't around back then, if they have three realms of areas then I would likely assume that despite the anarchronism of the use of those three colors, it would make more sense than two terms that might be confused for one another.
 
Referencing everyone correctly pointing out the more recent applications of Brown/Green/Blue:

While "Green" wasn't around back then, if they have three realms of areas then I would likely assume that despite the anarchronism of the use of those three colors, it would make more sense than two terms that might be confused for one another.

Assuming the traits will have similar tooltips and info as General traits have, then I don't see how there can be any confusion about their function. I never seen anyone confused about what for example the engineer general trait does ( even if you can imagine it could do all sorts of things ) because they have quite clear tooltip.
 
Last edited:
Can't wait for ship customizations :D
 
So the idea is that brown water is shallow waters and Inshore is archipelagos and such. Green water might fit our use better maybe. will think about it.
If it's yellow keep it mellow, if it's brown flush it down - Do you really want to be known as a Brown Water Admiral?
 
If it's yellow keep it mellow, if it's brown flush it down - Do you really want to be known as a Brown Water Admiral?

They say this in the VI, not regarding any admirals tho.