Ajdeathgiver Posted May 12, 2016 Posted May 12, 2016 thx I'll take a look at this issue, what areas are you using? All upstairs ones? is there any error in the console? All the upstairs ones, yeh, I've tried selecting just one of each, two, and all three and same issue arises.
Khaleesi Posted May 12, 2016 Author Posted May 12, 2016 All the upstairs ones, yeh, I've tried selecting just one of each, two, and all three and same issue arises. ok thx for the info, any idea about errors in the console?
Ajdeathgiver Posted May 12, 2016 Posted May 12, 2016 ok thx for the info, any idea about errors in the console? Can you tell me what to look for and such?
Khaleesi Posted May 12, 2016 Author Posted May 12, 2016 Can you tell me what to look for and such? if you click "settings" -> show logger you can see some of the logs. Sometimes an error pops up in there
LacielPvE Posted May 14, 2016 Posted May 14, 2016 Can I get a trial? I've been doing motherlode manually for a while now
bobsagheer Posted May 17, 2016 Posted May 17, 2016 (edited) I've had the stuck before climbing ladder bug, there are no bugs in console, but your webwalking event terminates and then attempts to start again in the same spot over and over again, which causes the bug. I've noticed this occurring on x:3755, y:5672. There may be other positions that it happens in, but at least here the webwalk event does not stop looping. Thanks for the script! Edit, just produced the bug again in x:3753, y:5673, x:3754, y:5673, x:3754, y:5672, x:3756, y:5672. Not sure about any other places, just looks like you need to revise the webwalk break condition. Edited May 17, 2016 by bobsagheer
Khaleesi Posted May 18, 2016 Author Posted May 18, 2016 (edited) I've had the stuck before climbing ladder bug, there are no bugs in console, but your webwalking event terminates and then attempts to start again in the same spot over and over again, which causes the bug. I've noticed this occurring on x:3755, y:5672. There may be other positions that it happens in, but at least here the webwalk event does not stop looping. Thanks for the script! Edit, just produced the bug again in x:3753, y:5673, x:3754, y:5673, x:3754, y:5672, x:3756, y:5672. Not sure about any other places, just looks like you need to revise the webwalk break condition. I already fixed this issue, but the fix isn't online yet Should be online soon ^^ Thx for the report EDIT: Script updated to V1.06 & V1.07: - Ladder to upstairs is working properly again - Should be a failsafe when clicking veins through veins upstairs. - Updated mouse pointer, let me know how it looks! Let me know if you still have issues with the vines in V1.06 or V1.07 Update should be online soon! Khaleesi Edited May 18, 2016 by Khaleesi
hath Posted May 22, 2016 Posted May 22, 2016 Top floor isnt working, character stays stuck at the top of the ladder
Khaleesi Posted May 22, 2016 Author Posted May 22, 2016 Top floor isnt working, character stays stuck at the top of the ladder Any console log? Could you get me a printscreen whne it's stuck?
hath Posted May 24, 2016 Posted May 24, 2016 Any console log? Could you get me a printscreen whne it's stuck? Working well now, thanks 1
Just Nuts Posted May 27, 2016 Posted May 27, 2016 Ran using Random Locations, Avoid Other Players, and Anti-Ban. Script worked wonderfully. Avoid other player option seems to keep you from mining the same vein as someone else, not staying away from other white dots. Had a problem with a random solver where, after the random was dismissed, client kept trying to click the random that was not there. I stopped the script and re-started, but the problem persisted and was fixed by re-logging my account. I suspect this is a client problem and not on your end. tl;dr Great Script! 1
Khaleesi Posted June 4, 2016 Author Posted June 4, 2016 Ran using Random Locations, Avoid Other Players, and Anti-Ban. Script worked wonderfully. Avoid other player option seems to keep you from mining the same vein as someone else, not staying away from other white dots. Had a problem with a random solver where, after the random was dismissed, client kept trying to click the random that was not there. I stopped the script and re-started, but the problem persisted and was fixed by re-logging my account. I suspect this is a client problem and not on your end. tl;dr Great Script! Hmm thats weird, if it happends again with the random let me know. I'll take a look at the avoid players function Can I get a trial please? can i get trial ? thx Both done!
