Jump to content

'Custom' Break


Recommended Posts

Posted
1 minute ago, Eagle Scripts said:

You can use your own LoginHandler, or play around with pausing and resuming the scriptExecutor.

I'd advise to just go with the LoginHandler solution though. Bear in mind that you'll have the disable all randoms through CLI for this :D

 

 

Thought I'd have to do as much. :P Thanks :)

Posted
10 minutes ago, Alek said:

Settings->Options and adjust the break values. It says "how long should stay logged out for before logging back in", which is what you are asking. 

Nope. I want the script to run as normal at certain hours of the day but cease to run at times I've selected which with the current break handler, I don't think is possible.

Posted (edited)
2 minutes ago, Alek said:

To Explv's or mine? I just tested the default OSBot one on the latest dev build lol.

Oh Explv's. YOURS IS FLAWLESS <3 

 

I've only experienced bugs with the built in one (maybe once every other week over a LOT of testing) when I've either started / stopped a script weirdly during the auto login (or it gets an NPE during auto login) or I start / Stop a script like a trillion times sometimes it acts funny.

Edited by k9thebeast
Posted
1 hour ago, k9thebeast said:

Oh Explv's. YOURS IS FLAWLESS <3 

 

I've only experienced bugs with the built in one (maybe once every other week over a LOT of testing) when I've either started / stopped a script weirdly during the auto login (or it gets an NPE during auto login) or I start / Stop a script like a trillion times sometimes it acts funny.

I think its an issue when you stop a script which throws an InterruptedException or gets caught in some sort of loop. I mean the way to fix this is to have scripters check to see if the script is stopped during all states, then breaking out of whatever they have if it is. Chances of this happening is not very likely at all though haha.

  • Like 1
Posted (edited)
11 minutes ago, Explv said:

Such as?

Two main things that I've changed in mine are a conditional sleep to tell the client is loaded before actually trying to log in (the default one throws NPE if applet isnt fully loaded)

Somethings off with the onResponseCode(), havent delved too far into it but it doesnt activate everytime when there is a response code other than a successful login of course. Remedied this by just overiding it within my main.java which works fine.

Edited by k9thebeast

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...