the bot just show a lot of this: [BeginUseAt] 3 False {206, 695} [InjectKeyEvent] 119 ms sleep for 2. the bot just stand on mobs and do nothing then i watched him died someone know how to fix it?!
You're most likely seeing this issue: Rebind your MMB and RMB to keys or move your main skills off mouse buttons altogether. That should help. If not, please attach a full log and we'll go from there.
I have the same problem. My cyclone maurader will just stand right on top of an enemy and do nothing. It only continues to attack if the mob moves. I have bound all my attacks off of the mouse, but that did not help. This is especially annoying in maps with mobs that do not move such as totems and tunnelers. I have to ignore specific maps because of this.
Same here, also stuck near strongboxes sometimes and spamming this shit.. all my active skills are on the second row...
It seems like cyclone will only work if it is applied or used at a spot other then where you are, as if it is required to move to work. If you are right on top of the mob clicking it with cyclone, it wont work. Ive tested other cyclone routines in the past and they do the same thing. It just seems like part of the mechanism of the ability. If I manually press my leap slam button while EB is still working, it continuously leap slams right on the enemy because EB is targeting that enemy but because of the way cyclone has to move to work it doesnt do anything. Wonder if there is a way to fix this? Guess ill just try making leap slam my melee ability and cyclone my range ability, maybe that will work. This does alleviate the problem, however it seems like it is not the most efficient way to play this build.... It just leapslams a boss to death, kinda slow but better than just sitting on top of them until chicken might save you.
Cyclone stuck issues are totally different. You need a routine that specializes in that skills casting mechanics to avoid the "deadzone" around your character where Cyclone fails to cast. This has always been an issue in the game, and the default routine cannot code around this specifically unfortunately.