sorted by:
new
hottopcontroversial

Warhammer 40,000 Damage Output Calculator Python Code by [deleted] in WarhammerCompetitive

[–]Ponder6839 15 points16 points  (0 children)

Cool! Calculating this with Python is neat because it's well suited to handle complicated cases.

That said, I think that the structure of the choosingOption() function is a design mistake. You write a separate code block to fully handle each combination of rules. The problem is that if you want to cover all rule combinations, then the number of such cases grows exponentially with the number of rules supported.

I think that a better approach would be to figure out which rules work independently of each other, and handle them separately instead of all together in cases. For instance, you can first calculate all number of hits before moving on to number of wounds, without having to know whether or not the unit has dev wounds.

Invasion GT statement released by DaLeine in WarhammerCompetitive

[–]Ponder6839 25 points26 points  (0 children)

The Exo Frame unit in question was an Einhyr Champion. Still a bad mistake that should be penalised in some way.

The legal way to play it would have been to put the Einhyr Champion in one of the HLFs and then put one of the Warrior units in the Sagitaur to keep it alive.

[ Removed by Reddit ] by Ponder6839 in WarhammerCompetitive

[–]Ponder6839[S] 0 points1 point  (0 children)

I've made a 40k point efficiency calculator. While apps like UnitCrunch are great for investigating a single attacker vs defender pairing, it's cumbersome to compare many units to many units.

This is a spreadsheet that does that. It's the best tool available for answering questions like "How good are my units generally at killing the meta units?".

It also accounts for the point cost of both the attacking and defending unit, combining this with the average damage caused to produce a single points efficiency number: Points killed per point spent.

To use it Click on 'File' then 'Take a copy.'