1. Hearts of Iron IV
  2. News

Hearts of Iron IV News

Barbarossa 1.11.13 - Nakama Crossplay - Checksum d173

Hello everyone!

We just released patch 1.11.13 for "Barbarossa" on Steam and Microsoft Store. The new checksum is d173.
This update introduces the possibility to play multiplayer games across stores (such as Steam and Microsoft Store) using the Nakama network solution already in use in other PDS titles. See the FAQ below for more details.

Saves made with 1.11.12 are expected to be fully compatible with 1.11.13 and you can continue your previous game.

If you discover any bugs in patch 1.11.13, first check the known issues list, and if necessary please report them in the bug report forum as usual.

Nakama Crossplay FAQ

What is Nakama Crossplay?

Nakama is a network solution that is independent of the store you bought the game on (be it Steam or Microsoft Store) and allows you to play with your friends regardless of where they have the game.

Does it replace the current network layer?

Nakama does replace the current solution (PDX MP) on Microsoft Store, but on Steam it is an optional alternative you have to select when launching the game. By default the game will behave exactly like it did in the previous release on Steam.

How does Nakama compare to Steam MP?

First and foremost, Nakama allows you to play across game stores, something our current implementation of Steam MP is unable to do. Secondly, it does not rely on direct connection, meaning it makes it impossible for clients to know the real IP address of the host (and vice versa). This comes at the cost of some extra latency, so depending on where the players are located in given MP session you may experience higher ping than with Steam MP.

How do I enable Nakama MP?

Nakama is always enabled on Microsoft Store. On Steam, you will get prompted to select if you want to start with Steam MP or Nakama MP when launching the game. Starting with the first two options will start the game with Steam MP as usual.


Once in the game, you can tell which version was used by looking at the bottom of the main menu. The letter (S) or (N) after the checksum tells you whether you are using (S)team or (N)akama.


Why does the game ask for a Paradox Account to play with Nakama?

The matchmaking service needs to be able to identify players across game stores, so we cannot effectively use your Steam or Microsoft Store ID. Instead, we rely on your Paradox Account user to be able to host, view and join other players’ games.


Patch 1.11.13 (d173) - FULL PATCH NOTES

################################################################
######## Patch 1.11.13 "Barbarossa" #########
################################################################

##################################
# Free Features and Important
##################################

- Nakama MP is now available


Developer Diary | Peace Conference Roundup

Hello all!
I join you to once again talk about peace conferences. This time we have more info on our changes and features that I was not able to go into last time. Most of these are coming as part of By Blood Alone.

Previously I talked about mostly the structure of the new Peace Conference system. If you have not read that Dev Diary, I recommend checking that out first. The short version is that we are reworking the old peace system into a new one that features simultaneous and blind turns, all conferences actions being contestable, and limited points to use in the conference.

Before we cover new stuff I also want to address some changes to the jargon we introduced last time. We considered changing “demands” to “bids” to fit with the new system. The previous dev diary talked at length about bids. We are instead now referring to all of these as “demands.”

Now for some new stuff! Firstly, I would like to show off our nearly complete UI with a comparison to the old UI.

Nearly Finished PC UI

Old PC UI

In the new system we have expanded the “Demands” portion to the entire left of the UI while moving all relevant information about victors or beneficiary nations to the right. Part of this was to make the menu more presentable, but another part of this was to handle what is now a more complex system of demands.

As part of By Blood Alone, we are adding five new types of demands to the peace conference. Four of these are a new type of “Additional Demand” which I will go into shortly. The other new demand is “Take Navy.” This will allow participants in the conference to use their participation points to demand enemy capitol ships as they would a single state. This means that players requesting the same ship will result in a contested claim. When the conference finishes, screen ships will be divided up amongst those who claimed capital ships based upon the ratio of capital ship industrial cost claimed. We attempted to find solutions to allow more precise claiming of non-capital ships, but were unable to arrive at a satisfactory interaction flow or a good way to fit it into the larger peace conference system.

Naval Demands being issued for the mighty Scharnhorst

As mentioned previously, we now have “Additional Demands” These options all require an underlying demand of puppet or change government to have been applied to a state first. Secondary demands can be applied over the top of a normal demand during the same turn or any subsequent turn.

The first secondary demand we have is “Demilitirized Zone.” this prevents the target nation from placing troops in the selected state. This is a pretty classic part of many historical peace conferences and serves as a way of keeping troops off of borders.

DMZ option

The next two secondary demands are both economic. These are “Resource Rights” and “War Reparations.” To make resolving contested demands fit into our system, both of these demands target single states. Resource Rights gives access to the resources in a state. War Reparations gives control of local civilian factories in a state. Both of these last for a period of time the length of which is still TBD.

Resource Rights and War Reprations options

Our final new demand, coming with BBA, is “Dismantle Military Industry.” This will remove military factories from the targeted state. This can be used to tear down a heavily militarized state’s mic and help slow down re-militarization postwar.

Dismantle Miltiary Option

That’s all we have for today and I thank you for stopping by. Next week, we will be talking about modding. Stay tuned! o7


Developer Diary | Division Commanders & Unit Medals


Greetings all!

Welcome back to today’s feature dev diary on a series of interconnected subsystems being added to the game in By Blood Alone.

One of the major points in my first roadmap dev diary was that I felt quite strongly about the inclusion of further roleplay and immersive elements in Hearts of Iron. What I’ll be showing off today is intended to fulfill a small part of this bullet point.

Those of you with keen memories will recall an early teaser I posted here. Some of you guessed correctly, and in BBA, we’ve introduced a dynamic system for naming battleplans. For many major nations, battleplan names can be provided through a list of locations, resulting in a historical series of operation tags which will be applied when plans are created:​


Of course, the war does not always proceed historically, and battleplan names can also be generated from several component lists for instances where a historical variant cannot be found. These name lists are fully moddable, and can be unique to countries. In some cases (ie; Soviet Union) a different naming convention can be utilized to represent the somewhat uninventive approach to naming operations that was used in reality:


Naturally, in the spirit of roleplaying, these operation names can be modified in-game, and you can replace the text with whatever operation name you desire. This will apply to any sub-orders derived from the initial drawn line:


If unset, naval landing and paradrop orders will have a unique pattern to remain unique.

This system however, goes further than a simple naming convention, and ties into another addition being made to BBA.


[h3]Division Commanders[/h3]

In BBA, we’re replacing the standard method of recruiting new generals out of thin air. Instead, every division will be created with a commanding officer upon game start, or when they are trained:


These are predominantly generated from country-specific namelists, however in some cases we have set these individually for starting divisions. When a new unit is created, they will be provided a randomly generated character name and portrait. To accommodate the increased use of generic portraits for these, we’ll be adding a large quantity of additional generic portraits for owners of BBA. The work involved in creating these is not insignificant, so for now we’ve limited ourselves in adding portraits to major nations only.

You’ll be able to get an overview of all division commanders in your army within the officer corps screen:


In an effort to avoid unnecessary micromanagement, we’ve made a few important decisions. Division commanders themselves will not directly confer bonuses upon the divisions they command, however the divisions they command will now earn and log a record of important actions they may perform during the natural course of a campaign:


Important actions such as taking a capital, securing a high-value victory point, and more, constitute actions for which a unit can be awarded a medal. It is expected that over the course of a campaign, many units will qualify for receiving medals, often several - the system is not driven by scarcity, as we do not intend for players to micromanage individual actions, rather to manage the macro-level step of choosing when and what to award their units.


As mentioned above, division commanders will not explicitly confer bonuses, however the medals awarded for action will. Medals are intended to act as a pp sink for the mid-late game, as we find a lot of players tend to end up with a significant amount of this resource as decisions, advisors and focuses begin to dwindle.

Units can receive multiple medals, however the cost for each will increase as more are granted to any given unit, and the effect of stacking specific medals will decrease per instance of the same effect.

As you will note above, medals can be specific to countries, and we’ve included a series of generic medals based on alignment, as well as unique medal sets for each major country. A medal’s effects will only extend to the unit it belongs to.

A medal’s name and description will in most cases be dynamic depending on what action it was awarded for, and extreme valor while on a specific named operation can also result in receiving a medal for that action.

To further streamline the process of awarding medals, you can perform quick actions to do this through the officers entry in the corps screen:


As mentioned previously, we’re removing the old method of recruiting generals by means of reaching into the void and plucking out a fully qualified officer. This means that your army generals will now be directly linked to your field of divisional officers, and their capability directly linked to their actions in the field.

Divisional officers will store experience based on the experience gain of the unit they are commanding, as well as receiving a lump-sum when a medal is awarded. While active as a divisional officer, this experience will have no meaningful effect, however, when in need of a new army general, you can promote divisional commanders out of their divisional role and directly into their new role as a general.

Any medals awarded to the division will be retained by that division, however, the newly created general will keep a reference to their awarded medals as a means of remembering their accomplishments in the line of duty (albeit with no direct effect on their new army - although we’ve elected to support this behavior for modders should they wish):


When a divisional officer is promoted this way, the experience they have earned during the course of their field command will be applied to their experience level as a general (up to a maximum cap). Promoting someone with field experience can prove a lot more valuable than hiring another pen-pusher, after all. If they have earned at least a certain quantity (as yet undecided) of field experience, they will also begin with a personality trait corresponding to the type of division they were commanding (armor officer, infantry officer, etc).


[h3]Unit Cohesion[/h3]

You will also note that my roadmap included a wish to improve the battle-planner. While this is likely to be a slow, iterative process, BBA heralds the inclusion of a new frontline parameter intended for advanced users.


The Cohesion parameter can be set on any root frontline order, and will affect how the unit controller places divisions across that frontline. The default setting of ‘Flexible Cohesion’ functions as you have grown to expect - all units will be evaluated for placement suitability and potentially relocated to fill perceived gaps in frontline cohesion.


Balanced Cohesion’ will only successfully evaluate units that are within a defined distance from the target (distances are moddable). In practice, this results in less unit shuffling along frontlines, but should still ensure that frontlines respond to changes in size and shape.


The final setting, ‘Rigid Cohesion’ is intended primarily for long defensive lines, and will only successfully evaluate unit positions that are within a very short distance from the target location. In practice this results in relocations only taking place to neighboring provinces, and can result in gaps being created in frontlines if left unattended. It is expected that this setting will be used by players who primarily rely on micromanagement of frontlines.

The AI will make use of flexible and balanced cohesion settings depending on the ratio of divisions:frontline length, but will avoid the use of rigid cohesion.

It is worth noting that units that are not placed directly on the frontline (having been left behind or recently added to an order instance) will not be subject to the same cohesion restrictions, and will make use of strategic relocation to find themselves a new place on the frontline. Additionally, the cohesion setting will be respected regardless of whether an order is being executed or not.


[h3]Modding[/h3]

For those of you interested in modding, the addition of these subsystems also comes with some new tools regarding units. It is now possible to iterate over unit arrays in states and countries by condition, and apply a series of effects, including the awarding of medals, history entries, and other basic parameters such as affecting org, strength, and more. For performance reasons, units do not currently support storing or being stored as variables, though we will monitor the need for, and performance implications of doing this in future (I SEE YOU EaW).

Predefined divisions can be set up with lists of historical commanders that they will draw from when their current commander if replaced, should you wish to opt for extreme historical fidelity.


The visual display ranks of divisional commanders correspond to their gained experience, and are fully customizable, though confer no gameplay effect.

Medals themselves can be added to the medal array based on arbitrary conditions, and support a variety of modifiers, not all of which are represented in our vanilla use-cases.


Name combinations can also be split from various random lists, if you have a particular penchant for randomly generated names.


That’s all for now, tune in next week for a second look at how peace conferences are progressing!


Get your PDXCON 2022 tickets now!

[previewyoutube][/previewyoutube]

PDXCON returns to Stockholm this September! Meet the devs, join a massive board game session, attend Paradox games’ orchestra & play our games!



Developer Diary | Plane Designer



Hello, and welcome back to another Dev Diary for the upcoming By Blood Alone DLC and accompanying Patch 1.12! The team has returned from the summer vacation, and we are now back fixing bugs and tweaking the balancing of the new features and focus trees.

Today, we are taking a look at the Plane Designer. As always, any number value that you are going to see in this DD is subject to change.

The Plane Designer became a subject of discussion, both inside the team and in the community, almost as soon as we announced that No Step Back would feature a Tank Designer. We felt that it would mesh well with the rework of the Italian focus tree, not least because the Italian aviation industry was very well developed and produced some of the best combat airplanes of the war - hampered mostly, as Italy so often was, by lacking production capacity.

We also felt that a Plane Designer would help plug some gaps in the lineup of available aircraft. Over the years, many players have commented on the fact that many nations modified their fighters to also be able to carry bombs, or their tactical bombers to also carry torpedoes. One of the big goals of the Plane Designer was to allow for these types of multi-role aircraft.

At the same time, we didn’t want to make these multi-role planes too powerful. Instead, a plane design optimized for a single mission should still be more effective than a multi-role plane. Where multi-role planes offer flexibility, optimized designs offer top performance, if you can afford them.

The basics of the Plane Designer are probably not a surprise for anyone who is familiar with the Ship or Tank Designers. The base is called an airframe, which roughly corresponds to the hulls and the chassis of the ship and tank designers. The Airframes have a number of module slots, where you can put the modules that give the final design its actual stats. There are three different size classes of airframes: Small, Medium, and Large. Small planes also come in a carrier-capable variant of the airframe.

The types of module slots in the Plane Designer are slightly different from the Tank Designer. There are effectively only three types of slots: Engines, Weapons, and Special modules.

Engine modules are perhaps the most straightforward of them. Unlike tanks, where this slot dictates what type of engine the tank uses and a separate stat determines what its speed is, engine modules in the plane designer determine the number and power of the engines mounted on the aircraft. These engine modules produce a new stat called Thrust, while all other modules have another new stat called Weight. These two stats are effectively the limiting factor of what and how many modules you can put on the plane. A design is only legal if Weight does not exceed Thrust (some people might point out that the only planes with a Thrust/Weight ratio of 1 or better in reality are modern, high-performance fighter jets, but these people will be summarily ignored).

Any excess Thrust is converted into extra speed, which is intended to provide a reason not to fill every module slot.

One thing to note here is that jet engines (and rocket engines, for that matter) are part of these engine slots, which means that they are available for all types of planes. This, by necessity, means that Jet Fighters and other jet-powered airplanes are no longer their own unit type - they are now simply fighters with jet engines. Jet fighters will therefore reinforce regular fighter wings, and also that you can now effectively make jet carrier planes, jet CAS, jet heavy fighters etc.with the plane designer.

Or Rocket Naval Bombers, one supposes, if you really hate your pilots on a personal level.

Weapon modules are also fairly self-explanatory. But beyond providing offensive stats like Air Attack, weapon modules fulfill two other major functions. The first is that the weapons define what type of plane a design ends up being. For this the designer has a Primary Weapon Slot. The module in this slot defines the role of the final design, i.e. Fighter, CAS, Naval Bomber etc.

This is relevant because the weapon modules also unlock what missions a design has available. That means that the strict separation of mission by type of aircraft will be gone. You can now create fighters that can provide ground support, or Strategic Bombers that can do naval strikes, depending on the modules you put on the plane. There are, of course, some restrictions - strat bombers can never mount the modules necessary to unlock air superiority missions, for example.

We still wanted to give you an easy way to classify your designs on a high level and it also makes it a lot easier to tell the AI what a design actually is and how it should be used. Without accounting for doctrines, there are no stat differences between, say, a fighter that has a set of 4 Heavy MGs in the Primary Weapon Slot and bombs in a secondary weapon slot, and a CAS that has the bombs in the primary weapon slot and the MGs in the secondary slot - but one goes into Fighter Airwings and the other goes into CAS Airwings.

CAS planes have a large variety of weapons available to them to attack ground targets.

There is a full list of weapons, the missions they unlock, and what they classify a plane as if mounted in the primary weapon slot, below (stats omitted because balancing is still ongoing):


While some of these weapons are unlocked in the (reworked) Air Tech Tree, some of them are also found outside of it, in a similar manner as the tank weapons are found in various trees. I will note that the total number of techs in the Air tech tree has actually decreased.

A view of the Air Tech tree. It has a total of 28 techs, compared to the old tree’s 38 techs.

One notable aspect is that a lot of these modules provide different stats only for specific missions. For true multi-role planes to make sense, we wanted to make sure that building a design with a mixed set of missions didn’t make the plane useless in some of them. Hanging bombs off a plane should make it less agile and slower, but a fighter that was able to do CAS missions shouldn’t be useless in air superiority missions. Thus, the weight and agility penalties only apply to the fighter if it is actually on a CAS mission, not if it is on an air superiority mission.

Modifiers only apply to certain missions. Here, the bombs the Stuka carries make it less agile, but the dive brakes give it better air defense

Finally, we have the so-called “Special” module slots. These are effectively a catch-all term of various different items, a list of which you can find below:​

Armor Plate: Increased Air Defense, reduced range
Self-Sealing Fuel Tanks: increased Air Defense, costs Rubber
Drop Tanks: increased range (small airframes only)
Extra Fuel Tanks: increased range, reduced air defense
Dive Brakes: increased air defense, increased naval strike hit chance
Radio Navigation I: reduced night penalty, increased strat attack
Radio Navigation II: reduced night penalty, increased strat attack
Air/Ground Radar: reduced night penalty, increased strat attack, increased naval detection
Air/Ground Radar II: reduced night penalty, increased strat attack, increased naval detection
Air/Air Radar: reduced night penalty when on intercept mission
Air/Air Radar II: reduced night penalty when on intercept mission
Floatplane: increased naval spotting (small airframes only)
Flying Boat: increased naval spotting (medium+large airframes)
LMG Defensive Turret: increased Air attack, reduced agility
2x LMG Defensive Turret: increased Air attack, reduced agility
HMG Defense Turret: increased Air attack, reduced agility
2x HMG Defense Turret: increased Air attack, reduced agility
Cannon Defense Turret: increased Air attack, reduced agility
2x Cannon Defense Turret: increased Air attack, reduced agility
Recon Camera: unlocks recon mission (LaR only)
Demining Coil: unlocks demining mission (MtG only)
Bomb sights I: increased strat attack
Bomb Sights II: increased strat attack
Non-Strategic Materials: reduced Aluminum cost, reduced air defense

Special Modules are primarily intended to help optimize planes for various missions or give them different niches.

The eagle-eyed amongst you have already spotted that planes now have a surface and sub detection stat. Up until now, planes that were active in a sea zone always provided a flat bonus to the spotting speed of any navies active in the seazone. This will now change, with planes having dedicated spotting stats that determine how well they do with helping the navies spot. There are modules, like the Air-Ground Radar and the Flying Boat hull, which give bonuses to naval spotting.

Vanilla planes have those stats already baked in, with some being better than others - carrier planes are better than their land-based counterparts, naval bombers are better than fighters etc.

To further support this, we are adding two more things: Maritime Patrol Planes as a dedicated unit type and a special Naval Patrol mission for planes with the right modules.

Maritime Patrol Planes are built on the Large Airframe, giving them exceptional range. They are able to mount the whole array of naval bomber weapons, but naval strike is really not intended to be their primary role. Maritime Patrol Planes are meant to help with spotting raiders in the deep ocean, where smaller planes with shorter ranges struggle to provide much mission efficiency.

You can run naval patrol missions with many different types of planes.

Finally, let’s talk a bit about art! While we already have a large amount of historical art for various plane types, we also wanted to give you more options to visually distinguish your designs, even if it is just to find the plane design more easily in the production menu. For the tank designer, we split up the existing art and recombined it into various combinations to quickly generate a large number of assets. We realized early on that this wouldn’t work for the plane designer. So instead, we decided to fill in some gaps in the existing art as well as add some art for a number of prototypes that flew but were historically passed over for mass-production.

Here is a partial list of new plane icons coming in BBA. Which one’s your favorite?

We also decided that we wanted to add more 3d art. Much like the tank designer, you can select these assets when you design the plane. We are adding about 80 new 3d models for planes to the DLC, but more on that in the future!

Here is just a teaser of some of the new assets coming in the DLC:

That is about it for this week. We hope that you will enjoy playing with the Plane Designer as much as we enjoyed making it. To end this DevDiary on a personal note: The Plane Designer will be my final contribution to Hearts of Iron 4. After close to 6 years on the project, all the way from the early days on Together for Victory, the time has come for me to leave the company and move on to greener pastures. It has certainly been an eventful and productive couple of years, and there are many things that I am very proud of (and a few that I regret - like adding Austria-Hungary as a joke and then finding out that people love monarchism). Working on the Hearts of Iron series has always been a dream for me, since the day I launched Hearts of Iron 1, almost 20 years ago now. Few people can say that they had an impact on a piece of entertainment that has had a similar impact on themselves. But the thing I am most proud of is the team we have built. Hearts of Iron is in very good hands, and there are years of content still to be released. I’m looking forward to it - but, once again, as a player.​

Weird designs that QA came up with:

This single plane outguns an entire tank platoon, unfortunately it can’t ever turn:

And then we restricted the number of bomb bays you can have on a plane:

6 engines, 8 cannons, 4 cannons in turrets, and a production cost 50% higher than a strategic bomber. Needless to say, this combo is no longer possible:

When you look at the Spitfire Mark I’s armament and wonder: but what if…more guns?