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

HELP PLEASE

Recommended Posts

Posted (edited)

Hi, please help solve the reason why my account was banned.

-I hand played the entire account

-It was botting on a SOCKS proxy by Virmach

-The orignal IP it was botting on stopped working so i cancelled service and decided i would use a different IP from VIrmach.

-I logged into that account on 2nd IP Aprox 3/18 at night. played for a couple hours (just fishing)

-I logged onto that account on my OS Mobile phone and traded over some gold Yesterday night to my Main bot Which i Bot on my HOME IP.

-I checked if my main bot was banned and he wasn't. He has been running 24/7 (i originally thought that the ONLY way he could've been banned was with a "Chain-ban" but i dont even think thats a possiblity.

-I also paid a power-leveler to train on my account (G2g.com) which cost me 120$ IRL (my method involves 200+ hours of playing before you can start botting it)

-I Let the account Age

-I always use LG/Human mouse movements

If you have any thoughts on what the cause of this ban could be please let me know. I'm very clueless right now and i'm counting on you guys.

(RIp 120$ and like 10 hours of hand training.. ) is it possible that after years jagex has finally upgraded there shit and can detect Tribot???

 

Here is the Evidence

 

Account banned for macroing in OldSchool. Our macro detection system has been monitoring your account closely and has detected that you are using illegal 3rd party software which violates the rules of the game and breaches your terms of service with Jagex. Our team have reviewed the evidence and can confirm that you were using illegal botting software. Jagex are able to accurately detect all illegal 3rd party software and any promises from their makers about being 'totally undetectable' or 'no ban guaranteed' are inaccurate. As such your account has been permanently removed from game. Please take this time to familiarise yourself with the rules should you wish to create another account.

PLEASE post and Ideas/thoughts that could've resulted into this.

 

Edited by kylezell

Share this post


Link to post
Share on other sites
28 minutes ago, coffeedog said:

1) Botting, that's pretty obvious for a ban.

2) Changed IPs so that could've been it, but mostly would've been a lock.

3) Paid someone to level your account, which can flag account.

I mean you're botting, that's why you got banned, simple as that.

 

NO I DID NOT BOT AT ALL it was a typo.  its not simple

Share this post


Link to post
Share on other sites
4 minutes ago, kylezell said:

NO I DID NOT BOT AT ALL it was a typo.  its not simple

You said " it was botting on a SOCKS proxy by Virmach "/"The orignal IP it was botting on stopped working so i cancelled service and decided i would use a different IP from VIrmach." Is this incorrect?

  • Thanks 1
  • thonking 1

Share this post


Link to post
Share on other sites
Posted (edited)

Any time you bot, you risk getting a ban.
It's hard to say for exactly what reason this happened.

I'd recommend testing scripts on a dummy account until you feel comfortable enough that you can use it without much risk of a ban.

 

Edit:
How can you say you didn't bot at all, when in OP you say:

-It was botting on a SOCKS proxy by Virmach

-I always use LG/Human mouse movements

Edited by YoHoJo
  • Thanks 1

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 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
      • 74 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
    • 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
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...