Jump to content

What Sleep Methods Are Interrupt-able by the client "Stop Script" button

Recommended Posts

Scripts.sleep(), general.sleep(), and ABCUtil.sleep() all seem to function relatively the same.  I would guess ABCUtil is the newest and it throws an InterruptedException, which I am assuming is thrown by the Stop Script button in the client..  Which one should we used for fixed sleeps? ABCUtil?

Share this post

Link to post
Share on other sites

If you want a completely fixed sleep, use General.sleep_definite as it ignores the sleep modifier (antiban). Otherwise, General.sleep will work fine. It will sleep for x miliseconds with a small randomization for antiban.

Read the docs for the sleep here:



ABCUtil#sleep should only be used for ABC related sleeps, as it is interruptable by the ABC thread in the event you're in combat or it needs to interrupt the sleep.

Script#sleep is the same as General#sleep (if you decompile tribot, that's what you will find out)




Script#sleep is same as General#sleep

Use General#sleep for sleeping purposes

Use ABC#sleep for reaction time sleeps only. They are interrupted by the abc2 thread

use Timing#waitCondition if you want the script to sleep until a specific condition has been reached

All sleeps will pretty much be stopped the moment you click stop script. Even if the script calls General.sleep(Long.MAX_VALUE), the script will pretty much be stopped immediately.

  • Like 1

Share this post

Link to post
Share on other sites

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

  • Our picks

    • This release will:

      Fix key event handling issue

      Fix other event handling issue

      Fix RSServer hook

      Update world hopper to have it use OCR, thanks to Todd

      Use proper disposal of old Graphics objects

      Reformat code

      Rearrange code

      Organize code imports

      Apply around 8000 automated code refactorings

      Make preparations for Java 9

      Fix 11 various bugs

      Add more reliable debugging support

      Fix mouseEntered/Exited event dispatching bug

      Fix minimap walking bug where it opens the map

      Fix broken hooks for today's game update
        • Thanks
        • Like
      • 86 replies
    • This update will:

      Fix GE inventory item positioning bug

      Fix broken object hooks
        • Like
      • 27 replies
    • This release will:

      Fix some ClosedChannelException bug

      Fix bug in RSObject#getAllTiles

      Add game tab support for "Kourend Favour"
        • Like
      • 15 replies
    • This release will:

      Fix Settings UI placement bug

      Fix game object location bug

      Fix small layout bug making the client shift up and down

      Fix client crashing bug where loading the client with a small display area will cause the client to crash

      Fix annoying Linux bug relating to painting events and peers

      Fix settings saving bug where settings are saved to disk more often than they should

      Fix RSInterface#isBeingDrawn bug affecting a limited amount of people

      Drop Java 1.7 bytecode version for 1.8

      Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).

      This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
        • Like
      • 40 replies
    • This update will:

      Fix the RSMenuNode bug which also fixes the bug with bank opening

      Fix the incorrect object positions bug

      Fix and re-enable the LG Objects API Accelerator

      Fix the RSObject#getAllTiles bug
        • Like
      • 22 replies
  • Recently Browsing   0 members

    No registered users viewing this page.