the siege small cluster jewel

So, i am using totems, and the jewel says attack projectiles will inflict bleeding, maim, and knockback. when i look at the information, i have 100% knockback, but nothing for bleed.

I tried this for skills in both the body armor and the weapon slots.

any ideas?

thanks in advance

X

In order to proc a bleed, your weapon must do at least 1 physical damage. Perhaps you convert all your physical damage to elemental/chaos with that skill?

Also yes, the Kineticism keystone works with Ballista totems or trap/mines that use projectile attacks

using brutality support on explosive arrow with a bow that has flat phys...

still not getting 100% chance to bleed, but getting 100% chance to knockback.

Even when putting a skill like split arrow in place of explosive arrow... i still only get bleed chance that i have allocated on tree....

Brutality makes your skill only deal physical damage. I am not really sure on how this will work with the explosion since it's a Secondary Damage. But that's beside the point.

EA was reworked so that the bow's natural damage will be preserved. If your bow inflict physical damage, and you are not using Avatar of Fire, or anything that would fully convert your damage in elemental, then EA should be able to proc bleeding unless it's supported by Bloodlust

If even like that the EA tooltip (which is not the tooltip you see when pressing C, that's just the Default Attack tooltip) doesn't show bleeding damage, nor it's shown in Miscellaneos/Offensive tab, you may try doing a test right on the field to see if it's just a tooltip problem. What the tooltip says it's not always what you will get.

You can do it in a safe environment by buying a Crude Bow in Act1, slotting there an Explosive arrow, then reach the Epilogue/Act 10 and hit an enemy. You should do little damage enough to make it survive and see if it leaves bleeding's trail behind it.

I dont think it was a tooltip error.

I was not getting on hit (or explosion) bleed effect.

The explosion cannot proc bleeding since it deliver full fire damage (and only fire damage). Only the hit may cause bleeding

Actually, a bit of research and reading shows that the explosion does, in fact, delivers added fire damage and the base bow damage at 50% damage effectiveness. So... yes, apparently the explosion may cause bleeding if the bow. Sorry about that. I could swear there were specific interaction with Elemental Equilibrium on Explosive Arrow because of the full-fire damage from explosion...

Anyway. If you are not supporting Explosive Arrow with bloodlust, and not convert 100% of your bow damage to element/chaos, then with Kineticism it should totally deliver a bleeding.
Perhaps it can only make always bleed an attack that has a chance to bleed? Have you tried supporting EA with a Chance to Bleed support gem and see what the tooltip says?

If even like that you can't proc bleeding, then it's indeed a bug, and a nasty one. People use kineticism specifically for the non-pierce and extra bleeding for a perfect Ensnaring Arrow totem

I talked with support. They said they cannot help, and referred me to the forum.

but i was definitely not getting bleed effects, until after now, getting more %chance to bleed nodes in my tree.

no bleed on impact or explosion.

Sorry, I did not understand. Are you saying that you started having bleeding when you allocated a node for chance to bleed? Or even with those nodes for Chance to Bleed you are still not causing bleeding? Or that you had bleeding because of your passive's nodes that gave you chance to bleed, then stopped causing bleeding after getting Kineticism?

Your characters are private, so I don't know if there is something in your passive/equipment that can justify this beside bug

things have only started bleeding since allocating points on the tree.

sorry for the confusion.

i will try and make the profile public when i get around a pc.

So in order to proc the "always bleed" you need to have at least 1% chance to bleed.
I am pretty sure that's not how it's supposed to work, but it's how it's working nevertheless...