What's new
By:
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

Skill usage

K

kalanikila

Member
Joined
Nov 28, 2012
Messages
293
Reaction score
5
Is there a way to force the bot to use a skill? Cyclone for example will run into a pack of mobs and just stand around till it dies. I can do a map by hand in under 4 mins but using EB i just die constantly in a T1 map.
 
It depends on your routine configuration, but make sure to use ranged and melee slots (consider maybe leap slap for ranged). Make sure to try the new builds just pushed, because it seems there were some skill changes in the last patch, and trying to retest all skills would take too much time. I can checkout cyclone soon though, but its easier if users try it first.
 
Ive tried that. The issue Im running into is the bot will come to a wall or an object and just stand there. I know its in in game because GGG addressed the issue of cyclone doing that in 3.0
 
[FinishCurrentAction][True] Waited 0 ms for the action to finish Cyclone.
[FinishCurrentAction][True] Waited 112 ms for the action to finish Cyclone.
[FinishCurrentAction][True] Waited 237 ms for the action to finish Cyclone.
[BeginUseAt] 3 False {310, 944}
[Logic] Could not determine the path distance to the best target. Now blacklisting it.
[Blacklist::Add] Blacklisting object with id 898 for 00:01:00 (Expires at: 08/18/2017 00:51:50). Reason: Unable to pathfind to.
[MoveTowards] Moving towards Trunk at {313, 903} (distance: 39)
[BeginUseAt] 7 False {288, 943}
[Logic] Could not determine the path distance to the best target. Now blacklisting it.
[Blacklist::Add] Blacklisting object with id 904 for 00:01:00 (Expires at: 08/18/2017 00:51:51). Reason: Unable to pathfind to.
[BeginUseAt] 7 False {292, 945}
[OpenChestTask] Abandoning current chest because its too far away.
[TrackMobTask] Cached monster locations: 87
[TrackMobTask] Moving to "Croaking Chimeral" at {305, 942} (distance: 41)
[UseAt] 7 False {292, 942}
[TrackMobTask] Alive monster is nearby, this is our 1/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 2/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 3/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 4/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 5/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 6/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 7/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 8/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 9/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 10/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 11/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 12/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 13/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 14/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 15/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 16/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 17/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 18/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 19/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 20/20 attempt to kill it.
[TrackMobTask] All attempts to kill current monster have been spent. Now ignoring it.
[TrackMobTask] Alive monster is nearby, this is our 1/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 2/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 3/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 4/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 5/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 6/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 7/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 8/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 9/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 10/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 11/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 12/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 13/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 14/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 15/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 16/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 17/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 18/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 19/20 attempt to kill it.
[TrackMobTask] Alive monster is nearby, this is our 20/20 attempt to kill it.
[TrackMobTask] All attempts to kill current monster have been spent. Now ignoring it.
[TrackMobTask] Cached monster locations: 85
[TrackMobTask] Moving to "Mountain Hound Alpha" at {301, 759} (distance: 182)
[BeginUseAt] 7 False {282, 945}
[BeginUseAt] 7 False {282, 947}
[InjectKeyEvent] 172 ms sleep for 82.
[BeginUseAt] 7 False {263, 948}
[InjectKeyEvent] 168 ms sleep for 82.
[TrackMobTask] Cached monster locations: 85
[TrackMobTask] Moving to "Mountain Hound Alpha" at {301, 759} (distance: 185)
[TrackMobTask] Cached monster locations: 95
[TrackMobTask] Moving to "Mountain Hound Alpha" at {296, 758} (distance: 133)
[Logic] Now moving towards the monster Mountain Hound because [canSee: False][pathDistance: 66.27715][blockedByDoor: False]
[FinishCurrentAction][True] Waited 0 ms for the action to finish Move.
[UseAt] 2 True {309, 826}
[LatencyWait] Now sleeping 76 ms.
[FinishCurrentAction][False] Waited 0 ms for the action to finish Blood Rage.
[FinishCurrentAction][False] Waited 157 ms for the action to finish Blood Rage.
[LatencyWait] Now sleeping 76 ms.
[BeginUseAt] 3 False {305, 791}
[Logic] Now moving towards {303, 776} because [dist (50) > MaxRangeRange (35)]
[BeginUseAt] 7 False {306, 813}
[Logic] Now moving towards {303, 779} because [dist (44) > MaxRangeRange (35)]
[Logic] Now moving towards {303, 781} because [dist (39) > MaxRangeRange (35)]
[FinishCurrentAction][True] Waited 0 ms for the action to finish Cyclone.
[FinishCurrentAction][True] Waited 126 ms for the action to finish Cyclone.
[FinishCurrentAction][True] Waited 259 ms for the action to finish Cyclone.
[FinishCurrentAction][True] Waited 377 ms for the action to finish Cyclone.
[FinishCurrentAction][True] Waited 492 ms for the action to finish Cyclone.
[BeginUseAt] 3 False {303, 784}
[InjectKeyEvent] 154 ms sleep for 2.
[BeginUseAt] 3 False {301, 756}
[Logic] Now moving towards {301, 763} because [dist (16) > MaxMeleeRange (10)]
[UseAt] 7 False {301, 764}
[TrackMobTask] Cached monster locations: 131
[TrackMobTask] Moving to "Scum Crawler" at {374, 754} (distance: 69)
[BeginUseAt] 7 False {319, 767}
[InjectKeyEvent] 69 ms sleep for 82.
[Logic] Now moving towards {379, 758} because [dist (67) > MaxRangeRange (35)]
[Logic] Now moving towards {379, 758} because [dist (63) > MaxRangeRange (35)]
[Logic] Now moving towards {379, 758} because [dist (59) > MaxRangeRange (35)]
[Logic] Now moving towards {378, 758} because [dist (52) > MaxRangeRange (35)]
[Logic] Now moving towards {376, 758} because [dist (46) > MaxRangeRange (35)]
[Logic] Now moving towards {375, 758} because [dist (42) > MaxRangeRange (35)]
[FinishCurrentAction][True] Waited 0 ms for the action to finish Move.
 
Thats waht the log says every time it just stands there while fighting a mob. IF i dont die it will just black list and move on if not its rip over and over in the same spot
 
Do you have the "Always Attack in Place" option set in the routine? Try that if you do not.

The issue you might be seeing is a game mechanic with Cyclone and the routine not really being coded around that specific skill.

Alright so there's this concept called a "dead zone" with input. It means any actions that take place within a certain zone around your character fail to execute. Cyclone is one such skill where the client's dead zone can prevent it from casting in certain cases.

Basically, the skill cast logic for cyclone needs to be custom, where you're always attacking "through" the path to a monster than attacking "at" the monster. So imagine Firestorm, you cast it near the monster, AoE effects hit all around. If you cast it further away, you miss your target.

Cyclone, you need to attack far "behind" the monster, and the skill travels the entire path, kind of like a projectile would. The default skill casting logic is not meant for that, so that's why Cyclone has issues out of the box.

3.0 cyclone casting was greatly improved, but the routine is not coded for any one particular skill. For best results you most likely need a custom routine. We'll have a routine update release in the near future to help with issues like this, but for now, you just need to tweak your settings to see if you can get something that works nice, or switch Cyclone to a ranged skill and use another up close melee skill to avoid having it cast so close and fail.

Also, make sure you're casting from a Key and not a Mouse button. That is another game issue where skills can fail if they are on LMB due to interaction logic taking over.
 
You must log in or register to reply here.
Back
Top