Hextouch isn't a trigger gem.

There is no Hextouch feedback thread in the 'support gem feedback' section, so I thought this would be the most appropriate place for this complaint.

Hextouch isn't a trigger gem as it doesn't trigger anything. It simply applies a curse to a target. It is no more a trigger than blasphemy is a trigger.

Hextouch having the 'trigger' tag is an arbitrary restriction to nullify automation of curse application, plain and simple.

This tag should be removed.

I agree that this trigger tag doesn't seem accurate and should be removed (I think it's only there to clarify that the curses don't gain Doom but I'm not sure).

I'm confused as to how this stops you from automating curses though? Because automatically applying curses to bosses is literally the only way I've used Hextouch (and Curse on Hit before the change) in the last 2 years or so. If you do something like CWDT-Storm Brand-Hextouch-Flammability, taking damage will automatically create a storm brand which applies Flammability to enemies.

What is it that you're trying to do which isn't working?

Hextouch is it's old name (Curse on Hit) on the other forum
https://www.pathofexile.com/forum/view-thread/547064

"

ARealLifeCaribbeanPirate wrote:

I agree that this trigger tag doesn't seem accurate and should be removed (I think it's only there to clarify that the curses don't gain Doom but I'm not sure).

I'm confused as to how this stops you from automating curses though? Because automatically applying curses to bosses is literally the only way I've used Hextouch (and Curse on Hit before the change) in the last 2 years or so. If you do something like CWDT-Storm Brand-Hextouch-Flammability, taking damage will automatically create a storm brand which applies Flammability to enemies.

What is it that you're trying to do which isn't working?

Nah. Hextouch only works as the only trigger mechanic. You have to self cast/attack with whatever it is attached to. Any other trigger mechanic attached will prevent the spell from procing. Trigger spell weapons, CWDT, Asenath's Chant. For example you couldnt attach a BV + any trigger mechanic + hextouch + curse

"

DaCurse wrote:

Hextouch is it's old name (Curse on Hit) on the other forum
https://www.pathofexile.com/forum/view-thread/547064

Thanks ill repost there.

"

maLcious wrote:

"

ARealLifeCaribbeanPirate wrote:

I agree that this trigger tag doesn't seem accurate and should be removed (I think it's only there to clarify that the curses don't gain Doom but I'm not sure).

I'm confused as to how this stops you from automating curses though? Because automatically applying curses to bosses is literally the only way I've used Hextouch (and Curse on Hit before the change) in the last 2 years or so. If you do something like CWDT-Storm Brand-Hextouch-Flammability, taking damage will automatically create a storm brand which applies Flammability to enemies.

What is it that you're trying to do which isn't working?

Nah. Hextouch only works as the only trigger mechanic. You have to self cast/attack with whatever it is attached to. Any other trigger mechanic attached will prevent the spell from procing. Trigger spell weapons, CWDT, Asenath's Chant. For example you couldnt attach a BV + any trigger mechanic + hextouch + curse

???

I'm sorry, but you're 100% wrong. I've used it on 40+ different builds, including one I'm literally playing right at this instant, and it definitely works:



So I gotta ask, again: what is it you're trying to do that isn't working?

"

DaCurse wrote:

Hextouch is it's old name (Curse on Hit) on the other forum
https://www.pathofexile.com/forum/view-thread/547064

hmmm cwdt might be the exception then.
doesnt work with asenath's
or with "Trigger a socketed spell when you use a skill"

"

maLcious wrote:

"

DaCurse wrote:

Hextouch is it's old name (Curse on Hit) on the other forum
https://www.pathofexile.com/forum/view-thread/547064

hmmm cwdt might be the exception then.
doesnt work with asenath's
or with "Trigger a socketed spell when you use a skill"

Thats because you can not Trigger a Trigger.. Hextouch is Triggered upon hitting with whatever skill you have your Curse Linked to along with Hextouch. Thats what makes it a Trigger Skill it Triggers the Curse on Hit with whatever skill you have the Curse linked to with Hextouch. If you try to Trigger with say Asenath's Helm Hextouch will not work because you are already triggering the Skill put into the Helm you cant also Trigger the Curse via Hextouch as well.

Its also worth noting Marks do NOT work with Hextouch because even though they are Curses they are Marks and Not Hex's and there is a difference between the two. (Thus why the name of the Support was changed from Curse On Hit to Hextouch) I had to figure this out the hard way this league.

If you remove the trigger tag that shouldn't be there, you could.
Its not a trigger gem, as it doesn't trigger anything.
"hex" and "support" are the only tags that make sense.

Just saw this in the wiki.
"Hextouch is considered a trigger only for the linked curse, and not the attacks or spells which are applying it (see Trigger). This means it can be used with trigger skills such as Vengeance or Riposte. It can also be used with Cast when Damage Taken Support, as long as the spell is within its level threshold and the curse is above the level threshold. Minions, totems, mines, and traps cannot use Hextouch".

Some weird word salad to try any justify it working for Vengeance and Riposte. So a trigger that triggers, can trigger, but a triggered cast can't trigger.

As for why CWDT works... gloss over that shhhh.

"

maLcious wrote:

If you remove the trigger tag that shouldn't be there, you could.
Its not a trigger gem, as it doesn't trigger anything.
"hex" and "support" are the only tags that make sense.

Just saw this in the wiki.
"Hextouch is considered a trigger only for the linked curse, and not the attacks or spells which are applying it (see Trigger). This means it can be used with trigger skills such as Vengeance or Riposte. It can also be used with Cast when Damage Taken Support, as long as the spell is within its level threshold and the curse is above the level threshold. Minions, totems, mines, and traps cannot use Hextouch".

Some weird word salad to try any justify it working for Vengeance and Riposte. So a trigger that triggers, can trigger, but a triggered cast can't trigger.

As for why CWDT works... gloss over that shhhh.

It makes sense if you focus on the important detail of, "a gem cannot simultaneously be supported by two separate triggering effects." The CWDT Wave of Conviction I posted works because a when high level hex linked to a low level CWDT gem, the hex is not supported by CWDT (as it says on the CWDT gem, it only supports gems level X and below). Hextouch works with Riposte etc because those gems are not supports, and therefore they are not supporting the hex skill gem.

The reason what you're trying to do doesn't work is because when a Flammability skill gem in your Asenath Chant is linked to Hextouch, the Flammability gem is simultaneously supported by both Hextouch and the Asenath effect, both of which are triggers.

THAT BEING SAID, you can get the exact effect you're looking for if you just don't use Hextouch at all. Putting a curse gem in your Asenath Chant with nothing linked to it will automatically cast said curse on enemies when you shoot your bow.

"

DaCurse wrote:

Hextouch is it's old name (Curse on Hit) on the other forum
https://www.pathofexile.com/forum/view-thread/547064

It just another sign that GGG abandoned that section of the forum.....(Note that i told them to rename the Abyssal Cry thread.....and no action, no reply)