avid Posted December 4, 2017 Share Posted December 4, 2017 (edited) Hello all, thanks for reading! So, I am putting together a lil script that requires some custom obstacle handling. All fine and dandy, I got the handler written and if I let it run while I path manually, it blazes through the obstacle at breakneck speeds! HOWEVER, if I use the setBreakCondition feature of WebWalkEvent the script takes a good 1-3 seconds before it even begins handling the obstacle. Script's current delays as set by me: onLoop(): 200 WebWalkEvent evt = new WebWalkEvent(targetArea); evt.setBreakCondition(new Condition() { @Override public boolean evaluate() { return dialogues.inDialogue(); } }); execute(evt); I figured it could be the dialogues.inDialogue(); check, but generally it is returning extremely quick (so I don't think it is causing the 1-3 second delay). Note this isn't a killer for the script, just very noticeable and slow. Anyone know what's up? Thanks in advance for your advice, Avid EDIT: Upon timing the delay, it's anywhere from 1-10 seconds. The ten second delays, seeming like forever! Edited December 4, 2017 by avid Quote Link to comment Share on other sites More sharing options...
avid Posted December 4, 2017 Author Share Posted December 4, 2017 bump Quote Link to comment Share on other sites More sharing options...
The Undefeated Posted December 8, 2017 Share Posted December 8, 2017 You're sure it's not something else? Your WebWalkEvent looks fine. Quote Link to comment Share on other sites More sharing options...
Juggles Posted December 8, 2017 Share Posted December 8, 2017 Check your whole script for an extra sleep. Its happened to me before and wasted an hour trying to fix a fake problem when all i needed to do was remove my sleep. Event code is fine, Nothing wrong with the event Quote Link to comment Share on other sites More sharing options...
d0zza Posted December 8, 2017 Share Posted December 8, 2017 Check the logger too, I feel like there might be positions in your area that the webwalker can’t reach and it’s looping until it finds a position it can reach. Quote Link to comment Share on other sites More sharing options...