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

Bot Automatic Login Help

Recommended Posts

Hello, 

Last night my VPS internet went down and my accounts were stuck trying to login for 'X' amount of time. When I woke up, reset the VPS and got the connection back I found out that all of the accounts were banned.

Could RS see that they were trying to login even without any internet connection?

If so, is there a way I can stop the accounts trying to login if the internet does go off, or do I just have to turn automatic relogging off? But if I turn it off, how do I do breaks?

Thank you.

Edited by ConnorM

Share this post


Link to post
Share on other sites
6 hours ago, ConnorM said:

Hello, 

Last night my VPS internet went down and my accounts were stuck trying to login for 'X' amount of time. When I woke up, reset the VPS and got the connection back I found out that all of the accounts were banned.

Could RS see that they were trying to login even without any internet connection?

If so, is there a way I can stop the accounts trying to login if the internet does go off, or do I just have to turn automatic relogging off? But if I turn it off, how do I do breaks?

Thank you.

runescape wouldn't be able to send the login attempts to their server without internet connection. they might save the data and send it as soon as your internet goes back on, who knows?

Jagex works with delayed bans, which means that even though your accounts are still logged in, they could already be banned. this can take from minutes to hours. So theres a big chance the bans you got weren't from this.

Edited by gef30

Share this post


Link to post
Share on other sites
6 hours ago, ConnorM said:

Hello, 

Last night my VPS internet went down and my accounts were stuck trying to login for 'X' amount of time. When I woke up, reset the VPS and got the connection back I found out that all of the accounts were banned.

Could RS see that they were trying to login even without any internet connection?

If so, is there a way I can stop the accounts trying to login if the internet does go off, or do I just have to turn automatic relogging off? But if I turn it off, how do I do breaks?

Thank you.

No, it's extremely unlikely they do this. Almost zero chance whatsoever. First of all, they can't see anything you do if you don't have an internet connection.

 

Second, repeatedly trying to log in isn't a bannable offense, so why would you get banned for it?

Share this post


Link to post
Share on other sites
26 minutes ago, gef30 said:

runescape wouldn't be able to send the login attempts to their server without internet connection. they might save the data and send it as soon as your internet goes back on, who knows?

Jagex works with delayed bans, which means that even though your accounts are still logged in, they could already be banned. this can take from minutes to hours. So theres a big chance the bans you got weren't from this.

That's what I would have thought, but I've been running a large amount of bots and stopped over 90% to do something last night with them, after running all for 4-5 days but the only ones that got banned were the ones that got stuck in the login loop?

I know they can't send a login request when their is no physical connection I just found it strange how it was only those 4 accounts 

Share this post


Link to post
Share on other sites
Just now, wastedbro said:

No, it's extremely unlikely they do this. Almost zero chance whatsoever. First of all, they can't see anything you do if you don't have an internet connection.

 

Second, repeatedly trying to log in isn't a bannable offense, so why would you get banned for it?

I know that a connection isn't their so login requests would not be sent but I do not understand why the 4 I left in the login loop got banned whilst all the others did not. They were all botting the same amount, exact same bot etc yet only the 4 I forgot to turn off got banned. I mean this could just be a coincidence. 

Logging in is not bannable no, but an account trying to login repeatedly for 6 hours may seem a bit suspicious.. I mean, a real person would not sit there logging in for 6 hours if they're not connecting 

Share this post


Link to post
Share on other sites
12 minutes ago, ConnorM said:

I know that a connection isn't their so login requests would not be sent but I do not understand why the 4 I left in the login loop got banned whilst all the others did not. They were all botting the same amount, exact same bot etc yet only the 4 I forgot to turn off got banned. I mean this could just be a coincidence. 

Logging in is not bannable no, but an account trying to login repeatedly for 6 hours may seem a bit suspicious.. I mean, a real person would not sit there logging in for 6 hours if they're not connecting 

No, but keep in mind, Jagex isn't looking at your screen. They only collect data they think will be helpful. It seems unlikely they would choose something like this, because of the fact it's not that common and probably not a great indicator of bots.

Your situation is probably a coincidence, or perhaps there's another factor you aren't thinking of (think about every difference). 

 

If you still feel otherwise, you're more than welcome to keep testing it. If it truly is consistent, then maybe you're on to something. However, for now, I'm still chalking it up to pure coincidence.

Share this post


Link to post
Share on other sites
6 minutes ago, wastedbro said:

No, but keep in mind, Jagex isn't looking at your screen. They only collect data they think will be helpful. It seems unlikely they would choose something like this, because of the fact it's not that common and probably not a great indicator of bots.

Your situation is probably a coincidence, or perhaps there's another factor you aren't thinking of (think about every difference). 

 

If you still feel otherwise, you're more than welcome to keep testing it. If it truly is consistent, then maybe you're on to something. However, for now, I'm still chalking it up to pure coincidence.

I'd have to disagree it that it isn't a great indicator as a real life human would not login over and over for an hour if it just says 'Error connecting', not even for 2 minutes.

I mean, it must be a coincidence I just found it very very odd that it was only those stuck in the loop that saw the banhammer, even those that were created same day/trading same mule - Even those that are older are surviving. There really is no difference in my accounts at all, unless a Jmod was actually active in game and banned me before they disconnected I have no idea.

I obviously believe that it couldn't be for this reason purely as I had no connection so their should be no login attempts. Back to the previous questions though - Is there any settings in tribot that stops automatically logging in after 5 failed attempts or not?

Thanks for the replies as well :)
 

Share this post


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

I'd have to disagree it that it isn't a great indicator as a real life human would not login over and over for an hour if it just says 'Error connecting', not even for 2 minutes.

I mean, it must be a coincidence I just found it very very odd that it was only those stuck in the loop that saw the banhammer, even those that were created same day/trading same mule - Even those that are older are surviving. There really is no difference in my accounts at all, unless a Jmod was actually active in game and banned me before they disconnected I have no idea.

I obviously believe that it couldn't be for this reason purely as I had no connection so their should be no login attempts. Back to the previous questions though - Is there any settings in tribot that stops automatically logging in after 5 failed attempts or not?

Thanks for the replies as well :)
 

How many times has this happened to you? 

like @wastedbro basicly said: its coincidence until you get a much larger sample. And even then you can't be sure. 

I dont think this happened to you often enough to make these conclusions.

Edited by gef30

Share this post


Link to post
Share on other sites
36 minutes ago, gef30 said:

How many times has this happened to you? 

like @wastedbro basicly said: its coincidence until you get a much larger sample. And even then you can't be sure. 

I dont think this happened to you often enough to make these conclusions.

Have you even read what I have put?

You clearly just quoted me saying 'I obviously believe it can be for this reason'. I was stating what happened and wanted other people's opinions whilst asking questions located at the bottom of the thread which anyone is still yet to answer lol

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