Arrow Penetration Limit Ignored By Compound Bow

[exsanguination microtubules]

1. Wish yourself stat:Strength:99 or similar
2. Fire a compound bow with penetration debug text turned on.

Other bows don’t have this problem and cap the penetration correctly

I suspect this might be because the code that’s supposed to enforce this limit is wrapped in the following conditional in GetMissileWeaponPerformanceEvent.FromPool - I think the event might be arriving here with the penetration values already specified

if (BaseDamage == null || !BasePenetration.HasValue || !PenetrationCap.HasValue || Attributes == null || !PenetrateCreatures.HasValue)

This includes the uncapped value that is determined earlier in MissileWeapon.MissileHit:

            if (!string.IsNullOrEmpty(ProjectilePenetrationStat) && Attacker != null)
            {
                num2 += Attacker.StatMod(ProjectilePenetrationStat);
            }

‌

[exsanguination microtubules]

This now also affects the Turbow after this week’s patch, which enabled strength-based penetration for it.

‌

[chaos]

Fixed in next update.