DreamBot 2.9.9 version bug with banking

[Dollar99 9]

44 minutes ago, Man16 said:

If you have this problem or any widget related problem (some of my users for one of my scripts had the problem and this solved it), go delete the following file: C:\Users\USERNAME\DreamBot\BotData\client.jar

Then run the launcher (DBLauncher.jar) to get the client back and all problems should be fixed.

Edit: Sometimes it breaks again and only works the first time the client is downloaded. If this happens to you, skip using the launcher and run just the client.

just tryed that trick didint help me out 😕

[oh_my_goth 41]

Was having this issue myself about 13 hrs ago.  In the brief moments I saw the bots, I also saw it trying to do it while using a furnace.

Bank scenario- Opens bank, doesn't recognize it's open, keeps trying to open via npc/booth(unable to as banks already open), I can manually close the bank, & the bot would recognize bots closed, try again, & everything works "normal"  afterwords, it wouldn't read the proper widget for banks open while bank was open.

Furnace scenario- Opens widget interface, still tries to interact with furnace, it wouldn't read the proper widget for interface open while interface was open..  Same idea, close manually, it resets as if nothing was wrong to begin with.

It seems to ignore certain widgets at certain random times.  As said above, it doesn't always happen. Maybe 1/30-1/40 banks, but it did eventually happen. 

I just checked most of my bots, & the proggies seem normal, & saw no issues running at all. Can't confirm it still happens, but can confirm it once did.  Seemed very random, but worrisome ban-wise.  

Try not to interrupt your bot to re-run/change script, that's where my issues began. Set up your bot, walk off for a couple hours & do something else.  Helps die down the anxiety, & maybe it cleared itself up with time, like it did for me? Good luck.

[Dollar99 9]

12 minutes ago, oh_my_goth said:

Was having this issue myself about 13 hrs ago.  In the brief moments I saw the bots, I also saw it trying to do it while using a furnace.

Bank scenario- Opens bank, doesn't recognize it's open, keeps trying to open via npc/booth(unable to as banks already open), I can manually close the bank, & the bot would recognize bots closed, try again, & everything works "normal"  afterwords, it wouldn't read the proper widget for banks open while bank was open.

Furnace scenario- Opens widget interface, still tries to interact with furnace, it wouldn't read the proper widget for interface open while interface was open..  Same idea, close manually, it resets as if nothing was wrong to begin with.

It seems to ignore certain widgets at certain random times.  As said above, it doesn't always happen. Maybe 1/30-1/40 banks, but it did eventually happen. 

I just checked most of my bots, & the proggies seem normal, & saw no issues running at all. Can't confirm it still happens, but can confirm it once did.  Seemed very random, but worrisome ban-wise.  

Try not to interrupt your bot to re-run/change script, that's where my issues began. Set up your bot, walk off for a couple hours & do something else.  Helps die down the anxiety, & maybe it cleared itself up with time, like it did for me? Good luck.

You explained very good, so its client problems, thank you for information

[Defiled 423]

7 hours ago, Infidel said:

Not experiencing any of these issues reported. Banking is working fine in my tests.

Tested;

        getBank().close(); //Working.
        getBank().deposit("Coin"); //Working
        getBank().depositAllExcept("Iron axe"); //Working
        getBank().depositAllItems(); //Working
        getBank().depositAllEquipment(); //Working

Suspecting users scripts are are at fault. Probably using a sleep() and possibly getting lag while banking. instead of getBank().isOpen checks.

It is possible that it is caused by lags or items not found in the bank.

As they say that it keeps depositing All items.. this points to a problem where it keeps looping getBank().depositAllItems() cuz it faces an obstacle with the lines after it..

like for an example..

if(!getInventory().contains(995)) {

if(!getBank().isOpen()) {

getBank().openClosest();

} else {

getBank().depositAllItems();

getBank().withdrawAll(995);

}

^ If coins weren't in the bank.. itd keep depositing all items in the bank.. 

thats why in all scripts there should be a check in every step.

OR they may have executed that if the bank is open do the stuff ^ and they didn't close the bank.. so many possibilities.. 

I guess the script writer has to check over the script because I'm not encountering this problem 

[BrownK1d 4]

7 hours ago, Man16 said:

If you have this problem or any widget related problem (some of my users for one of my scripts had the problem and this solved it), go delete the following file: C:\Users\USERNAME\DreamBot\BotData\client.jar

Then run the launcher (DBLauncher.jar) to get the client back and all problems should be fixed.

Edit: Sometimes it breaks again and only works the first time the client is downloaded. If this happens to you, skip using the launcher and run just the client.

 

This didn't work for me either. I have a jug filler, this script needs to go to deposit many times and I can't use them if they keep sticking. It needs to be solved

[Dollar99 9]

its client problems not scripter jesus christ in last version it was perfect now it has bugged.....

[Manly 879]

1 hour ago, Dollar99 said:

its client problems not scripter jesus christ in last version it was perfect now it has bugged.....

Ye this is correct.

[just4show 10]

On 1/6/2020 at 2:12 PM, Man16 said:

If you have this problem or any widget related problem (some of my users for one of my scripts had the problem and this solved it), go delete the following file: C:\Users\USERNAME\DreamBot\BotData\client.jar

Then run the launcher (DBLauncher.jar) to get the client back and all problems should be fixed.

Edit: Sometimes it breaks again and only works the first time the client is downloaded. If this happens to you, skip using the launcher and run just the client.

This worked for me