Jump to content
asiliukas123

Cant use bot, insta banning

Recommended Posts

HI again. Idk whats happening, but I keep getting banned 90% of all accs. Some of them right after tutorial island. Tried many different scripts, but same things happening, Tried 2 different pc, proxys but nothing changing. Before I was getting maybe 1-2 acc banned from 20-30. What im doing wrong?? I also put acc to afk to stay some hours before going lvl up, but even on afk script after 5min getting account disabled.

Share this post


Link to post
Share on other sites

Has been happening for about two weeks. Reason I've not renewed my VIP here. I have converted all my scripts to another clients API and I've not had that issue since and I'm still using the same proxies. It's odd, I know and it sucks because with TRiBot I can run a 3:1 ratio of bots because it uses the least amount of resources.

  • Sad 1

Share this post


Link to post
Share on other sites

Heya, 

Others may have different opinion but I'll share some of my experience. Although the whole IP flagging thing may be true, I do not believe it plays a huge role in getting your accounts instabanned. It's what you're doing, the duration you're doing, and other factors that are causing you to get instabanned. I've tried experimenting with proxies/vpsn and personally I think it's horseradish unless you're trying to bot on numerous accounts. I've had 50+ accounts created, botted, and banned on my home IP but my main account with total level 2k+, along with my zulrah accounts are doing perfectly fine. All you have to do is  get past the early "instaban" period of a fresh account and watch what you're doing from there on. I'm using the exact same scripts you are (assuming you are using premium scripts) on all my accounts and I'm doing fine. 

Few tips to for avoiding instaban: 

level a wide variety of things.

do a few quests. There are great quest scripts (not on tribot though). For quest scripts, don't do more than 2 quests consecutively. 

Also, "break time" lowering your chance of getting banned is somewhat true but for maximum progression/gains, just switch up the tasks that you're doing instead of taking breaks. it works just as well.

For the first few days, keep your total play-time relatively low. Between 4-6 hours range.

Rest is up to experimentation. You have to find what works and what doesn't. For example, you don't want to bot witch's house + waterfall on fresh accounts. Don't only wcing and fishing the whole day. You learn as you go! Don't be afraid of bans! With every ban, you learn what not to do!

Share this post


Link to post
Share on other sites
16 hours ago, asiliukas123 said:

HI again. Idk whats happening, but I keep getting banned 90% of all accs. Some of them right after tutorial island. Tried many different scripts, but same things happening, Tried 2 different pc, proxys but nothing changing. Before I was getting maybe 1-2 acc banned from 20-30. What im doing wrong?? I also put acc to afk to stay some hours before going lvl up, but even on afk script after 5min getting account disabled.

People can keep denying it but the tribot client is detectable as of rn, its an insta ban but no keep brushing it under the rug lmao.

Share this post


Link to post
Share on other sites
14 minutes ago, UncleHard said:

People can keep denying it but the tribot client is detectable as of rn, its an insta ban but no keep brushing it under the rug lmao.

It is instaban if you do tutorial island on flagged proxies, you will run into the same problem on any client.

Share this post


Link to post
Share on other sites
19 minutes ago, godspower33 said:

It is instaban if you do tutorial island on flagged proxies, you will run into the same problem on any client.

I get banned when using the client, when using looking glass i don't. I've done multiple tests, the client is a giveaway.

Share this post


Link to post
Share on other sites
Posted (edited)
49 minutes ago, UncleHard said:

I get banned when using the client, when using looking glass i don't. I've done multiple tests, the client is a giveaway.

If you're using looking glass with a 3rd party client you can't conclude that TRiBot is detectable without more evidence. Jagex most likely considers many factors when narrowing down whether or not an account is a bot or player. One of those is likely which client the player is using. It's certainly the case that the overwhelming majority of bots are using the default OSRS client, so Jagex may ignore 3rd party clients because statistically they're probably but not definitely real players. This is probably more true concerning fresh accounts that are behaving somewhat botlike.

Nobody can say for sure if TRiBot is detectable or if looking glass is simply good armor without more information, but we can say that it probably is one of those two.

Edited by IceKontroI

Share this post


Link to post
Share on other sites
3 hours ago, IceKontroI said:

If you're using looking glass with a 3rd party client you can't conclude that TRiBot is detectable without more evidence. Jagex most likely considers many factors when narrowing down whether or not an account is a bot or player. One of those is likely which client the player is using. It's certainly the case that the overwhelming majority of bots are using the default OSRS client, so Jagex may ignore 3rd party clients because statistically they're probably but not definitely real players. This is probably more true concerning fresh accounts that are behaving somewhat botlike.

Nobody can say for sure if TRiBot is detectable or if looking glass is simply good armor without more information, but we can say that it probably is one of those two.

Tribot should do something to make their default client unique, looking glass uses a ton of resources.

Share this post


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

Tribot should do something to make their default client unique, looking glass uses a ton of resources.

If TRiBot's client was linked to a unique client signature, Jagex could instantly detect and ban all its userst. Disguising it as something that's already recognized as safe currently seems like a good strategy. Maybe the best strategy would be to optimize looking glass's performance (if that's even possible) since it's already proven itself to be effective.

Share this post


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

I've had bots on bots going for months now many have multiple 99s. Maxed a main and a pure, all recently. I do not think it is detectable.

From what I've seen about this, it's mostly about fresh or low level accounts that don't have a lot of diversity in their skills. Highly leveled or quested accounts should probably not fit into this category.

Share this post


Link to post
Share on other sites

I never was an advocate of using LG, but it's all I use as of now.  Level 3 accounts are flagged by the automatic system and banned as quickly as within 10 minutes for me, across various proxy providers and residential addresses, even without running scripts.

  • Like 1

Share this post


Link to post
Share on other sites
3 hours ago, FALSkills said:

I never was an advocate of using LG, but it's all I use as of now.  Level 3 accounts are flagged by the automatic system and banned as quickly as within 10 minutes for me, across various proxy providers and residential addresses, even without running scripts.

Yep, same for me till I switched clients. Still using same proxies without issues.

Share this post


Link to post
Share on other sites
5 hours ago, FALSkills said:

I never was an advocate of using LG, but it's all I use as of now.  Level 3 accounts are flagged by the automatic system and banned as quickly as within 10 minutes for me, across various proxy providers and residential addresses, even without running scripts.

Hmm, for me, tutorial locks/bans disappeared completely. All my accounts make it out fine, and start up as normal. However, I notice way more bans when leveling up reqs, usually around day 2-4 of leveling. I think the accounts that would have been locked in the past are the ones getting the bans as far as I can tell.

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 key event handling issue


      Fix other event handling issue


      Fix RSServer hook


      Update world hopper to have it use OCR, thanks to Todd


      Use proper disposal of old Graphics objects


      Reformat code


      Rearrange code


      Organize code imports


      Apply around 8000 automated code refactorings


      Make preparations for Java 9


      Fix 11 various bugs


      Add more reliable debugging support


      Fix mouseEntered/Exited event dispatching bug


      Fix minimap walking bug where it opens the map


      Fix broken hooks for today's game update
        • Thanks
        • Like
      • 55 replies
    • This update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
        • Like
      • 27 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
  • Recently Browsing   0 members

    No registered users viewing this page.

×