Jump to content
Sign in to follow this  
morbideraser

2nd botting offence?

Recommended Posts

40 minutes ago, morbideraser said:

I used an agility script on a different account and got a 3 day or 5 day ban from it. I was considering running a zulrah script on a different account now. My account I play on now has no offences or reports, so would I just get a temp ban if discovered?

Depends on accounts age, total level, and a bunch of other things.
Unless youre mass gold farming or something like that though you probably would only get a temp ban(assuming its an old main account or something)

Share this post


Link to post
Share on other sites

I've heard of chainbans, Personally I've got a total of 3 accounts banned, The first account I ever got banned it started off as a temp ban then I decided I really could care less and tried another script and ended up getting perm banned. I made 2 other accounts after put bonds on at level 3 and they got perm banned right off the bat. So i'm not sure if that has something to do with my IP or maybe it was just the level and script I was using. My first account that got the 2nd chance I did a few quests on, And was just using a autofighter and did a little work on, Had some cash and a dragon defender aswell. But the other 2 I just put bonds on and started spinning flax, and the other minning, Since then i've only really used the premium NMZ bots from here and they work like a charm, I've done training services for people using the nmz script and not once ever got banned. I use VPNS now and bounce around from botting at home and work aswell. But the nmz is flawless.

Hope that helped a tad.

Share this post


Link to post
Share on other sites
On 12/17/2017 at 7:11 PM, morbideraser said:

It's an ironman with 2k total+ that's why I really just hope its a temp ban lol

Why do people bot ironmen? Just asking out of curiousity. Like isn't the fun and challenge of it playing legit? You can't even trade/profit. I would understand botting a main to high stats much more than an ironman, it seems pointlessly "extra".

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

×