Hey Frost I've ran into a problem - the bot keeps getting stuck on checking the charges of the trident (it just keeps checking it even though it's charged). I never had this problem the past week, it began today so probably has to do with an update.

1 hour ago, Slay n Slay said:

Hey Frost I've ran into a problem - the bot keeps getting stuck on checking the charges of the trident (it just keeps checking it even though it's charged). I never had this problem the past week, it began today so probably has to do with an update.

Todays update did have some trident related changes (can be enchanted now). Can you check for me if the chatbox message when checking charges has changed? (Post or PM me the message)

EDIT: nvm I think I got it

Edited February 8, 20188 yr by FrostBug

39 minutes ago, FrostBug said:

Todays update did have some trident related changes (can be enchanted now). Can you check for me if the chatbox message when checking charges has changed? (Post or PM me the message)

EDIT: nvm I think I got it

it's still happening for me (tried restarting osbot/computer to see if it helps).

the message is "Your weapon has 1,234 charges."

1 hour ago, myOSBaccount said:

it's still happening for me (tried restarting osbot/computer to see if it helps).

the message is "Your weapon has 1,234 charges."

Yea, I pushed a fix, but a developer needs to update the SDN before changes are live.
Usually done once a day

i know the bot is currently broke with the trident, currently waiting. Ive been banking myself and still running the script, sometimes the bot keeps clicking the chest after its looted and not doing anything else but clicking the open chest. =o

just a quick one. when house tele out from barrows, it clicks house tele, teleports, but just before it, it clicks house tele again.

21 hours ago, FrostBug said:

Yea, I pushed a fix, but a developer needs to update the SDN before changes are live.
Usually done once a day

any idea when the update should take place? right now it's still stuck checking

Until then, if the maximum fire runes in ur bank is 4995 he will put that into charge, 999 and wont check it again : >

2 hours ago, ckibbi said:

Until then, if the maximum fire runes in ur bank is 4995 he will put that into charge, 999 and wont check it again : >

what does that even mean?

On 08/02/2018 at 6:32 PM, FrostBug said:

Yea, I pushed a fix, but a developer needs to update the SDN before changes are live.
Usually done once a day

Can you let us know when changes are live, if not already? Not on my PC atm to check

11 hours ago, wtf11 said:

what does that even mean?

If you put maximum 4995 fire runes into your bank which is equal with 999stacks into the staff.  and you put 999 stacks into ur staff aswell, and set the charge amount req. To recharge ur staff to 0 it wont keep checking ur charges of staff. ( you have to manually bank every 1998 charges shot via staff)

9 minutes ago, ckibbi said:

If you put maximum 4995 fire runes into your bank which is equal with 999stacks into the staff.  and you put 999 stacks into ur staff aswell, and set the charge amount req. To recharge ur staff to 0 it wont keep checking ur charges of staff. ( you have to manually bank every 1998 charges shot via staff)

WILL RUN FLAWLESSLY

@FrostBugso today i had a few issues happening.

when i first tried to run the script the first run went fine up until it opened the chest, then it just repeatedly tried opening it even after obtaining the loot (getting the message that the chest is empty over and over again). after starting over the script it hadn't happened again.

i noticed at some point that when trying to enter the last tomb that would lead to the tunnel it clicked on it a few times, then left and reentnered the tomb and worked fine.

when i wasn't checking it was apparently stuck without moving for 5 minutes so the script had stopped. then when i tried to start it up again it was stuck in a loop checking for charges like before.

Could i have a trial to test this out? i wanna buy it but wanna test how it works first

3 hours ago, myOSBaccount said:

@FrostBugso today i had a few issues happening.

when i first tried to run the script the first run went fine up until it opened the chest, then it just repeatedly tried opening it even after obtaining the loot (getting the message that the chest is empty over and over again). after starting over the script it hadn't happened again.

i noticed at some point that when trying to enter the last tomb that would lead to the tunnel it clicked on it a few times, then left and reentnered the tomb and worked fine.

when i wasn't checking it was apparently stuck without moving for 5 minutes so the script had stopped. then when i tried to start it up again it was stuck in a loop checking for charges like before.

Alright; I'll be doing extensive testing over the next couple of days in prep for next client release anyway, so I'll see what I can find.

The trident fix is live now for the record