Jump to content
Sign in to follow this  
zshorty123

are combat scipts more ban prone?

Recommended Posts

been botting on 3 accounts. my skiller i been botting like a crazy person but no ban or anything. my 2 accounts i didnt come combat training also used another script that also could be it but i notice i can bot 12 hours plus on skillers no issues. had all 3 bots running when the 2 got banned and the skiller stayed un touched.

Share this post


Link to post
Share on other sites

Your sample size is way too small to make any conclusions. You didn't mention how you were training combat or what you were planning to do with the account once you had combat stats. You didn't mention how long you've been training on the accounts or what scripts you are using. Furthermore you didn't mention what skills your 'skiller' was training.

Provide that information and I can give you a meaningful reply. 

Share this post


Link to post
Share on other sites
1 hour ago, zshorty123 said:

well i didnt go in to detail because i was asking a general question not on the script i was using. it was weather combat scripts are more ban likely than skiller scripts. im using free scripts so it dosnt really matter yet.

Combat is so broad that you need to be more specific. You basically are asking the question "What are the ban rates like for botting?". 

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 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
      • 55 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.

×