[POE 2] Titan Ascendancy "Crushing Impacts" disables Keystone "Heavy Contact"
Hi,
I am currently building on a heavy Stunner and try to combine the different Keystones with each other. When I use the Titan Ascendancy "Crushing Impacts", the Keystone "heavy contact" will not be triggered. Crushing impact does: "All your hits are Crushing blows" Crushing blows mean: Every hit i do, if my target is primed to stun, it will be stunned What does "Heavy contact" do: All my hits that "heavy stun" will have culling strike. The passive tree defines hits as "everything that is not a damage over time counts as a hit" My thought process: - I do heavy stun damage on enemies, - they are prime to stun -> Sunder triggers the heavy stun through "Crushing impact" -> I did a "heavy stun", therefore "Heavy contact" should procc. When i remove the ascendancy, "Heavy contact" seems to work. Am i missing something here? Or is there maybe something that declares crushing blows not to be hits? Last bumped on Jan 12, 2025, 10:24:17 PM
|
![]() |
Also not working:
Splinter Support with Sunder |
![]() |
Also it disables the Boneshatter aftershock combo because it uses the Prime for Stun debuff to applies heavy stun. Wasted points on this ascendancy as my gameplay was Leaping and priming enemies for stun and after that finishing with boneshatter.
|
![]() |
" That is intended i think. I wanted to skip the part with the boneshatter aftershock with skilling that the prime for stun debuff is instantly popped |
![]() |
+1
This is most likely unintended, imo. Feels like it should work perfectly. Hope they fix it soon. |
![]() |
After the update nothing changed. "Heavy Contact" is still not working with "Crushing impacts"
Also Sunder still does not work with "Splinter Support", even though implied when hovering over the support gem. Last edited by MaddinMakellos#3869 on Dec 18, 2024, 6:28:05 AM
|
![]() |
Let's take a look.
Crushing Impacts: Your hits have crushing blows Crushing Blows: Crushing blows cause a heavy stun on enemies that are primed for stun Heavy Contact: Hits that heavy stun enemies have culling strike Now what is a hit? Hit: Any damage that isn't damage over time is a hit Here's where I think the problem may be. Culling Strike: Blah blah blah 30% 10% 5%. These thresholds are checked before the damage of the hit is applied. Are the enemies below these threshold before the hit that heavy stuns? If you are heavy stunning enemies when they are full life and knock them down to 1% health, culling strike will not go off. Now for sunder, while the implied interaction may be confusing, I think the answer is obvious. Splinter: Break Armour equal to 15% of Physical Damage dealt by Supported Skill Sunder: Wave +1.4 seconds to Total Attack Time +0.2 metres to wave length for each wave in the Sequence 100% increased Critical Damage Bonus While Dual Wielding, both weapons hit with 30% less damage Cannot Break Armour Consumes Fully Broken Armour on enemies to guarantee a Critical Hit Wave length is 0.9 metres Wave causes Shockwaves from up to 5 Enemies in each Area Shockwave Attack Damage: (65–265)% 100% increased Critical Damage Bonus While Dual Wielding, both weapons hit with 30% less damage Cannot Break Armour Consumes Fully Broken Armour on enemies to guarantee a Critical Hit Shockwave radius is 1.2 metres Last edited by tyrant14#2537 on Dec 18, 2024, 12:52:41 PM
|
![]() |
Where do you have that information that this spell cannot break armour? Because when I hover over the tooltip ingame, it does not show that information... Which is a little irritating and also qould destroy my whole plan about how i want the build to go
Last edited by MaddinMakellos#3869 on Dec 18, 2024, 6:06:08 PM
|
![]() |
So what i posted was copy and pasted from poe2db. Your comment made me do more investigation.
![]() if you go to the little arrow next to damage, it will open a panel with more in depth explanation of the ability. the ability in the image is fragmentation. on the skill gem itself, it does not say it cannot contribute to freeze buildup. in the additional details tab, it does. HOWEVER we don't even need to go that far. If you hover over the payoff tag we get... ![]() i think its a little bit of an oversite, but it does force people to read. Last edited by tyrant14#2537 on Dec 19, 2024, 9:50:54 AM
|
![]() |
Well, that sucks for me.
But thank you for the clarification! Much appreciated |
![]() |