Hand of Chayula Missing Hits
Palm skills can't be evaded (includes hand of chayula) - it's written on the tooltip of those skills, yet there are instances where they will miss or whiff or whatever you wanna call it.
I did testing and I have freezing mark on it, it happens that it will not apply the mark even if it visualizes hitting the target (no mark icon above monster). Last bumped on Sep 28, 2025, 9:48:11 PM
|
![]() |
I also have issues with it hitting.
Some maps it is fine, then suddenly it struggles to hit at all. I have socketed with a guaranteed hit when enemy at 100% life support and it still had the same issue. It just misses, even from close range. |
![]() |
Having the same issue here, I hope it gets fixed. Seems like point blank it registers 80% of the time. From a distance its like 5%...
|
![]() |
Still an issue, a Dev replied back in 0.1, I think they are still working on it.
|
![]() |
Got into this problem recently, very annoying.
It depends a lot on the enemy. The smaller ones I hit almost all the time, but bosses are harder to hit (especially phase 2 Doryani, I just could not hit him even while hugging his mech's spiky butt). I just got out of a test build with Siphoning Strike, which didn't miss at all, so it made me think that maybe the melee strike range helped (this skill has +6 range intrinsically). So I allocated +2 range on the tree (Reaching Strike), and since then I miss a lot less (but still do sometimes). It definitely helps not whiff the hit. I assume the bug is caused by palm skills using unarmed range, which must be really low (I can't find the number), and pathfinding around obstacles / enemies. The character always throws the hit close to the enemy, just not close enough, maybe because the enemy moved, or because your pathfinding deemed the position to be good enough to land your hit when it isn't. I don't know how the game calculates distances for hits, whether its from the center of your character to the center of the enemy, the edge of your hitbox the your enemy's, or something in between. But if it's closer to the first option, then that might be the issue. Here's how it looks without any melee strike range if anyone is wondering :
Spoiler
![]() |
![]() |