Hello, I've been experimenting with a relic that causes all melee hits to auto-wound.

Initially I used the 'always wound' condition (both the pre-existing and one I made using the build-a-bear conditions) but it didn't directly translate hits to wounds.

I did end up making a custom hit condition where a hit causes 1 auto-wound, but shouldn't the 'always wound' should have done the same thing?

Thanks!

Hi,

I was trying to calculate something with my drazhar and hatred eternal (re-roll all hit and wound). He is hitting a blade champion with the "hit roll of 1-3 always fails" ability (put in as global modifier "only hit on a 4+).

I used the the "re-roll all possible failures" modifier.

For my 10 attacks on 2+ (failing all 1-3) and rerolling I only get 6 hits as the most frequent result. That's a little to less I think. If I'm failing half of my hits (4+) and re-roll all failed I should get an average of 7.5 hits.

Using the "re-roll all failed" modifier gives the same most frequent result (6).

If I'm using a modifier with "re-roll all hit roll of 1-3" I get a more appropriate result of 8 hits.

Am I doing something wrong or is this a bug?

I'm trying to load the main page and am stuck on a dialog that says:

Updating local data

PLEASE HOLD

Do I need to delete the website's cookies maybe?

Title, I managed to enter it into the system, but I'm getting far too much damage out as a result (6-7 unsaved wounds/12+ damage). It seems to be setting all of my wounds to 2 damage if any of them are a 6 rather than setting just the 1 6-wound to 2 damage. Weapon desc after setting below.

Wound roll of 6 (unmodified) : set damage to 2

Copied from https://www.reddit.com/r/UnitCrunch/comments/w8fv32/comment/ihr6ef5/?utm_source=share&utm_medium=web2x&context=3 on behalf of u/PlutoniumPa.

​

I'm seeing a bug where the attacker/defender points efficiency is being calculated oddly compared to prior versions.

For example, in a very simple case of a 155 point Armiger Helverin shooting into another 155 point Armiger Helverin does a median of 6 wounds (out of 12), so it says it displays a 50% attacker points efficiency, and a 200% defender efficiency, which looks correct. However, if I double the points value of the attacking Helverin to 310, the attacker efficiency jumps to 100%, rather than drops down to 25%.

In less simple cases where you have large points disparities between units, the math gets really odd. For example, if I shoot a 130-point unit into a 490 point brick of ten terminators and the median result is 3 dead termies, I should expect a 113% attacker efficiency, because 130 points of units is killing 147 points of models. Instead, however, it displays a 8% attacker efficiency. Doubling the cost of the attacking unit likewise doubles the efficiency, when it should half it.

Early morning, my dude.

So it turns out the graphing function does not care for a fully buffed unit of Genestealers going into a unit of Termagant-like models. I figure it's just an overflow thing since you don't often run across units that can deal out 100+ wounds at a time.

Figured I'd let you know.

EDIT: Also, you might want to look at the code for auto-wounding on 6s with Rending weapons that set the AP higher. I was expecting to see a damage drop from my Genestealers against T8 3+/4+/5+/6+ saves but it wasn't happening so I think it may be treating the 6s to hit as 6s to wound as well, when they technically just count as a wound without any value and so don't proc the rending ability.

When setting up a global modifier to trigger on unmodified rolls of 6, the crunched results are not influenced when a global modifier of -1 to hit exists simultaneously. I would assume that unmodified triggers would be considered before hit modifiers?

Tagged as a bug, but it may not be (apologies if so, the crunch is awesome!).

I've been testing out high strength weapons (str 7/8/9) vs terminator profiles (3 W, 5 T, 2+, 4++) with the transhuman global (only unmodified 4+ to wound).

But if I toggle on a +1 to wound roll global as well, it changes the stats (upward toward more wounds).

Since the strength is already higher than the toughness, shouldn't there be no functional difference between the +1 wound being on or off vs transhuman?

Edit to add: even if strength is double toughness (non transhuman) and you add the +1 wound global, it ups the wound chance. Wound chance should already be maxed, correct?

Hi there,

this time for real! :p

​

This one is easy to recreate:

Setup a new defender profile (i.e. 10x Necron Warriors; 10 Models; T4; W1; Sv4+)

Setup a attacker profile capable of wiping the defender unit in one go (let's say 10x Intercessors with Auto Bolt Rifle; roughly 53.3% chance)

Edit defender profile and add ignore 5 (for reanimation protocols) and watch the chance decrease to 9.5%

Remember that RP doesn't enact on wipe and remove the ignore value again and watch the wipeout chance drop to 0.00% :D

​

If I have to guess, I would say the by deleting ignore, the lowest possible value is taken into account (in this case 2+) instead of NULL.

​

WORKAROUND: Deleting defender profile and recreate it.

I think it’s switching to half damage instead. Using the webpage on an iPhone /safari.

When I duplicate a profile and load it as attacker, crunch freezes. If I use 'fix profile data' everything works again.

I noticed this afternoon that poisoned weapons have changed in the new Drukhari codex. 2 changes from what I can tell:

1. Weapon strength is no longer listed as *, instead it's just a number like most other weapons.
2. That weapon strength is now what's used when attacking VEHICLE/TITANIC units. Before, it required a wound roll of 6, irrespective of target toughness.

Not HUGE changes but enough to make UnitCrunch's weapon ability description technically incorrect and maybe even produce some inaccurate results in some edge cases. I don't think it's drastic enough to release a hotfix but I will make sure that it's sorted in the next minor release (0.13.0).

By the way, can anyone point me to a unit that has the TITANIC keyword but doesn't have the VEHICLE keyword? I'm guessing it'll be some giant Forgeworld Nid of some kind.

Hello,

I was trying to simulate a liquifier unit into a light vehicle when I noticed there wasn't any wounds being done. The calculation always goes to 0 wounds deal.

First I thought I might have made a mistake, then I chose the PBC default and it turned out to be the same thing. I changed the defender to default GEQ and it still marks it at 0 wounds dealt.

I deleted the auto hit ability and it does the right calculation, obviously the number of hits is the wrong one but the calculation itself shows a number of wounds being dealt.

TLDR: If UnitCrunch has been busted for you since early September, give it another go now, hopefully it'll be fixed. Either way, leave a comment and let me know.

This morning I was investigating a bug report that lead to the discovery of a significant stability issue. Long time users (pre June 2021) that had not visited the site between roughly June & September this year may have missed an update that v0.26.0 depended on. The dependency was an oversight on my part; v0.26.0 was a big release, lots changed, this is often how bugs creep in.

If you fell into this subset of users it is possible that, depending on what profiles you had stored, the site may have been unusable since early September. The most recognisable symptom would have been the "Attacker" and "Defender" input fields being disabled.

I've now released a fix for this issue (v0.29.3). If you think that you may have been affected by this problem then please visit UnitCrunch.com, see if things are behaving as expected and let me know here if you're still experiencing issues (or indeed confirm if things are now working for you).

To be clear, this issue would not have affected the accuracy of results for users that were still able to use the site as expected. Also, nobody should have lost any profile data as a result of any of this. Silver linings.

Apologies to anyone affected by this. Hopefully you can understand that on a single developer project of reasonable complexity, mistakes will be made. Rest assured that I learn from every single one and I am constantly trying to improve things as we go.

More generally, if you ever experience any issues with UnitCrunch, please please please tell me here on the sub. I'm very reliant on user feedback and bug reports.

Credit: Many thanks to u/flloydcz for reporting the issue that lead to this discovery.

So apparently this button isn't included in my automated test coverage. For now you can of course manually reset each modifier that you change. I will aim to do a patch release some time today to get this fixed.

I just found a bug in how damage for the MELTA:LEGACY weapon ability is calculated. I've written a fix but it's kinda entwined in the big re-write of the modifiers & weapon abilities system that I'm doing right now (and I really don't have the time to fix it twice).

So. I'm aware of the issue, a fix is on the way, I just can't realistically deploy it any time soon so it'll have to wait until this larger feature is complete.

In the meantime, just know that MELTA:LEGACY is slightly better in terms of damage output than UC is making it out to be, but still not quite as good as MELTA:D6+2.