Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
TRiLeZ

Tutorial for Safe Botting

Recommended Posts

So what do you think about the bans after doing tutorial island legitimately on the tribot client?

 

Flagged Ips, or ban related to one of your other accounts. I run all my bots on proxies and my mule was my legitimate account. 

Only connection, and it got banned today, never botted just trained legit. Can't make any mistakes atm.

 

This guide is great, and if you're not gold farming cutting down on time is definitely wise.

Share this post


Link to post
Share on other sites

So what do you think about the bans after doing tutorial island legitimately on the tribot client?

 

BLW4E.jpg

 

I just passed through the tutorial perfectly fine. Maybe the people getting banned on tutorial island:

  • Have a flagged IP.
  • Are using disposable email addresses.
    • I'm not sure about this one, but using disposable email addresses could raise suspicion.
  • Are using flagged RuneScape membership payment methods.
    • Maybe PayPal accounts get flagged?
    • Or credit card numbers get flagged?
 

erm hardware bans ? ips are never the only thing , there are ways to flag hardware specially using java

The last time I checked the client, I didn't find any code which grabs hardware IDs.

Share this post


Link to post
Share on other sites

Switch Up Activities

Surely you could implement a way of swapping between scripts eg

Start by woodcutting for 2.5 hours.

- Then swap bots to an Auto Walker and get it to go to a custom tile of where u will start the NEXT bot

- Then start the next bot eg Auto Fisher

 

surely this would MASSIVELY decrease the amount of banns AND you could bot for much longer periods of time?

 

I'm only recomending this here as its not a script thing its a client thing....

Edited by luck or skill
  • Like 1

Share this post


Link to post
Share on other sites
 

I'm pretty sure from a legal standpoint, all sales information (paypal accounts/ccs) can only be used for payment and flagging them for other purposes would be a huge breach of the 1998 Data protection act

 

The patriot act & the NSA don't give a fuck about your privacy.

 

------

 

Great post, Tri. However, if I may, I'd like to suggest an amendment:

 

  • Scripts with bugs in them can cause your account to be trapped in an endless loop of doing something which looks bot-like. Example: If the account gets stuck outside of the Lumbridge chicken coop and it tries to attack chickens which are in the coop for hours, it will look like a bot. It will keep trying to kill the chickens even though it can't reach it. A human would be smart enough to know to open the coop door to fight the chickens.
  • If the script you are running wasn't developed by an established script writer, then baby-sit your bot to ensure that the script doesn't have any bugs in it. If it does have bugs, you can either use a different script, or baby-sit the bot at all times when running the script.

 

You should always baby-sit a bot the first (or first few) times you use it.

 

I learned this 2 days ago the hard way. Here's an example.

 

https://tribot.org/forums/topic/20999-abcl10aio-tri-melee-ranged-magic-trainer-the-one-premium-bot-that-can-do-it-all/

 

An AIO bot made by someone I, as well as many others, I'm sure, consider to currently be one of the top scripters for tribot. He's a premium scripter by the name of Tri.

 

It's an experienced scripter.

It's a premium script - a pricey one, too. I paid $15.

It's been around for a long time - since September of 2013.

It has a lot of user feedback. His thread is almost 50 pages long.

 

Despite all this: https://tribot.org/forums/topic/20999-abcl10aio-tri-melee-ranged-magic-trainer-the-one-premium-bot-that-can-do-it-all/page-48#entry431187

 

I let the bot run unattended for the first time. All of my settings were set correctly (I even spoke to him directly about setting it up properly). Three hours later I came back to this:

 

FOOlvg1.png

 

Like your chicken example, the bot had been trying to walk past the gate, without knowing to open it, for quite some time. Long enough to solve 5 randoms in the same spot.

 

Needless to say, I got banned.

 

I didn't rage at Tri, and that's because one of the first things they teach you when learning Java is that you must try to debug your programs as effectively as you can.

 

You aren't taught to try & debug every single problem that may arise because it's impossible to predict every single scenario & outcome.

 

To ensure absolute safety - always make sure your bot is running correctly before leaving it to its own accord.

Share this post


Link to post
Share on other sites

Switch Up Activities

Surely you could implement a way of swapping between scripts eg

Start by woodcutting for 2.5 hours.

- Then swap bots to an Auto Walker and get it to go to a custom tile of where u will start the NEXT bot

- Then start the next bot eg Auto Fisher

 

surely this would MASSIVELY decrease the amount of banns AND you could bot for much longer periods of time?

 

I'm only recomending this here as its not a script thing its a client thing....

 

A "Script Queue" is in the works.

  • Like 1

Share this post


Link to post
Share on other sites

Nice guide I guess. Most of this is common knowledge for an experienced farmer though.

I don't switch up activities, only to get the needed requirements.

 

The last 3 accounts I created got banned within 4 hours though.

1 day ban ( Bot bust) My accounts are ~21 years old.

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

  • Our picks

    • 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
      • 57 replies
    • This release will:

      Fix NPE in Camera API (Thanks @wastedbro)


      Update deposit box interface ids (Thanks @Encoded)


      Add various bank methods (Thanks @wastedbro)


      Banking#getWithdrawXQuantity


      Banking#getDefaultWithdrawQuantity


      Banking#arePlaceholdersOn




      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
    • This release will:

      Fix an issue where breaks would stop firing


      Fix Combat#getWildernessLevel, use dynamic search for text and cache ID for later calls


      Fix an NPE in the Combat API


      Fix Mouse#leaveGame bug where the mouse wouldn't actually leave the game screen
        • Like
      • 21 replies
    • This release will:

      Add LG support for Runelite


      Fix NPCChat issues


      Fix a bug where the camera angle setter would just hold down a key for 5 seconds (the timeout)


      Slightly adjust the rotation via keys to be more accurate


      Add the ability for asynchronous camera movement via keys


      Make Camera rotation via mouse more fluid, with more antiban, and work much better in resizable mode


      Add a "Camera#setCamera" method, allowing the rotation and angle to be set in parallel


      Increase the likelihood of using the mouse for camera movements


      Add support for adjusting the camera to positionable entities (Positionable#adjustCameraTo)



      Upcoming updates:

      Improved CLI support


      Much more



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

    No registered users viewing this page.

×