[dahnae]

will give it a shot and report back if any errors
 
Seems i got that watchdog sorted, only other question i have now is does the coal bag need to be inventory to work? as bot doesnt current use it if its in the bank TIA

https://puu.sh/HEDGY/6966cf744e.png

It should withdraw the coal bag, but I haven't tested that feature in a while. Having it in your inventory already is best.

 

[delta squad]

It should withdraw the coal bag, but I haven't tested that feature in a while. Having it in your inventory already is best.

Bot seems to put the bag in the bank and withdraw coal when its in the inventory, and doesn't use it when its in the bank, other than that it seems to work great

 

[dahnae]

Bot seems to put the bag in the bank and withdraw coal when its in the inventory, and doesn't use it when its in the bank, other than that it seems to work great

That is very weird, I just tested it and it worked fine. Can you send me your log files via DM?
 
To anyone wondering, it was caused by the coal bag being open, which changes the item name from "Coal bag" to "Open coal bag". Simply closing the bag fixed the issue.

 

[delta squad]

So after getting it all sorted, bot runs great, heres a little proggie update

 

[cptyusuf]

Hi Dahn, could you please assist with an issue I'm having with my Coal bag. The script fills the coal bag at the bank chest and then proceeds to fill it again at the conveyer belt. Hence observing message. Please refer to debug log below for more information. Already performed trivial workarounds, clear cache etc.



DEBUG LOG
00:05:03 WARN Empty coal bag has timed out
00:05:03 DEBUG Action Empty coal bag was cancelled
00:05:04 DEBUG Hovered SpriteItem(name:Coal bag, quantity: 1, index: 0, origin: INVENTORY) on the first attempt.
00:05:04 DEBUG MenuInteractionEvent[action='Fill', target='Fill', param0=12019, param1=0, param2=9764864, opcode=33, type=sprite Grid, mouseX=578, mouseY=229, targetEntity=SpriteItem(name:Coal bag, quantity: 1, index: 0, origin: INVENTORY)]
00:05:04 DEBUG Attempting to hover InteractablePoint(263, 153) since the target of InteractablePoint(263, 153) is less then 4 pixels away.
00:05:04 DEBUG Attempted to hover InteractablePoint(263, 153) since InteractablePoint(263, 153) was less than 4 pixels away (success: true)
00:05:05 DEBUG Attempting to hover InteractablePoint(263, 171) since the target of InteractablePoint(263, 171) is less then 4 pixels away.
00:05:05 DEBUG Attempted to hover InteractablePoint(263, 171) since InteractablePoint(263, 171) was less than 4 pixels away (success: true)
00:05:05 INFO Executing task "Put ores on conveyor"
00:05:05 DEBUG Attempting to hover InteractablePoint(275, 162) since the target of InteractablePoint(275, 162) is less then 4 pixels away.
00:05:06 DEBUG Attempted to hover InteractablePoint(275, 162) since InteractablePoint(275, 162) was less than 4 pixels away (success: true)
00:05:06 WARN Empty coal bag has timed out
00:05:06 DEBUG Action Empty coal bag was cancelled
00:05:06 DEBUG Hovered SpriteItem(name:Coal bag, quantity: 1, index: 0, origin: INVENTORY) on the first attempt.
00:05:06 DEBUG MenuInteractionEvent[action='Fill', target='Fill', param0=12019, param1=0, param2=9764864, opcode=33, type=sprite Grid, mouseX=574, mouseY=226, targetEntity=SpriteItem(name:Coal bag, quantity: 1, index: 0, origin: INVENTORY)]
00:05:06 DEBUG Attempting to hover InteractablePoint(272, 164) since the target of InteractablePoint(272, 164) is less then 4 pixels away.
00:05:06 DEBUG Attempted to hover InteractablePoint(272, 164) since InteractablePoint(272, 164) was less than 4 pixels away (success: true)
00:05:06 INFO Bot was paused by user

 

[dahnae]

Hi Dahn, could you please assist with an issue I'm having with my Coal bag. The script fills the coal bag at the bank chest and then proceeds to fill it again at the conveyer belt. Hence observing message. Please refer to debug log below for more information. Already performed trivial workarounds, clear cache etc.

View attachment 11210

DEBUG LOG
00:05:03 WARN Empty coal bag has timed out
00:05:03 DEBUG Action Empty coal bag was cancelled
00:05:04 DEBUG Hovered SpriteItem(name:Coal bag, quantity: 1, index: 0, origin: INVENTORY) on the first attempt.
00:05:04 DEBUG MenuInteractionEvent[action='Fill', target='Fill', param0=12019, param1=0, param2=9764864, opcode=33, type=sprite Grid, mouseX=578, mouseY=229, targetEntity=SpriteItem(name:Coal bag, quantity: 1, index: 0, origin: INVENTORY)]
00:05:04 DEBUG Attempting to hover InteractablePoint(263, 153) since the target of InteractablePoint(263, 153) is less then 4 pixels away.
00:05:04 DEBUG Attempted to hover InteractablePoint(263, 153) since InteractablePoint(263, 153) was less than 4 pixels away (success: true)
00:05:05 DEBUG Attempting to hover InteractablePoint(263, 171) since the target of InteractablePoint(263, 171) is less then 4 pixels away.
00:05:05 DEBUG Attempted to hover InteractablePoint(263, 171) since InteractablePoint(263, 171) was less than 4 pixels away (success: true)
00:05:05 INFO Executing task "Put ores on conveyor"
00:05:05 DEBUG Attempting to hover InteractablePoint(275, 162) since the target of InteractablePoint(275, 162) is less then 4 pixels away.
00:05:06 DEBUG Attempted to hover InteractablePoint(275, 162) since InteractablePoint(275, 162) was less than 4 pixels away (success: true)
00:05:06 WARN Empty coal bag has timed out
00:05:06 DEBUG Action Empty coal bag was cancelled
00:05:06 DEBUG Hovered SpriteItem(name:Coal bag, quantity: 1, index: 0, origin: INVENTORY) on the first attempt.
00:05:06 DEBUG MenuInteractionEvent[action='Fill', target='Fill', param0=12019, param1=0, param2=9764864, opcode=33, type=sprite Grid, mouseX=574, mouseY=226, targetEntity=SpriteItem(name:Coal bag, quantity: 1, index: 0, origin: INVENTORY)]
00:05:06 DEBUG Attempting to hover InteractablePoint(272, 164) since the target of InteractablePoint(272, 164) is less then 4 pixels away.
00:05:06 DEBUG Attempted to hover InteractablePoint(272, 164) since InteractablePoint(272, 164) was less than 4 pixels away (success: true)
00:05:06 INFO Bot was paused by user

You have to enable "Shift-click to drop" in your osrs settings
 
I've added a check for it. In the next update, it will always right-click to empty if the shift-click to drop setting is disabled.

 

[cptyusuf]

You have to enable "Shift-click to drop" in your osrs settings
 
I've added a check for it. In the next update, it will always right-click to empty if the shift-click to drop setting is disabled.

Thanks Dahn. It appears one of the accounts it was disabled.

 

[dahnae]

dahnae updated Dan Blast Furnace Beta with a new update entry:

Dan Blast Furnace Beta v1.1.4 Released!

Dan Blast Furnace Beta updated to v1.1.4.

• Bot will no longer use potions if disabled in settings
• Bot will now automatically activate run
• Fixed a bug that happened when ore in bank was at exactly the amount of empty inventory slots
• Added support for an open coal bag
• If shift-click to drop is disabled, bot will right-click the coal bag, regardless of playersense

Read the rest of this update entry...

 

[delta squad]

I used this bot from 65-80 smithing, but i flew too close to the sun, i just got a 2 day ban, i 100% believe it was my own fault as i was doing, 2, 2 hour sessions a day for the last week and a half with no breaks, make sure you use breaks people bot has been working great tho

 

[dahnae]

I used this bot from 65-80 smithing, but i flew too close to the sun, i just got a 2 day ban, i 100% believe it was my own fault as i was doing, 2, 2 hour sessions a day for the last week and a half with no breaks, make sure you use breaks people bot has been working great tho

Sorry for your ban Just out of curiosity, were you on resizable of fixed mode?

 

[delta squad]

Sorry for your ban Just out of curiosity, were you on resizable of fixed mode?

i was using fixed classic, as i couldnt get the bot to work in other modes.

edit- i can send you my last couple logs if you want to look through them to see if anything triggered, but i 100% believe its because i did nothing else on the account, and did the exact same amount of bars each session.

 

[dahnae]

i was using fixed classic, as i couldnt get the bot to work in other modes.

edit- i can send you my last couple logs if you want to look through them to see if anything triggered, but i 100% believe its because i did nothing else on the account, and did the exact same amount of bars each session.

Yea, your botting behavior probably played a big role in the ban. However, I have a slight suspiscion that fixed mode might also play a role in this, but I have no proof, other than the fact that all the bans I've heard of were on fixed mode (all 2-day bans btw).

No need for the logs, there's an anti-glitch in the bot. If it had gotten stuck or something, you would have noticed the bot stopping before it was done.
 
Btw, I've added some more info regarding resizable mode in the bot Overview, I've shown examples of incorrect camera angles / window size.

 

[delta squad]

Yea, your botting behavior probably played a big role in the ban. However, I have a slight suspiscion that fixed mode might also play a role in this, but I have no proof, other than the fact that all the bans I've heard of were on fixed mode (all 2-day bans btw).

No need for the logs, there's an anti-glitch in the bot. If it had gotten stuck or something, you would have noticed the bot stopping before it was done.
 
Btw, I've added some more info regarding resizable mode in the bot Overview, I've shown examples of incorrect camera angles / window size.

Sounds good, its a throwaway account anyways, i'll let it rest for a week or two and try it again

 

[bobzoc]

In your opinion, what do you think optimal break usage is? Take a break every hour? I know its a subjective and guess-like question. Just looking for an opinion.

Otherwise great work! Glad to see a blast furnace bot on the market.

 

[dahnae]

I've been using the default breaks 5-10-15:15-30-45, but I really have no idea of what's best. Been botting like this 2-3 hours a week, ~5 days a week for a month now on an account with a temp ban and it's still going strong.

 

[bobzoc]

Ah, I meant more along the lines of going x hours then breaking, (ex: 1 hour of botting then taking a break).

 

[dahnae]

Ah, I meant more along the lines of going x hours then breaking, (ex: 1 hour of botting then taking a break).

I usually bot for ~2-3h sessions (including breaks), once a day, sometimes with a shorter session later in the day. But I don't have a big sample size, I only bot on two accounts.

 

[dahnae]

dahnae updated Dan Blast Furnace Beta with a new update entry:

Dan Blast Furnace v1.1.5 Released!

Dan Blast Furnace updated to v1.1.5.

• Removed "Beta" from the name. This bot has been out long enough and is stable enough. It will go premium once it gets used more than 100 hours per day, on average.
• Fixed the item icons not being displayed in the progress tab
• Fixed some rare bug that would cause the bot to crash whe napplying settings
• Clarified that the mouse overlay is for windows only and made sure it doesn't crash the bot when enabled on other OS (linux or MAC)

Read the rest of this update entry...

 

[hit my gong]

Hey mate. Sorry to hear about your perm :-:

Bot is working well for me if i use just an hour or two a day.

I was wondering if you were thinking of adding the option for buying coal from the shop there when doing mithril? >

Cheers

 

[dahnae]

Hey mate. Sorry to hear about your perm :-:

Bot is working well for me if i use just an hour or two a day.

I was wondering if you were thinking of adding the option for buying coal from the shop there when doing mithril? >

Cheers

Thanks, the account was just a smithing alt, so no biggie. And no, I don't think this bot will ever support buying from Ordan (definitely not in the near future).