Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Sign in to follow this  
mitch..

Botting and manually leveling up same skill

Recommended Posts

3 hours ago, Led Zeppelin said:

i dont think playing legit is going to make you more likely to get banned but they could definitely profile you against your bot.

I sometimes just pause the bot in the middle of a session and randomly legit it for a while- I don't know if it actually helps but I hope it might throw off their heuristics a bit. 

Share this post


Link to post
Share on other sites
11 minutes ago, BitzLeon said:

I sometimes just pause the bot in the middle of a session and randomly legit it for a while- I don't know if it actually helps but I hope it might throw off their heuristics a bit. 

i think that if anything they would just see the data of a human and it would make it less likely to get you banned, like maybe they give you some leeway if you play legit?

Share this post


Link to post
Share on other sites

I've read that playing with your bots movements in the middle of a sesh could be a bad thing, as the movements all of the sudden change compared to how the script was designed to do.

I've managed to bot 12 hours straight for months without bans, some get caught some don't.

Botting red chins is highly monitored, unless you scripted your own chinner to have a completely different approach to all of the chinning scripts out there & you should be fine.

Share this post


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

I've read that playing with your bots movements in the middle of a sesh could be a bad thing, as the movements all of the sudden change compared to how the script was designed to do.

I've seen this too, that its better to always bot on your account so that's what looks "normal". Then again...I have botted on mains for hours a day then play on them legit after a 8-12 hour botting session and they have never been banned so who knows.

Share this post


Link to post
Share on other sites
2 minutes ago, monkaSman said:

I've seen this too, that its better to always bot on your account so that's what looks "normal". Then again...I have botted on mains for hours a day then play on them legit after a 8-12 hour botting session and they have never been banned so who knows.

that's exactly what we are dealing with. 

No one knows.

Share this post


Link to post
Share on other sites

Like i said fellas if they have ANY inclination that the account is being played legit by a human and not completely botted they could possibly leave you out of the ban waves despite knowing that you're a bot, i am under the assumption that they can detect any and all bots within a matter of a couple hours so it's about botting smart and staying within whatever Jagex considers to be "reasonable use" for bots, not more than 12 hours a day and less is better.

 

It is easier to detect a human than a bot at this point, think of it in the british police mindset: everyone is a bot until we prove they aren't, that's the only way a botwatch would work effectively.

Edited by Led Zeppelin
  • Like 1

Share this post


Link to post
Share on other sites
On 12/15/2018 at 11:20 PM, BitzLeon said:

I sometimes just pause the bot in the middle of a session and randomly legit it for a while- I don't know if it actually helps but I hope it might throw off their heuristics a bit. 

Today i for the first time created an alt to bot on to supplement my mains cashstack.

Facts: i played half/half legit and botting on main for 2+ months (probably botted like 10+ hours a day atleast on main)
I used looking glass 100% of the time.

I created alt and botted on it for ~2 days without looking glass and running a premium script.

Woke up today with a ban on main for 1 day and perm ban for my alt. 

Not sure what factors were in play, but i am quite certain that playing legit played a huge part in only receiving a 1 day ban.
I say this because my main has 240+ quest points and 1600+ totals while my alt that got permbanned had less than 100 total level, and 80 of them were mage levels, 0 quest points and pretty much looked like a bot account overall.. needless to say i've learnt my lesson...
Bot smart, not by interfering while botting a certain skill, but by playing legit doing other stuff such as farm runs that is a bit more difficult to bot  

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Our picks

    • This update features:

      Fixed broken hooks from today's update


      Fix wilderness level with RuneLite (Thanks @Todd)


      Add support for Kotlin .class files in scripts (Thanks @wastedbro)


      Overhaul Inventory API (Thanks @wastedbro)


      Add List support for common methods


      Change method grouping to make more sense (by functionality)


      Refactor methods to utilize Java 8 streams instead of cumbersome loops




      Recognize chatbox minimization (Thanks @JoeDezzy1)


      Fix Screen#isInViewport when NPC chat is open (Thanks @JoeDezzy1)


      Fix login bot bugs (Thanks @erickho123)


      Fix hint arrow return values (Thanks @Encoded)


      Fix depositAllExcept functionality (Thanks @wastedbro)


      Change containing box interface bound and adjust for Y values (Thanks @erickho123)
        • Like
      • 150 replies
    • This release will:

      Fix prayers and world hopper API (Thanks @JoeDezzy1 and @erickho123)


      Improve banking API (Thanks @Encoded)


      Adds methods for returning and using Java Lists, rather than arrays


      Slightly randomizes some hardcoded behaviour


      Removes sleeps from waitConditions; the efficiency saving potential is negligible in these use-cases, therefore cleaner code is preferable


      Other back-end improvements





      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Sad
        • Haha
        • Thanks
        • Like
      • 90 replies
    • This release will:

      Add new internal framework for capturing exceptions


      Fix issue with not selecting the last column in world hopper (Thanks @Todd)


      Add a message about pin usage in Banking#openBank (Thanks @Todd)


      Disable the firewall by default (Thanks @Todd)


      Fix handling of the welcome screen after login (Thanks @Encoded)


      Fix wrong amount bank withdrawal (Thanks @Encoded)


      Fix Screen#isInViewport


      Fix Game#isInViewport (Thanks @Encoded)


      Call onBreakEnd for ListenerManager Breaking Listeners (Thanks @Encoded)


      Fix Prayer#getPrayerPoints NumberFormatException (Thanks @JoeDezzy1)



      Note: If you are using LG, please restart both the RS client and TRiBot.
        • Thanks
        • Like
      • 28 replies
    • 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
      • 64 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
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...