[Stable] OSBot 2.6.6

[Patrick]

Hey,

 

Some more bug fixes in this release. There will probably be a dev build after this release instead of another stable.

 

API CHANGES:
- Added Quests#isAdventurePathTabActive()

FIXES:
- Fixed the issue where the quest tab couldn't be opened when adventure path was selected.
- Added deselecting a spell when trying to cast a different one.
- Fixed the issue with break manager randomly logging out when loading a new region.
- Updating webwalking data now works automatically when running via cli.

MISC:
- The breaks enabled checkbox status can now be saved by pressing the save button and automatically loads on client startup.
- Added the option to stop after breaking. This is also saved/loaded just like the breaks enabled option.
- Added '-breaksettings enabled:stop_after_break' cli arguments to override the saved setting. Example: '-breaksettings true:false' will enable breaks but not stop after breaking, '-breaksettings true:true' will breaks and stop after breaking. '-breaksettings false:false' won't break by default nor stop after breaking.
- Added some extra debug to the world hopper.
- Minor bug fixes.
 

 

- The OSBot Team

[ez11]

nice

[ProjectPact]

World hopping debug gonna come in clutch this release, I can feel it!  

[Vi X]

thanks Pat!

Edited December 1, 2020 by Vi X

[Heist]

Sweet

[Khaleesi]

noice!

[Trappa]

Good work guys 

[ukasz]

nice release ,,enable breaks'' is saved in new clients but breaks doesnt work  
anyone else have this problem ? or all in this topic post ,,nice'' ,,good work'' ,,sweet'' without test ? 
maybe doing something wrong but bots are not making breaks....

@Patrick

[BobBot]

Nice update!

[keeptheFaith]

thank you all

[Patrick]

9 hours ago, ukasz said:

nice release ,,enable breaks'' is saved in new clients but breaks doesnt work  
anyone else have this problem ? or all in this topic post ,,nice'' ,,good work'' ,,sweet'' without test ? 
maybe doing something wrong but bots are not making breaks....

@Patrick

Anything in the logger about the break handler? Maybe you can contact me on discord and we'll see if we can find the issue 

[Seriously]

Could you add mouse and keyboard input hotkeys back? It was so nice thing to have and I still keep pressing them and hoping it would work 

[Patrick]

1 hour ago, Seriously said:

Could you add mouse and keyboard input hotkeys back? It was so nice thing to have and I still keep pressing them and hoping it would work 

I was planning on adding more hotkeys like start/pause scripts. I can add these too whilest I'm at it

[botimusprime]

@Patrick

Yep, breaks 100% broken now. Nothing in the logger. Set it for 2-5 mins as well as 20-40. No breaks on either as well as no printing to logger.

This needs to be fixed ASAP, it basically broke osbot for any script without internal breaking.

The last issue had us logging in and out on every script start for a month but at least it was usable after. This is not usable, please dont let this one go on for long. Many scripts have no internal breaking and depend on this break manager.

The improvements to the break handler are nice in theory, but dont force us to use it in production when the old break handler worked fine...

Edited December 2, 2020 by botimusprime

[Patrick]

45 minutes ago, botimusprime said:

@Patrick

Yep, breaks 100% broken now. Nothing in the logger. Set it for 2-5 mins as well as 20-40. No breaks on either as well as no printing to logger.

This needs to be fixed ASAP, it basically broke osbot for any script without internal breaking.

The last issue had us logging in and out on every script start for a month but at least it was usable after. This is not usable, please dont let this one go on for long. Many scripts have no internal breaking and depend on this break manager.

The improvements to the break handler are nice in theory, but dont force us to use it in production when the old break handler worked fine...

https://gyazo.com/41d91fda0a3bbc381e1dd9a120edd9a0

Please show me some more info because it seems to be working for me. I will need your exact values and way of starting it to know where it's going wrong. And which script you might be using.