Energy attacks no longer work for psychic thorns?

I take psychic thorns path in war, and have always used sparky to clear it. (The strategy being build 10 poise then spam heavy attack, as the heavy is (or was) energy damage and did not trigger thorns)
Today in war my sparky was reciving thorns damage on 70% of the heavy attacks he does (Because I have 30% reduced accuracy while stunned mastery, without that it would have been triggering 100%)

What gives, is sparky no longer dealing energy damage on his heavy, or do all energy hits now take damage as well?

Comments

Cryptic_Cobra

Has nobody else had this issue?

Cryptic_Cobra

Still having this issue.

Gamer

I’m just use sym and didn’t hav any problem

Cryptic_Cobra

Well I doubt my sparky is the only one changed. Used his heavy on HT today and confirmed it is not dealing energy damage anymore, as he doesn’t smolder.
Why was this changed without telling us @Kabam Miike

Pach

Can you show a video

Cryptic_Cobra

Can you show a video

Sure, I have already done my aw path today so can’t show that specifically, but I can show proof that sparky is no longer dealing energy damage on heavy.

As you see here, all energy hits will cause HT to smolder, so that makes him a great way to test what is and is not energy attacks. (Keep In mind as I said I run the 30% ability reduction mastery, so you could pretend that’s the sole reason for why HT isn’t smoldering, bg I feel I have demonstrated enough hits that any reasonable person would deem that a statistically anomaly. I could make 100 recordings and they would all be the same.

So with that, here is what you requested

https://youtu.be/JMw4uog0Bts

disgruntled

@Kabam Miike
Can you clarify this please?

Summary:
Stark Enhanced Spider-Man’s heavy attack is described as an EMP webshot, is animated like an energy attack, and used to be treated as energy attack a month ago (including not taking damage back on a psychic thorns node).
It is no longer being treated as an energy attack.
Why was this changed? Why was it not in the update notes? Or is it an unintentional bug?