well its not ruining your reputation, it's telling other ppl to take care with trading with a newer member. Just to stop ppl making new accs and scamming on them. But deffo could be wrong as i've never used the market xd
apa
close osbot, delete all files in your script directory, open osbot, reexport script, refresh scripts, voila!
apa
PS i'm glad I got you into scripting
hopefully things go well and good luck don't give up!
apa
Other bots have this system implemented too. It seems this optional addon was added within the last couple of days
This check ensures that you're not part of a botnet, and in order to pass the check you need to have javascript enabled on your browser
apa
1) I've just pushed an update (3.39) which will fix any issues you have with refreshing (hopefully!) Let me know if they continue (MAKE SURE YOU ARE RUNNING 3.39 BEFORE SAYING ANYHTING! )
2) Banking seems to be fine for me, it is able to withdraw a full inventory just fine... perhaps you calculated the potion amount + 2 runes for teleport + food was maybe 1 or 2 above 28?
3) am fixing this as we speak
cheers!
apa
EDIT:
Just pushed a nested update as part of 3.39 which will stop random things spinning around the screen (such as random solver screen, debug messages, adverts.
============================================================================================
UPDATE!
Version 3.39 changelog:
Fixed outstanding bugs with crab refreshing and by default the script will now always run south unless specified otherwise.
Added additional console log message to aid with the debugging process.
Stopped anything other than the cursor rotating around the screen.
Happy botting! Update should be live shortly (within the next few hours) when the script manager gets round to checking and publishing the source.
apa
Hey
I was doing testing last night and it was hard to test aggressive issues as it took forever for the crabs to loose aggro for just 1 test haha!
Please can you tell me your setup? whether you were using east or west or random, and whether you had cave aggro reset on or off. I just need this info so I can get to the bottom of this problem. This issue must have arised from the resent update I pushed with the cave resetting system!
apa