1. A description of the suggestion

/*
 * Called before the break manager kicks in
 */
public void onBreak();

2. How will this suggestion impact scripters and/or botters?

 

Lots of people have been complaining that if the break manager wants to take a break and the script is in combat, it would die because the script stops but even after dying the bot won't log out because it was in combat and couldn't log out when it wanted to. There is no general solution to "taking a break" that won't affect the script context but scripters can implement their own, so for example a script that collects mort myre fungi will first go to a safe zone where it can't be attacked by ghasts and will wait until it's out of combat, and then it will take a break. There are many other situations where this would be useful such as interfaces that prevent the bot from logging out, cutscenes, being underwater, etc. which can be handled at script level

 

3. Post any examples such as code or pictures to supplement your description (optional) Non-graphical suggestion

 

The problem with this is that eventually at least one scripter will prevent the break from executing. I try and minimize any client setting/configuration that can be modified by scripters. Break Manager specifically was getting overriden by popular scripters and botters consistently spammed this forum with breaks not working. 

 

TLDR:

You can currently grab time until next break, which should solve your issue. The return is time in minutes.