Jump to content
Sign in to follow this  

Testing a Script

Recommended Posts

Welcome to TRiBot.

Some helpful info:

On 7/1/2017 at 3:28 PM, YoHoJo said:

Things I recommend to do before purchasing a premium script:

Read 1st post on script thread. Make sure it has the features you want. 

Read through last few pages on the script thread. See if customers are happy, any reported bugs, any good progress reports posted, does the scripter respond to help/suggestions in a timely manner?

Most premium scripts offer a FREE trial. Make use of this, and make sure the script works well for your needs. 

Only after taking these steps should you purchase the script and be guaranteed you'll be happy with it. 

Happy Botting. 

Anytime you bot, you risk getting a ban.
Don't bot anything you're not willing to risc.

Share this post

Link to post
Share on other sites

Since you posted in this section I assume that you refer to testing your own script. You are going to need VIP for this purpose.


On 2/6/2018 at 8:16 PM, 13thFox said:

When testing a script should I have a separate account?

There is no point in using a maxed account to test a few lines of code. Use a spare account with the minimum stats required for that particular script.


On 2/6/2018 at 8:16 PM, 13thFox said:

Do I get banned instantly if my script doesn't work properly?

Patters are easily observed over a prolonged period of time. The more input your script provides, the higher the chance of it getting banned. Getting detected within seconds is not very commonly reported.


On 2/6/2018 at 8:16 PM, 13thFox said:

What do you guys recommend me to do in order to test scripts?

Click the Start button and see what happens.

  • 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
Sign in to follow this  

  • Our picks

    • This update will:

      Fix GE inventory item positioning bug

      Fix broken object hooks
        • Like
      • 21 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
    • Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.

      This release features:

      Re-sizable mode support for both LG and the regular client

      Slightly improved login bot

      Removed final access modifiers from API classes

      Added RSServer hook wrapper to get the client's cached list of server/world info

      [NEW] Bug fix for intelligent banking

      [NEW] Improvement to the stability of LG over time

      [NEW] Vastly improved the reliability and speed of Screen#getColorAt on both LG and the regular client

      [NEW] Fix LG login problems

      [NEW] Fixed re-sizable mode container bug

      [NEW] Fixed re-sizable mode mouse bug

      [NEW] Use of public constants in the Banking API

      [NEW] Use of other various constants such as Projection#NULL_PT and Screen#EMPTY_COLOR

      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
        • Thanks
        • Like
      • 12 replies
  • Recently Browsing   0 members

    No registered users viewing this page.