Jump to content
Sign in to follow this  
borax

Getting Banned

Recommended Posts

I botted for approximately..... 2 1/2 hours, at most 3.

I logged out, smoked a nice blunt that periled with the finest Tabaco leaf straight from the amazon itself. The bud within this beast of a leaf was basically the color of the power rangers combined into on big green nugget of love.

So I log back on. BAM! I got the ban hammer within the 3 hours of botting. GG RIP Lost 120m cash and I was a mith ftp pure.. so gg.

 

  • Like 2

Share this post


Link to post
Share on other sites
55 minutes ago, borax said:

I botted for approximately..... 2 1/2 hours, at most 3.

I logged out, smoked a nice blunt that periled with the finest Tabaco leaf straight from the amazon itself. The bud within this beast of a leaf was basically the color of the power rangers combined into on big green nugget of love.

So I log back on. BAM! I got the ban hammer within the 3 hours of botting. GG RIP Lost 120m cash and I was a mith ftp pure.. so gg.

 

Don't bot on acc you care about then.

  • Like 1

Share this post


Link to post
Share on other sites
4 hours ago, borax said:

I botted for approximately..... 2 1/2 hours, at most 3.

I logged out, smoked a nice blunt that periled with the finest Tabaco leaf straight from the amazon itself. The bud within this beast of a leaf was basically the color of the power rangers combined into on big green nugget of love.

So I log back on. BAM! I got the ban hammer within the 3 hours of botting. GG RIP Lost 120m cash and I was a mith ftp pure.. so gg.

 

verry nice

Share this post


Link to post
Share on other sites
5 minutes ago, chrismm said:

same happend to me. ill not reffer tribot for anyone thats for sure, this bot is very bad

Using LG? A premium script?
I have accounts on their 4th bond. Obviously you dont bot on an account that your not willing to lose, but if you do it well you wont lose accounts often.

Share this post


Link to post
Share on other sites

If you take all the precautions that's all over these fourms when botting, you'll be fine. 

 

Don't bot on an account you wouldn't want getting banned, if your botting you at the risk for being banned . But from what I've read the best thing to do is use LG, proxies, paid/private script, and using break handler . Since I've started using all these precautions and doing some human activity on the accounts, I haven't gotten a ban. I'm not gold farming but I do have several accounts each getting high stats and making some bank.

  • Like 1

Share this post


Link to post
Share on other sites

This happened to me yesterday i did the Trial of the Mining bot here forgot the name and i botted 30 minutes only, today i log in i got a 2 day Ban. I'm never using tribot again, i tried several different scripts and only botting less than one hour and Jagex Detects everything, i even tried different computers and different States. The accounts always got Banned.

Share this post


Link to post
Share on other sites
24 minutes ago, MarioMaserati said:

This happened to me yesterday i did the Trial of the Mining bot here forgot the name and i botted 30 minutes only, today i log in i got a 2 day Ban. I'm never using tribot again, i tried several different scripts and only botting less than one hour and Jagex Detects everything, i even tried different computers and different States. The accounts always got Banned.

Did you use looking glass? getting banned within 3 hours if using looking glass is pretty unlucky. If I don't use looking glass there's a 90% chance ill be banned the next day. If i do use looking glass there's a 90% chance the account will last over 2 weeks. 

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

×