Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Buy OSRS Gold

Sell OSRS Gold
  • 0
Encoded

What improvements would you like to see to the Break Handler?

Question

A few of you brought to attention the break handler in What's the thing you'd like to see the most? I would like to gather more feedback in regards to break handler improvements.
Please answer the following questions with as much detail as possible. If you feel like you can't express what you want to describe in words then consider drawing it and uploading a picture.

1. What do you like about the current break handler?

2. What do you dislike about the current break handler?

3. What specific improvements would you like to see be implemented into the break handler?

  • Like 1

Share this post


Link to post
Share on other sites

13 answers to this question

Recommended Posts

  • 1
5 hours ago, Enano25 said:

The ability to stop the script based on reaching a certain level or a certain amount of hours played also stop the script.

The certain amount of hours played can be sort of accomplished with the script queue. With the script queue you can cap the total runtime of a script, which should accomplish at least part of that.

While I don't have any real issues with the break handler, here's some things I've seen around the forums that may not have been mentioned here:

  • Easier repetition of entire profiles
  • Some form of a simple built in walkthrough on how to create a break profile. People find the current handler confusing, and often threads with questions about it. It'd be cool to curb that a bit
  • An option to allow breaks to occur relative to each other instead of simply relative to the script runtime.

Share this post


Link to post
Share on other sites
  • 0

1. I like that it allows users to have multiple break patterns at once. We can have one repeated break pattern going, and a single-time break going at the same time.

2a. I don't like the fact it's been bug ridden for several months. Every time a break fires, there's a chance it gets stuck unable to login after break ends. The latest iteration of this bug ignores Script Queue, so there's no way for users to work around this. Today, every account needs constant manual monitoring - it's awful. The other alternative is not using breaks at all, which has it's own downsides.

2c. Could be script related, but some scripts continue performing actions while on break. That's reflected in Debug logs, and mouse sometimes moves on screen while account is offline. This happens with Tri Combat Aio, and sometimes with other other scripts.

3. Fixing bot breaking bugs is TOP priority.

A great addition would be a way to start breaks depending on time of the day. I.e. "12:00CET +-1h fire 10min break". The time can be taken from local PC clock.

Share this post


Link to post
Share on other sites
  • 0
2 hours ago, gef30 said:

Meh delay this. scripters can just add their own custom break handlers, for anti ban and more flexibility. in my opinion the breakhandler is completely redundant!

??? Yeah let’s make 20 different break handlers instead of one for the client.. genius plan.

Share this post


Link to post
Share on other sites
  • 0

1. I love how we can add in manual breaks.

2. I'm unsure if we can do this or not but I don't like how we can't have the break handler log our accounts out at a certain amount of hours played and then log in select other accounts in for another certain amount of hours.

3. Implement question #2 here. I think it would so convenient if we could do that and not have to worry about anything. I am aware that we can use TeamViewer but it still would be very convenient.

Thank you for posting this and asking for our input! ❤️

Share this post


Link to post
Share on other sites
  • -1

The way the breaks are added could be improved so the breaks won't be able to overlap if the user chooses such option. In this example the second break would not fire because it overlaps with the first break.

It would be great if the counter would reset after each break. In this example 8 minutes after the first break would start a 5 minute long second break.

I hope you get it what I want to say. :D

Capture.PNG.9e9b75233ce6be7ff7367500e456bdf7.PNG

 

Edited by reanox

Share this post


Link to post
Share on other sites
  • -2

 

 

I think the system should be reworked entirely. Maybe retaining it as an alternative to the new break handler. I just feel like it could be done a lot smarter than it currently is. Maybe your profile should be assigned an ABC-Breaking value, that determines exactly how your profile breaks, then maybe a slider to select modifier, as in how much you want to break, 1  being very generous breaks, and 5 being no breaks at all. 

So there'd be 5 default breaking profiles to choose from, which act as modifiers to your ABC-Breaking value. The ABC-Breaking value would just contain various randomized settings for how your bot breaks, like does it favour small breaks or big breaks, does it break a lot or a little? Quantity vs quality kind of stuff. Then maybe the user could input how long they plan to bot for, and the break handler would just tailor breaking to that variable.  

 

 

 

Share this post


Link to post
Share on other sites
  • -2
15 hours ago, HeyImJamie said:

??? Yeah let’s make 20 different break handlers instead of one for the client.. genius plan.

Yeah it actually is, lets look at it from an antiban perspective, you as as a scripter should know that you can generate profiles based on certain factors that users can choose or auto generate. Lets say you want to incorporate break profiles which perfectly fit the profile of a specific user, that is currently only possible with custom break handlers. Since the break handler doesn't do this, it will just break whenever the timer hits, ignoring whatever is happening at that time.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Our picks

    • Hi everyone,

      I'd like to thank everyone for their patience in this transition period. Since last week, we've worked out the remaining bugs with this integration.

      Some users have still been having issues with connecting their forums account to their Auth0 account. To resolve this, we've imported all forums accounts into Auth0.

      Unfortunately, the accounts which were imported today were using an unsupported password hashing algorithm. Hence, random passwords were set during the import.

      What does this mean for me?

      If you've previously linked your forums account to your Auth0 account, you don't have to do anything. Nothing changes for you.


      If you haven't logged in via our new login yet,

      Try logging in with your forums email address and the last password you used


      If you are unable to login, please use the "Forgot password" tool on the login page:
      Follow the instructions to reset your password
       
        • Like
      • 1 reply
    • Hello everyone,

      Last week we tried to roll out Auth0 Login, but we lost that battle. Now it's time to win the war!

      Important changes

      When logging into the client, you'll now have to enter your Auth0 account credentials instead of your forums credentials

      Note: 2FA is still handled through your forums account (for the time being)



      Changes for existing users

      You'll have to link your Auth0 account to your forums account here: https://tribot.org/forums/settings/login/?service=11


      Auth0 accounts have been created for most existing users. Please use your forums email address and password to login.



      Important notes

      Make sure to verify your email address upon creating a new Auth0 account


      When we mention your Auth0 account, we mean your account used for auth.tribot.org as displayed below
      • 71 replies
    • To better support the upcoming changes (TRiBot X, new repository), we're switching our login handler to Auth0. Instead of logging in with the standard form, you'll now be required to login through our Auth0 application.

      All existing accounts which have been used within approximately the past year have been imported into Auth0 using the same email and password combination which has been stored on the forums.

      What does this mean for users?

      Your account credentials are now even more securely stored


      You'll be able to login via Facebook, Google, and others in the future


      Is there anything users have to do differently now?

      Existing users: You'll have to login with the standard login, open your Account Settings, then link your Auth0 account


      New users: You'll be redirected to our Auth0 app (auth.tribot.org) where you'll be able to create an account


      Why was this change made?

      The new apps we are creating (such as the new repository) aren't able to use the forums to handle user logins


      To centralize all user accounts in one area


      To ensure that the client login doesn't go down when the forums are having problems


      To speed up our development


      Other considerations

      There's no documentation or official support for using Invision Community combined with Auth0, so there are still a few kinks we're working out


      We're in the works of creating an account management panel specifically for Auth0 accounts (ETA August)


      It's not possible to change email addresses for the time being (this will be resolved this August)


      Changing passwords is a weird process for the time being. To change your password, you'll have to use the "Don't remember your password" tool on the Auth0 login page
        • Like
      • 11 replies
    • Over the past month, we've been working hard on TRiBot's new repository - a much needed update. This change has been deemed necessary for TRiBot X, and will allow us to really speed up development of all aspects of TRiBot.

      Today we are going to share what we've been working on!


      Now you must be wondering what kind of features the new repository will have.... well, you'll have to be patient for a little while longer. We're still figuring out various technical aspects so we can't provide answers to all possible questions. We're also focusing on development rather than writing about it so that everyone can get access to our latest developments at lightning speed. I will however answer a few users' questions.

      We're planning on a release of this early to mid August, giving users some goodies before TRiBot X's release.

      Thank you all for being patient. I hope everyone is excited as much as I am!
        • Like
      • 17 replies
    • Over the past few months, I’ve been working diligently on a new project - TRiBot X. Everything has been written from the ground up, with all of the best practices of software engineering. Every aspect of TRiBot has been re-imagined to support three main goals: flexibility, useability, and reliability.
        • Like
      • 50 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...