So many HT and Byregots fails...

[Sartori]

Am I facing the wrong way?

[Silverbane]

Am I facing the wrong way?

In my experience, it doesn't matter how you face. I've had runs with lots of HT fails followed by fail-free runs without having moved.

[BushWookie]

To the right, man.

You have to face to the right....

[doctapeppa]

The real question here is why are you using BB without SH or SHII up?

[ServerCollaps]

The real question here is why are you using BB without SH or SHII up?

no risk, no fun obviously

[Porkchop]

wrong weather & moon phase most likely

[Ksenia]

Are you still leveling?

In my experience if your exper bar is at 80% or higher Hasty fail triples. Anything associated with progression.

To give you an example. I'm making Cedar lumber, just to level up. I have 12 HQ and 2 NQ in inventory. I get the message that an achievement is almost complete. fail, fail, fail, fail. Now I have 12 HQ and 10 NQ in my inventory. I went and purchased 3 maple logs at the vendor and cleared the achievement. Back to making mostly HQ. I call it the prick mechanic. If you are about to accomplish something, the RnG starts punching you in the face.

[Kiara]

No there is definitely something that CHANGED behind the scenes with Hasty Touch + Steady Hand II.

If you look at the Tooltip it still claims 50% chance of success for Hasty + 30% for Steady Hand II.

Before Heavensward (2.x version of the game), this felt pretty accurate.

I've found in Heavensward (3.0) that if you're leveling a Crafting Class (before 60), and/or don't have high enough gear, there is a high tendency for Hasty Touches (buffed by SHII) to fail FAR MORE OFTEN than the claimed "80% Success."

It feels dishonest. Like there's some scaling going on behind the scenes.

It's the same sneaky change the Dev Team did to NERF the amount of Good Condition Procs you'd get from 2.0 > 3.0. You get far FEWER procs now.

I have all Crafting Jobs to 60 now, but during the time from 50 > 60 when 3.0 launched till now, with hundreds of crafts, it absolutely fails far more often than it did in 2.0 time.

[doctapeppa]

No there is definitely something that CHANGED behind the scenes with Hasty Touch + Steady Hand II.

If you look at the Tooltip it still claims 50% chance of success for Hasty + 30% for Steady Hand II.

Before Heavensward (2.x version of the game), this felt pretty accurate.

I've found in Heavensward (3.0) that if you're leveling a Crafting Class (before 60), and/or don't have high enough gear, there is a high tendency for Hasty Touches (buffed by SHII) to fail FAR MORE OFTEN than the claimed "80% Success."

It feels dishonest. Like there's some scaling going on behind the scenes.

It's the same sneaky change the Dev Team did to NERF the amount of Good Condition Procs you'd get from 2.0 > 3.0. You get far FEWER procs now.

I have all Crafting Jobs to 60 now, but during the time from 50 > 60 when 3.0 launched till now, with hundreds of crafts, it absolutely fails far more often than it did in 2.0 time.

No. It does not. I hate hasty touch RNG as much as everyone else, but it was 80% in ARR and it's still 80% now.

[Silverbane]

No there is definitely something that CHANGED behind the scenes with Hasty Touch + Steady Hand II.
I've found in Heavensward (3.0) that if you're leveling a Crafting Class (before 60), and/or don't have high enough gear, there is a high tendency for Hasty Touches (buffed by SHII) to fail FAR MORE OFTEN than the claimed "80% Success."

Unless you have carefully counted the success rate of a few hundred Hasty Touches (HTs), you cannot say that with any reliability.
Do something like was done in this thread on G/E procs, and report the numbers back.

People typically remember the unusual occurrences better, and therefore often over-estimate how often the unusual occurrence occurs. Only by carefully keeping track can this issue be eliminated, and only by counting several hundred potential occurrences of the event.

I haven't kept track of HTs fails myself, but I've had enough synths where all 11 HTs succeeded to be skeptical of claims that it is not working as advertised. The devs have no motive to lie about it, and I believe it unlikely to have crept in as a bug at this point.