Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Sign in to follow this  

ABC2 Implementation

Recommended Posts

Hi Guys,


Im trying to implement ABC2 into a script and I'm having all sorts of problems.

EDIT: I saw someone on another post saying to multiply wait times by some sort of modifier. I'm currently using a value of 0.1 and it seems a lot nicer. I remember seeing something like this on one of the premium scripts...

1. There is an item that spawns every 30 seconds or so. When it appears, I call the abc sleep to simulate a reaction time. The data i input is the duration that has passed since the last spawn. Is this correct? I'm getting very large wait times here. Is it even worth using this reaction time for this event?


2. I have a task that takes around 2.5 seconds to complete. (Click on something, wait for trigger). ABC is generating very large sleeps sometimes, even around 6 seconds. No human takes 6 seconds to react, more like 0.2 seconds in this kind of scenario. Am I doing it wrong?

Here is a rough outline of what Im doing in the script

1. click on the object, generate trackers

2. start a timer

3. once the trigger occurs, stop the timer and add this value to the average wait times data

4. take average wait time data and use it to generate abc sleep:

		long averageWait = getAverageWait(activity);
		SUPER.print("Average wait time for activity [" + activity + "] is " + averageWait);
		final boolean menuOpen = m_abc.shouldOpenMenu() && m_abc.shouldHover();
		final boolean hovering = m_abc.shouldHover();
		final long hoverOp = hovering ? ABCUtil.OPTION_HOVERING : 0;
		final long menuOpenOp = menuOpen ? ABCUtil.OPTION_MENU_OPEN : 0;

		final int reactionTime = m_abc.generateReactionTime(m_abc.generateBitFlags((int)averageWait, hoverOp, menuOpenOp));
			SUPER.print("ABC2 Sleep [ " + activity + " ]: " + reactionTime + "ms");
		catch (final InterruptedException e)


Am I even doing this right? I'll be honest I'm having a hard time understanding the ABC2 tutorial...


Edited by botslave1

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.

Reply to this topic...

×   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.

Sign in to follow this  

  • Our picks

    • This release will:

      Fix prayers and world hopper API (Thanks @JoeDezzy1 and @erickho123)

      Improve banking API (Thanks @Encoded)

      Adds methods for returning and using Java Lists, rather than arrays

      Slightly randomizes some hardcoded behaviour

      Removes sleeps from waitConditions; the efficiency saving potential is negligible in these use-cases, therefore cleaner code is preferable

      Other back-end improvements

      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Sad
        • Haha
        • Thanks
        • Like
      • 85 replies
    • This release will:

      Add new internal framework for capturing exceptions

      Fix issue with not selecting the last column in world hopper (Thanks @Todd)

      Add a message about pin usage in Banking#openBank (Thanks @Todd)

      Disable the firewall by default (Thanks @Todd)

      Fix handling of the welcome screen after login (Thanks @Encoded)

      Fix wrong amount bank withdrawal (Thanks @Encoded)

      Fix Screen#isInViewport

      Fix Game#isInViewport (Thanks @Encoded)

      Call onBreakEnd for ListenerManager Breaking Listeners (Thanks @Encoded)

      Fix Prayer#getPrayerPoints NumberFormatException (Thanks @JoeDezzy1)

      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Thanks
        • Like
      • 28 replies
    • This release will:

      Fix LG for both OSBuddy and RuneLite

      Fix issue where the resizable client isn't able to be made smaller (Thanks @JoeDezzy1)

      Fix detection of the logout game tab when resizable mode and side panels are enabled (Thanks @JoeDezzy1)

      Add initial support for Sentry to allow us to identify and easily debug exceptions happening with all TRiBot users

      Add methods to determine if the bank is actually loaded, and not just the overarching interface (Thanks @wastedbro)

      Upcoming updates:

      Improved CLI support

      Full Sentry support

      Much more
        • Like
      • 64 replies
    • This release will:

      Fix NPE in Camera API (Thanks @wastedbro)

      Update deposit box interface ids (Thanks @Encoded)

      Add various bank methods (Thanks @wastedbro)




      Fix resizeable minimap bug (Thanks @wastedbro)

      Remove Java 8 requirement

      Please note: TRiBot is not yet fully compatible with Java 10+

      Fix the break handler issues by ensuring the break handler thread never gets paused

      Fix broken settings hooks

      Upcoming updates:

      Improved CLI support

      Much more

      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 68 replies
    • This release will:

      Add support for using custom F key bindings to switch between game tabs (Thanks @erickho123)

      Fix tab opening for "Skills" and "Kourend Tasks" (Thanks @erickho123)

      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 34 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...