Profile of Mr.Smith

Also people here talk a lot about conscripts being better at close range, let me explain something to those of you who think cons have better dps at close range than any axis unit.

Close range squad dps (upgunned)
sturmpios - 65,32
pgrens - 63,12
rifleman - 38,30 (46,06 - 2 bars)
penals - 34,20
sappers - 30,92
pios - 28,96
grens - 24,88 (26,32 - mg42)
volks - 24,70 (44,26 - stg)
rear echelon - 23,12
cons - 21,42
tommy squad - 20,88
combat engis - 13,68

DPS isn't the only thing you need to account for.

Personally, I would use the following formula to get a good first impression on unit cost-efficiency. The same formula works the same regardless of whether you're taking individual models or entire squads into account. Slot items will, of course, skew the result of the formula.

Cost efficiency per squad: (DPS of squad) * (effective health; received accuracy/hitpoint sum) / (cost to reinforce entire squad)

The cost efficiency of the squad is not a static value, and varies with range.

The cost efficiency curve is also not a set of numbers in a vacuum, and should always be compared with the cost efficiency of other squads at other ranges.

Moreover, even relative cost efficiency isn't a good metric, since squads will almost never fight it out stationary over long periods of times (or if they do, there will be snipers/etc involved). A low-DPS squad will be useless at killing enemy troops while they move to THEIR optimal range. A high-DPS (but low-survivability) squad, will have trouble surviving to get to close-range. That's why you can have stuff like cost-inefficient vanilla Conscripts and OP ppsh conscripts at the same time.

Conscript cost efficiency at Vet3 is bad; but not super-duper-bad. The major issue is how unreliable Conscripts are at getting it (due to their low-accuracy, RNG Mosins), and how badly they become bled while getting it (due to terrible long-range performance of Mosins). Also, if Conscripts die, forget about getting a late-game squad; they will never gain that level of vet again.

PS: Try Vet3 Conscripts vs Vet3 G43 Grenadiers. Pick any range you want and see which squad will always win. Now, take into account the kind of weapons supporting OST and Soviets.

I don't know how to do what you're asking. However, what I would start looking for is a way for squads to gain additional XP when they land a killing blow. The rest is easy.

I've never used kill_actions. However it sounds much cleaner than what I am about to recommend, so I suggest you continue toying around that.

1. Awarding veterancy

If you look at the tiger ace files, there's an action that awards veterancy to the tiger (it's either in the ebps file or the sbps file; can't remember). What you need to do is find a trigger for it.

2. Adding a Trigger (try to avoid it, if a better way exists)

If no such trigger exists, you can create your own trigger as follows:
- Go through each entity in the files and look for their death criticals (e.g., vehicle_destroy for vehicles, and I don't know what the name for soldiers is).
- Remove the destroy/brew-up/whatever criticals from the entity file; you're going to add them manually to the weapons
- For every weapon in the game, add a post-damage action that checks for the HP of the target:

Do so as follows:
- If the enemy unit has 0% HP, you should trigger vehicle_destroy on the enemy vehicle
- You should also trigger a veterancy-awarded action on your own unit (change-target-action -> self; award veterancy)
- To keep the interface clean, I recommend creating a special my_vehicle_destroy_crit and my_infantry_kill_crit. Inside each of those crits you call the actual vehicle destroy crit, and you also award the veterancy to the killer
- Inside the my_vehicle_destroy crit, you should also specify how much veterancy each vehicle should award (check Brit Command Vehicle to see how you can have a "switch" statement like this).

3. Removing on-hit veterancy

Once you've done the had part, what remains is to prevent units from awarding veterancy when hit (but are still alive). The way to do this is add an "awarded_veterency" (sic) modifier to each squad sbps with a multiplier set to 0. You can find the precise name of this modifier under sbps -> veterancy.

Currently this modifier is used to add 20% XP worth to each unit as it vets up.

4. Schreck veterancy (not a solution, but for reference)

The hack we used to fix schreck veterancy is commute some raw damage to a 'damage' action. That is because we, accidentally, discovered that the damage-action awards no veterancy of its own.

The schreck-veterancy method is ugly, and you should probably avoid this, as it will make your files difficult to read. Even if this works, I would only integrate this at the final stages of your mod, so that you have the flexibility to update the weapon files in a more humane way.

There's also armor values.

If the penetration on the Jackson were exceptionally high compared to the grand arsenal of mediums they would be able to damage heavy tanks much more reliably without affecting their accuracy or the size of their targets.

I feel like armor values are as non-sensible as target-sizes and pop cap.

Armour values aren't so bad (at least nowhere near as terrible as popcap and target size). What's bad is that penetration values across the board are very flat. Your medium tank has roughly the same chance to penetrate while sniping the enemy heavy from afar, just like going point blank (where it's kill-or-be killed territory).

At the same time, vehicles also lack side armour, which means that firing from the side might lead to, sometimes, your shots hitting front, or sometimes hitting the juicy rear armour. Since rear armour for heavies has been nerfed to be almost always penetrated by mediums at any range, you get the frustrating frontal rear-armour snipes that degrade heavies.

Also, designing a turreted tank that has a very high penetration gun might lead to pantheritis, where you get no reward for flanking the enemy (except for risking your own very expensive vehicle).

But yeah; penetration is the way to go if you want to draw a line between efficiency vs mediums and efficiency vs heavies.

The thing is that the luchs is well supported. You have fausts from volks and a raketenwerfer to protect the luchs from the t-70. The t-70 however doesn't have at backing him up and doesn't have fausts backing him up. Luchs still penetrates t-70 and with all it's support it will easy win the fight.
Imo it doesn't matter the luchs is less at then t-70 and stuart. It will still be worth it if it's a bit more expensive if you support it well like you always do.

If PTRS had a decent reaction time, you would be able to at least use them vs the Luchs. Also, if the Luchs didn't hit every single hot, it wouldn't be as good vs vehicles, as you can't really stop-shot with long bursts.

WFA teching is already non-sensical enough with uber-expensive support weapons and stuff that you only build once per game. A better fix is increasing the teching cost, rather than the unit cost (which also affects late-game and replace-ability).

However, for Luchs, it's mostly a lack of counters (handheld AT, and conscripts sucking), and those accuracy issues we missed while making WBP.

It's difficult to fix these things yes i know, but after the patch okw will remain op and i just don't want us to fall into another axis op year like we just had for 1.5 years with allies

I don't know how the decision-making works up there at Relic, however you have to take it up to them Hopefully, with the Ardennes Assault fixed, we will be able to patch the game more frequently.

Yeah, Sturmtiger is annoying as hell. Not only can it wipe infantry out of nowhere, but also medium tanks.
I had it so often, that my tank got stuck or tried to rotate around something because of the wonderful pathing and then there is no escape from the mighty stumtiger shell. Sturmtiger can almost one shot a Comet and that's just ridiculous. And don't forget how freaking cheap it is.

If I were to correct you, I would say it one-shots everything. If you're not too unlucky, the Sturmtiger will apply the beautiful permanent immobilize critical, and good luck getting that tank moving after that.

For people that complain they can't vet their Sturmtigers, you aren't aiming them at the right targets.

• Why are there squad and entity veterencies? I heard before about some glitch that wasn't patched for years... not sure if this is why? When for example, I want to change weapon accuracy for a squad vs change received accuracy, where would I have to put each veterency, and why?
  

Note that for certain team-weapons you might want to apply the modifiers only on the gun, rather the entire squad (e.g., raketenwerfer range).

Also, veterancy on teamweapons that can pack up is bugged/unreliable. We have a fix coming for it in the next patch.

• Why do squads have the modifier "entity_veterancy_experience_modifier" with usage_type multiply_add and value 0.2? I've seen this time and time again and don't understand what it does?
  

Multiply add stands for add + 20% of the original (pre-modifiers) value. This is different from a multiplication 1.2, when you intend to apply this multiple times.

Applying a 0.2 multiply add 3 times gives you a +60% difference from the original value
Applying a 1.2 multiplication 3 times gives you +72.8% difference over the original value

Also, how does construction speeds work? Barbed wire has a time cost of 24. Is this time divided by the number of models building? So would a 4 model engineer take 6 seconds, and a 3 model engineer 8 seconds? If that's true, and I change a 4 model squad to be a 3 model squad, would I have to increase the construction speed modifier on the 3 model squad by 1.33 to achieve the same speed?

Note that the construction entities themselves may also have a cap on how many models are allowed to contribute at the same time. Usually this is 8 models, but you can finetune it. E.g., if you want to prevent the sim city commander Tommies from powerbuilding emplacements, you can set that there.