Jump to content
  • 0

Break Handler Acting Funny?


Hello everyone,

So, I'm trying to get a good session setup with the break handler. (This is not actually what my break is going to be)

I attached my break.

So what I assume here with my break is that first it will play for 2 hrs +- 45 minutes and break for 45 minutes +- 5:45

Then it should log back in play for 1 hour and 35 minutes +- 25 minutes and then break for 10 hours.

What has been happening - Sometimes it starts off with the 1 hour and 35 minutes on and 10 hours off when I want it to start with 2 hours on and 45 minutes off. OR it works correctly and starts with the 2 hours on and 45 minutes off. So basically it seems to be switching? Is there a order to which will go first? Is it random? I'm kind of confused I've been testing this a bit.

Anything helps!




Link to post
Share on other sites

4 answers to this question

Recommended Posts

  • 0

Your breaks overlap with their randomness, so one might activate before the other. You need to consider the time spent breaking when adding multiple break timers.

For example. If i had 2 breaks:

After 1 HR, break  12 hours.

After 13 hours, break  12 hours.

This would: Run for 1 hr. Break for 12 hours. Come back at 13 hours, instantly break again for 12 hours.

Runtime still keeps counting up while you're on break

Link to post
Share on other sites
  • 0

@Adventure_Time So your saying "Runtime" means it will take a break after the script has been running "4 hours". So set runtime to 4 hours and have it break for 30 minutes.So now run time is sitting at a total of 4 hours and 30 minutes after the first break.

So if I set runtime to 5 hours and 15 minutes. It will login after the first break and run for another 45 minutes until it hits a total runtime of 5 hours and 15 minutes? Then I set it to break for 10 hours.(Edit - Actually it should only break for 4 hours and 45 minutes until it hits a run time of 10 hours?)

This look right?


Edited by Mellen
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.

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

    • What to expect from TRiBot moving forward.
        • Thanks
        • Like
      • 10 replies
    • TRiBot 12 Release Candidate

      The TRiBot team has been hard at work creating the last major version of TRiBot before the TRiBot X release. We've noticed many problems with TRiBot 11 with a lot of users preferring TRiBot 10 over 11. We've heard you, so we took TRiBot 10, added the new features introduced with 11, introduced some other new things, and created TRiBot 12. So without further adieu, here's TRiBot 12.
        • Sad
        • Like
      • 39 replies
    • Gradle is a build tool used to accelerate developer productivity.

      We recently setup a Maven repository (TRiBot Central) to make it easier for scripters to create scripts. Check it out here: https://gitlab.com/trilez-software/tribot/tribot-central/-/packages

      Furthermore, we've released a simple Gradle project to make it easy to run TRiBot and develop scripts for it. Check it out here: https://gitlab.com/trilez-software/tribot/tribot-gradle-launcher

      The goals of TRiBot Central are to:

      Deliver updates to TRiBot faster

      Better organize TRiBot's dependencies (AKA dependancies)

      Make it easier to develop scripts for TRiBot

      Make it easier to use and run TRiBot

      Note: TRiBot won't be able to run scripts from within this project until TRiBot's next release.
        • Like
      • 13 replies
    • 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
        • thonking
        • Like
      • 17 replies
    • 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
      • 81 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...