1. Hearts of Iron IV
  2. News

Hearts of Iron IV News

Road to PDXCON: Grand Campaign - Hearts of Iron [7th May 12:00 CEST]

[h2]Join the Hearts of Iron team, The Grand Campaign cast and our Discord senate for the third leg of our story![/h2]

The story has unfolded and the Dual Monarchy stands at the precipice of a World War. In this modded, community built scenario a cast of Developers and Paradox Staff must lead our nation to victory in a world wide conflict!

Acting as our ‘Senate’, you can influence how each campaign unfolds. Want to see a more military focused nation, or one that values the power of diplomacy or trade? By debating and voting inside the Senate, you can shape the course of our nation through all four grand strategy games.

You can take your seat in the senate by heading over to the discord here: https://discord.gg/pdxcon

Each leg of the journey will also have a knock on effect on the next, crafting a completely unique gamestate by the time we reach our Stellaris endgame. You have the power to not only shape history, but the universe!

The Event will be broadcast live on the Paradox Interactive Twitch Channel at the times below:

[h2]The Dates:[/h2]
    Crusader Kings III: 21st April 12:00-22:00 CEST
    Europa Universalis IV: 28th April 12:00-22:00 CEST
    Hearts of Iron IV: 7th May 12:00 - 22:00 CEST
    Stellaris: 15th-16th May 12:00 - 20:00 CEST

[h3]We’re looking forward to bringing hours of grand strategy gameplay to you as we forge our own story, together!
[/h3]

Dev Diary: Combat & Stat Changes



Hi everyone and welcome back to another dev diary! Today is about various changes that affect combat and units. With the Barbarossa update we want to shake up the meta a bit and also change a few stats and other aspects to make using the tank designer more interesting and rewarding.

[h2]High Command bonus changes[/h2]
For a long time now unit bonuses from high command have confused people. Most expect that they apply to battalions, when in fact they apply only if their target unit type was “the majority type”, which was basically a weighted type count. They also could overlap, so infantry, mountaineers and artillery would apply to the same units letting you stack stuff in ways that was never intended and quite unintuitive.



This system has now changed, and divisions get bonuses based on their composition, this is a straight up ratio based on the number of non-support battalions of each type, so a 2x artillery 3x infantry division will be 40% artillery 60% infantry.

Battalions are always classified as a single type for this (even though some are scripted with multiple types) based on this priority:
cavalry > armor > artillery > motorized > mechanized > infantry

The exceptions being rocket & special forces, which both act as an addition, so if the 3 infantry divisions in the example above were mountain units, then the division would also be 60% special forces and if the 2 artillery are nebelwerfers it'd also be 40% rocket.

When counting the battalions of armies (ie when we have an actual unit and not only a division template), battalions that lack equipment will count as less, so a Light Tank battalion with only half it's tanks will count as 0.5 battalions (and not count at all if without tanks). The total sum of the compositions will still end up 100% (unless every battalion is without equipment).

To make it easier to see this we now have an indicator in the division windows showing the breakdown.

[h2]Combat Width[/h2]
As a part of our efforts to shake up the 40/20 width meta, we have made changes to the combat width of province terrain. Province widths now range from 75 to 96. Plains have a new base combat width of 90, while Mountains have a new combat width of 75. Most of these widths will not divide into each other easily, hopefully moving the ideal width away from multiples of 10.

Urban provinces are now the “widest” with a width of 96. But this does not mean they will be the easiest provinces to overwhelm. Mountains, marshes, and urban provinces now have reinforcement widths of ⅓ of province width instead of ½. This should hopefully give these provinces a slight defensive buff, while allowing us to open up pushing power in the more open tiles.



In conjunction with these changes, we have also been looking at reducing the overstacking penalty. We hope that this will alleviate some of the need to have divisions that are the perfect width for a given province. But at the same time, smaller countries should now be able to specialize their division width to suit their home terrain more appropriately.

Breakdown (numbers not final etc etc)

Plains
  • Standard 90
  • Reinforce 45

Desert
  • Standard 90
  • Reinforce 45

Forest
  • Standard 84
  • Reinforce 42

Jungle
  • Standard 84
  • Reinforce 42

Hills
  • Standard 80
  • Reinforce 40

Marsh
  • Standard 78
  • Reinforce 26

Urban
  • Standard 96
  • Reinforce.32

Mountain
  • Standard 75
  • Reinforce 25



One of the major things that make larger divisions like 40 width armor hit disproportionally harder than smaller ones is also how targeting and damage works inside combat in relation to the enemies defense. Essentially the larger divisions make more efficient use of concentrated damage as it punches through defense. To solve this we are doing a few things. First of all we are weighting the targeting towards wider divisions being more likely targets and also when picking targets to try and match it to have wider divisions spread damage over smaller rather than always concentrating it. They will probably still hit harder, but combined with width changes and other downsides of larger divisions it should make it less clear cut.
However, this part isn’t quite done yet though so I’ll cover it again in more detail in one of the “bag of tricks” diaries in the future when i see how it pans out, but I figured it needed to be mentioned now ;) That said though, to wet your appetites here is a little tease from a debug mapmode in development...




[h2]Armor and Piercing[/h2]
Currently the effects of having stronger armor than the enemy can pierce, or being able to pierce an enemies armor are binary and give fixed bonuses. This meant that there wasn't really any benefit to have more armor than you needed to stop the enemies piercing, and also that being a single point of piercing under enemy armor was just as bad as having no piercing. So things were quite binary. With the tank designer coming we wanted to make it feel like your investments in upgrades were always worth it, so we are changing armor and piercing to have more gradual effects.

Armor > Piercing
  • Unit takes half damage (as it currently works)

Armor < Piercing and Amor > 0.75 * Piercing
  • Take damage between half damage to normal damage by difference in value

Armor < 0.75 * Piercing
  • The unit takes normal damage


Lets break this down with an example:
  • A panzer division has an armor value of 52
  • Its being attacked by an infantry division with some anti-tank guns. Their piercing is 60
  • If this was the old system this armor would be worthless and not reduce damage at all
  • Now because its close enough (between 60 and 45), so you get roughly half of the normal effect around 25% reduction of damage.


[h2]Reliability[/h2]
For the tank designer it was important that reliability was more impactful if it was to be a good tradeoff with other aspects of design, so we needed to change it up (lest @CraniumMuppets 0% reliability tank monsters would take over the world). Now it will not just affect rate of loss in attrition but various other aspects:
  • Reliability affects losses from attrition like before
  • Reliability now affects org regain when moving, and also makes any weather related org effects more impactful when low
  • Lower reliability scales up all impacts from weather so if facing extreme weather a unit with low reliability equipment will suffer more of those weather effects
  • At the end of combat units with better reliability will be able to get back a certain amount of tanks etc to simulate that simple more reliable constructions would work better for battlefield repair and be less fragile when taking damage. So it's a bit like capturing enemy equipment in combat - but in reverse :cool:




Our goal is that this creates interesting tradeoffs when designing equipment and will make you have to consider if its worth switching a strategy focused on speed and firepower towards reliability when operating in bad weather and tough areas like the Russian winter or in northern africa or jungles.

Oh, and I figured now might be a good time to point out that there will be a future diary on weather changes and other cool related stuff, so these changes aren't completely in isolation. But one step at a time :)

But before we go, a few words about the studio...


Studio Gold

Hello everyone, my name is Thomas, but perhaps better known as @Besuchov here on the forums.

As you saw here we have recently reorganized ourselves a little, moving from a big centralized Stockholm studio to splitting ourselves into Red, Green and Gold. This is mainly an internal org shift to make sure we keep our growing organization firmly focused around making good games. You shouldn't notice too many differences in the short term, we are still PDS making GSG on the Clausewitz engine, but it does mean that we can align each studio to the particular games. Since you will hear the studio names every once in a while, I just wanted to say who I am and what the studio is responsible for.

My role is Studio Manager, which means I'm accountable for the long term success of Studio Gold and working with things like management, staffing, and long term plans. Studio Gold has as its main focus Hearts of Iron (but we may or may not have some secret other stuff as well). Directly making the games though, that's still the job of Podcat and the team, but I intend to do my best to create an environment where we have the best chances to make great games together.

For me this is coming full circle at Paradox. I started as a programmer in 2004 and one of my first tasks was to work on Hearts of Iron 2. Since then I've done various things including being lead programmer for Hearts of Iron 3 (and Victoria 2), Project Lead for EU4 and more recently Studio Manager for PDS. Next to EU, HOI is my favorite game and I'm delighted to be back in a place where I can focus on fewer games and where that game is Hearts of Iron. You will see more of me in the future even though I will mostly take a backseat to the team working on the game.

[h3]That’s all, see you all again next week for more dev diary goodness![/h3]

Read the full article here: https://pdxint.at/3vJu32o

Hearts of Iron devs and former CEO speak out against toxic feedback in EU4 drama

If you've been paying attention to Paradox's grand strategy games this week, you'll have noticed that Europa Universalis IV just received its own expansion and free update. The Leviathan EU4 DLC adds new mechanics that allow you to play 'tall', whereas the free 1.31 'Majapahit' update attempts to give some fresh content for indigenous tribes across the map.


Neither update has worked out quite as well as was intended. In the three days since it launched, several bugs and major issues have been reported - including being able to cancel AI monument building - along with some major balance issues. The expansion is officially Steam's worst-rated launch ever, and a 1.31.1 hotfix was quickly released.


Sadly, players are now directing hatred towards not only Paradox as a company, but also specific members of the development team at Paradox Tinto, the new studio formed in Barcelona that's now in charge of EU4's development. Other teams within Paradox Interactive's umbrella have noticed and voiced their own concerns regarding toxicity and feedback, specifically the Hearts of Iron devs.


Read the rest of the story...


RELATED LINKS:

Next Hearts of Iron 4 DLC announced at PDXCon Remixed

New Hearts of Iron 4 expansion will let you form a Nordic empire in Baltic rework

Hearts of Iron 4's grand campaign is live, using a custom mod developed in six days

Dev Diary: Tank Designer



Hello, and welcome back to another DevDiary about content coming in the 1.11 “Barbarossa” patch and its accompanying DLC. As always, keep in mind that the things shown in this DevDiary are still under development, so the numbers and UI might change before release.

Ever since we revealed the ship designer in Man the Guns, people have been asking about a similar system for tanks. We did, however, want to improve a bit on the ship designer. In particular, we felt that the ship designer was encouraging too many generalist designs. Part of the problem is that ships have a very long lead time before they become available, so it is difficult to iterate on the designs in a timely fashion. When your ship takes two years to build, you can’t really specialize it too much, because you can’t always accurately predict the situation in two years.

Thankfully, tanks require a somewhat smaller investment (although our QA certainly has tried to make designs that rival ships in cost), so you see a new tank design in the frontlines much sooner than a new ship, allowing you to react to new situations much faster.

Another thing is that ships usually had trade-offs between different capabilities, in the sense that the space (or module slot) taken up by a torpedo launcher could also be taken up by an AA gun, making the ship better against one or the other type of enemy. But rarely did you want a ship that had no AA or no way to defend itself against surface targets, so you always wanted some AA and some ship attack.

Tanks, on the other hand, don’t usually have trade-offs in the same way. You don’t usually design a tank, wondering if you should put on another AA gun or a second gun against surface targets (unless, of course, you are German and it's 1944).

But Tanks still have trade-offs in their design, and we wanted to represent those. Traditionally, tank design revolves around three aspects: Mobility, Firepower, and Protection. A well-armored tank is slow, a fast tank can’t carry a big gun, and a big gun requires a large tank, which is difficult to armor. During the war, different nations tried different approaches, and learned different lessons from their observations - it is no surprise that the last German tanks of the war were heavily-armored vehicles carrying massive guns, but the first post-war design was the comparatively lightly armored but well-armed and quite nimble Leopard 1.

So we wanted to make you think about these three aspects, and have it be a trade-off between them. However, in a grand strategy game, other aspects also matter more than in the typical comparison of tank designs - the best tank in the world is useless if it breaks down on the way to the battlefield (Panther fans take note), and it is even more useless if you can’t afford it. So we wanted cost and reliability to also matter when designing a tank or armored vehicle.

In contrast to ships, we wanted to make you think more about specializing your designs to fill a certain niche, and optimize it towards a specific role. While you will probably still want to have a somewhat middle-of-the-road design for your main production medium tank (one might call it “the Sherman”), there is a place for more specialized designs as well.

As part of this approach, we will be making changes to the reliability system and the armor system. The details will be forthcoming in a future dev diary (together with other combat changes), but the broad strokes are that reliability will not just affect the rate of attrition, and that the armor system will become less binary. As part of these changes, we also decided to give mechanized equipment some upgrades, so that it can keep up with tanks.



Under the new system, reliability is meant to represent both the likelihood that a given piece of equipment breaks down as well as the likelihood that it suffers catastrophic damage when hit and the effort necessary to repair it. In effect, reliability also represents the carrying capacity of a given chassis, so you effectively have a reliability budget for every chassis to work with. The more armor you put on it, the bigger the weapon etc., the more reliability drops. Heavier or more advanced tank chassis generally have more reliability (over 100% on the base chassis in some cases).

But enough of the basics, let’s talk about what you really want to know: What’s the Kampfwagenkanone Zweiundvierzig in game terms? Is the weird hybrid-electric drive of the Elefant represented? Do we get to set the exact angle of the front armor or just the thickness?

Much like ships, tanks are based on a hull (called a chassis) and a number of modules that define the actual stats of the final design. These modules act a little different from the way the ship designer works. While the main armament is fairly self-evident, other “modules” represent something like “design features”. These features are meant to be distinct enough that even someone who does not have an in-depth understanding of armor development during the war can at least understand that different armor types are good for different things.




Instead of scripting in a gigantic list of armor types with different thickness, armor is represented by a thickness and a production method: Riveted Armor is the cheapest kind, but also the weakest. Cast Armor is the strongest, but also the most expensive.
Welded Armor is a compromise between the two extremes, making it the most cost-efficient (arguments can be made either way between cast and welded armor since welding does require specialized equipment and training).

Armor thickness is changed through something much like the old, vanilla upgrade system, with up to 20 different levels. You start with being able to put up to 5 levels of armor (roughly equivalent to 50 mm of armor) on a tank, but research allows you to put more on. Higher levels of armor protection require more resources, such as steel and eventually chromium. There is no limit to the amount of armor you can put on a chassis as such - if you want to make a light tank with the armor protection of a Tiger, you can (it’s called a Panzer I Ausf. F). The amount of armor upgrades on the vehicle translates to an actual armor value based on the type of armor you have selected, so 5 levels of riveted armor are still weaker than 5 levels of cast armor - but much cheaper.



Engine types are also meant to be simple to understand. Gasoline Engines are faster than Diesels for the same weight, but Diesels are more reliable. Beyond that, Electric hybrid engines are a very situational pick. We originally intended for them to be a joke pick - costly, unreliable, fuel inefficient - but on some further reading, the rationale behind them was that they offered better mobility in broken terrain. In game, this is represented by a small bonus to breakthrough and defense. Finally, there are gas turbines, which are unlocked from jet engine research. They are the fastest engine option, but take up a lot of fuel. Like armor, engines also have an upgrade system where you can set the level of engine power (up to 20). It should be noted that the speed of most historical designs is going to be lower than the stated max speed of the vehicle they are based on. This is because we represent the operational speed of a vehicle, i.e. how far the vehicle can get in 24 hours - tanks don’t drive around all day at maximum speed, they have to stop for refuelling, resting the crew, basic maintenance etc.

Turrets are split between different kinds and are meant to represent things like crew ergonomics. Early in the war, a lot of countries had tanks with one or two-man turrets, and one advantage the Germans had was having a commander who could direct the rest of the crew without also having to service the main gun. This is represented by bonuses to breakthrough with different turrets. A special type is the fixed superstructure. Main guns are differentiated by size (small, medium, large, super-heavy), which correspond roughly with the weight classes of tanks. Light tanks can only carry small weapons etc. - unless they have a fixed superstructure, which enables them to carry guns one size bigger, allowing you to mount a medium gun on a light tank chassis. Having a fixed superstructure also adds bonuses to defense while giving a penalty to breakthrough, making it a good option for vehicles meant to defend.



Suspensions affect mainly reliability and speed. The most basic kind is the Bogie suspension, which adds some reliability, while Christie suspension adds quite a bit of speed. Torsion Bar suspension adds more reliability than Bogies, but is more expensive. Interleaved Roadwheels - as seen on the later German tanks - add some breakthrough, but have reliability problems (the overlapping wheels add some protection and redundancy against fire coming from the side, but are difficult to repair and maintain). Light Chassis can also select wheeled and half-track suspensions, which make the vehicle itself quite a bit cheaper, but also drop reliability.



The main weapon has probably the biggest impact on the offensive stats of the vehicle. There are a lot of different options to choose from, but we have tried to give every weapon type it’s own niche, with realistic drawbacks and advantages, so for example the High-velocity tank guns (like the KwK 42 or the American 76mm) have worse soft attack but very good piercing and hard attack, while howitzers have very poor hard attack and piercing, but spectacular soft attack. This means that for example the early German tanks do struggle a bit against the French, which have pretty heavy armor (but suffer in other regards, mostly because of their one-man turrets).

As you can see, we made an effort to not have a giant tech tree this time. The tech tree for the new chassis is about the same size as the old armor tech tree, and the other modules are unlocked primarily through the artillery tab.



Finally, every chassis has 4 slots for “Special Modules”. These can include radios, which give bonuses to breakthrough and defense; secondary turrets for all your T-35 needs; smoke launchers; extra ammunition storage and wet ammo storage. Deciding whether or not a tank uses sloped armor also happens in this area. Perhaps most intriguing is the Amphibious Drive, which allows you to designate a design as an amphibious tank for the purpose of amphibious tank battalions (MtG owners only).

Designating designs for certain roles ensures that they are used in those subunits. Some roles require certain characteristics - for example, you can’t have an AA tank that uses a fixed superstructure. But it is completely possible to make both the German tank destroyers with fixed superstructures and the American ones with turrets and have them go to tank destroyer units. The weight class of the chassis determines the weight class of the final design, so a design on the heavy chassis that is designated as a tank destroyer is treated as a heavy tank destroyer. This also means we can represent vehicles that changed roles during the war more easily, so you can have your StuG III equivalent with a high-soft attack gun go to your armored artillery battalions in the early war, but then switch out the gun to something with better piercing and have it work as a tank destroyer afterwards.

Since we want you to optimize designs for different purposes, we also wanted to make sure that you can easily decide where a certain tank design ends up. So for example, you can follow the British approach of having fast cruiser tanks to use in armored divisions, and slower infantry tanks that go to support your infantry divisions. To do this, you tag a design with a symbol. You can then quickly select from a list of symbols in the division designer to make the division only pull equipment tagged as such. Equipment that isn’t tagged (such as lend-lease and captured foreign equipment, or equipment not tagged at all) will still be used for divisions that don’t have a specific tag requirement set.

We also took another look at what automation features were necessary for people who don’t want to spend a lot of time fine-tuning their tank designs (weird and alien though that thought may be to most of us). We do, of course, have the usual auto-design functionality. It takes the design the AI would use and offers it for approval. This has gotten some love, and there should now be some national flavor in how the AI designs its tanks. It also takes the overall situation into account, so tanks will be up-armored during the war and so on. Beyond that, we also have added an auto-upgrade function, which keeps a given design current as you research new guns, chassis etc. You can either click on a design you made in the past and upgrade it with a single click to the newest components (so a Radio I becomes a Radio II etc.), or click a checkbox to do so automatically. You don't have to pay XP for an automatic design upgrade, but you won't get thicker armor or a better engine that way. Still, we think that the combination of auto-design and auto-upgrade allows players to interact with the system as much or as little as they like.



To make the tank designs more visually distinct in the production view, we have added about 1000 new 2d icons to use for them, mostly stemming from combining parts of existing tanks in new ways (the gun of Tank A with the turret of Tank B etc.). The historical icons are, of course, still available. You can select the icon while making the design, as well as the 3d asset used to represent the vehicle on the map.





That’s all from us today for this feature. Before closing, I would like to note a few things on the subject of giving feedback. When I first started at Paradox, the direct line between community and developers was a major plus for me, because I liked the idea of talking to the community without having to run every post past three different marketing departments first. However, this kind of direct community access comes at a heavy cost for us. As many of you have noticed, we have gotten a little sparse in these forums in the last few months, or even years. The reason for this is that often we do face a debate culture that is not enjoyable to take part in, where it is taken as a given that the devs are either lazy or incompetent and where everything we do is viewed through that lens. Not only is it incredibly demoralizing to spend months of your life creating something, only to see the people you made it for tear it to shreds, it is also a debate that gives no one anything. We aren’t paid to wade through pages of abuse to find a few nuggets of useful feedback, and so that feedback is not acted on. A lot of you have access to sources in languages we don’t speak or have studied some detail that we weren’t aware of. Such feedback is very useful - just a few weeks ago someone sent me a plan of the Turkish railways in 1936 taken from an old Turkish book, so I was able to use that to update the Turkish railway setup at game start.

We’re not looking for fawning adoration (although we will certainly accept it) or a forum in which our decisions can’t be discussed with a critical eye. We want to have your feedback, but there is no point to it if it can’t be delivered with a minimum of respect for each other. If you want to have a forum where developers are willing to go and answer your questions, then it is also your responsibility to build a place where we feel welcome, and where we can disagree in a productive and professional manner. It costs you nothing to assume that we were acting in good faith. None of us wake up in the morning and go to work in order to do a bad job.

Extra Secret Spoiler: here are some tank designs QA has made over the past few months while we were developing this. Please note that the numbers on the screenshots are several versions out of date and that the issues pointed out in these shots have been fixed since then.

[h3][For the full list go to the full diary here]
[/h3]

Hearts of Iron 4's new DLC and patch will explore Poland's rich, alternative, history

World War II grand strategy game Hearts of Iron IV is building steam towards its as-yet unannounced new DLC, as well as the 1.11 Barbarossa patch that between them is looking to really shake up how the war game portrays WW2's Eastern Front. As part of this, they'll also be looking at overhauling more nations' Focus Trees to give players more options with how they navigate the perils of the Second World War.


Poland is the first nation to be highlighted in the recent run of developer diaries. The first one looked at what free content Poland will be getting in the 1.11 patch, where-as today's dev diary covers premium Focus Tree options from the expansion.


In recent Hearts of Iron 4 DLC, Paradox has developed the Focus Tree system into a branching narrative of sorts, giving nations various paths they can take. There's the historical path, as well as various alternate history options depending on the nation in question. For example, you can play as Nazi Germany but instead overthrow Hitler and restore the Monarchy, or found a new German Republic.


Read the rest of the story...


RELATED LINKS:

Hearts of Iron 4's grand campaign is live, using a custom mod developed in six days

This Hearts of Iron 4 mod map helps you navigate a complex web of alt-history

Hearts of Iron devs and former CEO speak out against toxic feedback in EU4 drama