Quick workout for that is editing this file and changing these values: Also, I don't think "Cyclone Target Range" is working properly. No matter what distance you set it to, it seems to not change the actions of the routine. Leap Slam cuz distance -> 23 and targetrage -> 45 Leap Slam cuz distance -> 21 and targetrage -> 45 Leap Slam cuz distance -> 20 and targetrage -> 45 Attack at random pos around me Attack at random pos around me Leap Slam cuz distance -> 30 and targetrage -> 45 Leap Slam cuz distance -> 40 and targetrage -> 45 or Leap Slam cuz distance -> 23 and targetrage -> 5 Leap Slam cuz distance -> 30 and targetrage -> 5 Leap Slam cuz distance -> 40 and targetrage -> 5 It leap slams quite often, even at close range, no matter what setting you change it to..
That is because leap slam is triggered like this: Code: if (Utility.NumberOfMobsNear(LokiPoe.Me, cycloneRange) > 0 && !LokiPoe.Me.IsDead) { ... } else { if (_leapSlamSlot != -1) { LokiPoe.InGameState.SkillBarPanel.UseAt(_leapSlamSlot, true, cachedPosition); Log.ErrorFormat("Leap Slam cuz distance -> {0} and targetrage -> {1} ", cachedDistance, cycloneTargetRange); } }
tried some small modifications to see how it performs. if someone else wants to try it out: my settings: [HIDE][/HIDE] Typhonis.cs https://gist.github.com/Cholik/85546f125b014e6c0a92
So, I've found I like the random targeting feature, but only when a mob is really close. Like let's like 4 or 5 m. Basically within the Cyclone Max Target Range settings. I'm going to tinker with the source code, and test the results and report back. Overall it works great, especially in packs, just sometimes hiccups happen when a mob gets too close and it hangs for a various amount of time (sometimes seconds, sometimes until death). When I play by hand sometimes when a mob gets too close, a similar even happens and it isn't solved until I randomly click somewhere. I think this is why I like the random click feature for this particular case. Otherwise when mobs are at a distance of lets say like 15+ meters away, it usually makes more sense to click either one unit of Cyclone Max Target Range in front of or behind them.
I just wanna use Flaskhelper with this again RF cyclone not so amazing if he cant use ruby flasks and granite at the right time, ya and i miss quicksilver
i have a problem with this routine most time the bot dont fight he only stay in the map and spam TrackMoreMobs even if mobs next to him he dont attack and only track more mobs. is there any way to fix this? . [TrackMoreMobs] Now adding Ancient Archer (646) at {408, 786}. [TrackMoreMobs] Now adding Shambling Cadaver (652) at {577, 803}. [TrackMoreMobs] Now adding Sutured Aberration (618) at {585, 786}. [TrackMoreMobs] Now adding Sutured Aberration (610) at {572, 782}. [TrackMoreMobs] Now adding Shambling Cadaver (656) at {557, 797}. [TrackMoreMobs] Now adding Ancient Archer (645) at {395, 782}. [TrackMoreMobs] Now adding Shambling Cadaver (655) at {595, 789}. [TrackMoreMobs] Now adding Sutured Aberration (612) at {616, 782}. [TrackMoreMobs] Now adding Hulking Titan (660) at {626, 801}. [TrackMoreMobs] Now adding Shambling Cadaver (663) at {605, 797}. [TrackMoreMobs] Now adding Ancient Archer (650) at {400, 785}. [TrackMoreMobs] Now adding Ancient Archer (644) at {434, 782}. [TrackMoreMobs] Now adding Shambling Cadaver (661) at {607, 804}. [TrackMoreMobs] Now adding Sutured Aberration (614) at {600, 782}. [TrackMoreMobs] Now adding Shambling Cadaver (667) at {638, 792}. [TrackMoreMobs] Now adding Sutured Aberration (615) at {592, 782}. [TrackMoreMobs] Now adding Sutured Aberration (613) at {600, 793}. [TrackMoreMobs] Now adding Shambling Cadaver (669) at {643, 801}. [TrackMoreMobs] Now adding Sutured Aberration (617) at {578, 782}. [TrackMoreMobs] Now adding Sutured Aberration (616) at {587, 782}. [TrackMoreMobs] Now adding Sutured Aberration (619) at {594, 782}. [TrackMoreMobs] Now adding Sutured Aberration (621) at {606, 782}. [TrackMoreMobs] Now adding Sutured Aberration (620) at {567, 782}. [TrackMoreMobs] Now adding Ancient Archer (651) at {424, 786}. [TrackMoreMobs] Now adding Ancient Archer (649) at {429, 782}. [TrackMoreMobs] Now adding Sutured Aberration (611) at {554, 782}. [TrackMoreMobs] Now adding Ancient Archer (647) at {413, 782}. [TrackMoreMobs] Now adding Ancient Archer (648) at {418, 782}. [TrackMoreMobs] Now adding Shambling Cadaver (664) at {626, 810}. [TrackMoreMobs] Now adding Shambling Cadaver (666) at {602, 810}. [TrackMoreMobs] Now adding Shambling Cadaver (662) at {637, 809}. [OpenChestTask (Leash -1)] The current chest to open is [443] Chest at {398, 531}. We have been on this task for 00:00:00.7453489 and have been attempting to interact for 00:00:00. [OpenChestTask (Leash -1)] Now moving towards the chest 443 because it is 214.9636 away (can't see). [TrackMoreMobs] Now adding Ancient Bonestalker (600) at {303, 772}. [TrackMoreMobs] Now adding Ancient Bonestalker (599) at {304, 752}. [TrackMoreMobs] Now adding Ancient Bonestalker (597) at {311, 791}. [TrackMoreMobs] Now adding Shambling Cadaver (566) at {302, 529}. [TrackMoreMobs] Now adding Shambling Cadaver (572) at {309, 551}. [TrackMoreMobs] Now adding Shambling Cadaver (564) at {289, 545}. [TrackMoreMobs] Now adding Shambling Cadaver (565) at {288, 535}. [TrackMoreMobs] Now adding Shambling Cadaver (569) at {295, 553}. [TrackMoreMobs] Now adding Shambling Cadaver (570) at {297, 542}. [TrackMoreMobs] Now adding Shambling Cadaver (567) at {285, 525}. [TrackMoreMobs] Now adding Ancient Bonestalker (593) at {291, 752}. [TrackMoreMobs] Now adding Ancient Bonestalker (596) at {279, 771}. [TrackMoreMobs] Now adding Ancient Bonestalker (595) at {296, 773}. [TrackMoreMobs] Now adding Ancient Bonestalker (598) at {281, 785}. [LatencyTracker] AverageLatency: 60 [OpenChestTask (Leash -1)] The current chest to open is [443] Chest at {398, 531}. We have been on this task for 00:00:00.9157700 and have been attempting to interact for 00:00:00. [OpenChestTask (Leash -1)] Now moving towards the chest 443 because it is 176.4753 away (can't see). [LatencyTracker] HighestLatency: 105 [TrackMoreMobs] Now adding Shambling Cadaver (568) at {273, 539}. [TrackMoreMobs] Now adding Shambling Cadaver (571) at {271, 545}. [TrackMoreMobs] Now adding Shambling Cadaver (573) at {272, 564}. [TrackMoreMobs] Now adding Ancient Bonestalker (594) at {271, 780}. [TrackMoreMobs] Now removing 609. [TrackMoreMobs] Now removing 607. [LatencyTracker] HighestLatency: 109 [TrackMoreMobs] Now removing 606. [TrackMoreMobs] Now removing 608. [LatencyTracker] HighestLatency: 57 [LatencyTracker] HighestLatency: 98 [TrackMoreMobs] Now removing 605. [LatencyTracker] AverageLatency: 64 [LatencyTracker] HighestLatency: 104 [LatencyTracker] HighestLatency: 106
Hey Tony, Doesn't look like it. I get this spammed every few seconds while running this one with FlaskHelper: 2015-09-04 06:27:49,891 [7] DEBUG CustomLogger (null) - [FlaskHelperRoutineInfos] Routine doesn't implement the GetCombatRange check in the Execute() part, QSF is Unusable ...
These settings are working well for me. It still leap slams more than I'd like, it keeps near 100% fort up by doing so though, so not completely terrible. NB: For those we recently installed this, if you have the issue of the bot stopping for a second or so after it finishes cycloning before it tries to again, these settings above fixed it for me, so give it a go. Toze does suggest to leave Cyclone Target Range less than Cyclone Range, but it seems making it larger works better, at least for me.
When i start bot i got this error: Exception during routine Tick.System.NullReferenceException: Object reference not set to an instance of an object. at Typhonis.Typhonis.Tick() in c:\bot2\Routines\Typhonis\Typhonis.cs:line 486 at Loki.Bot.RoutineManager.Tick(IRoutine routine)
