Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Buy OSRS Gold

Sell OSRS Gold
realidadk2

Jagex's Botwatch resources

Recommended Posts

Posted (edited)

 if there is such thing as getting "flagged", and getting your accounts banned continiously after the first ban, that means Jagex's botwatch can recognize ANY script, ABC, ABC2 or any anti-ban features.

 

but it seems that they have a limited capacity to distribute resources from their Botwatch to certain flagged IPs, botting areas or suspicious activities from accounts (maybe getting reported several times in the same day?),

 

if Jagex can recognize any script, then, the major concern for botters is to minimize their possibility to get choosed by Jagex's botwatch (whatever ritual they consider to be true to stay away from Jagex's botwatch like taking breaks/etc), ain't that right?

 

or MAYBE, the best way to create efficient anti-ban features/script is to test it on ALREADY flagged IPs. if an account from a flagged IP doesn't get banned while botting, that means that the anti-bot features/script is EFFICIENT to begging with.

 

what do you think about this theory?

Edited by realidadk2

Share this post


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

Bad idea, why would you want to feed botwatch data for no reason

maybe i didn't articulated my thoughts well enough:

 

if your IP is flagged and you play LEGIT, you do not get banned. this is because botwatch do not read your actions as coming from a BOT.

 

this means that if your IP is flagged and your script is well articulated, botwatch wouldn't read your behavior as coming from a BOT neither.

 

 

this means that we should use a flagged IP to achieve a more sophisticated anti-ban technology.

 

Share this post


Link to post
Share on other sites

 

45 minutes ago, adamhackz said:

Ive had different experiences. 

 

let's take that as a yes.

 

even if Jagex bans legit gameplay on a flagged IP, same logic can apply to botting in high risk areas such as cowhides/chickens/tutorial island.

 

if an anti-bot is efficient enough we should test it in high risk botting-ban areas of the game to make its technology unbanneable to the point in which Jagex's botwatch cannot detect it even using most of its resources.

 

we combat fire with fire.

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.


  • Our picks

    • Over the past few months, I’ve been working diligently on a new project - TRiBot X. Everything has been written from the ground up, with all of the best practices of software engineering. Every aspect of TRiBot has been re-imagined to support three main goals: flexibility, useability, and reliability.
        • Like
      • 30 replies
    • Come give us feedback on the next version of TRiBot!
        • Thanks
        • Like
      • 74 replies
    • TRiBot is looking to improve a lot of its customer relationship management, customer on boarding process, customer experience, design elements, community engagement and pretty much everything else you can imagine when it comes to marketing.

      Our goal: To ensure that the marketing done TRULY reflects the experience and does not shine an inaccurate light on what TRiBot is lacking in.

      So I ask, what do you love about TRiBot and what do you hate about TRiBot? What does O S Bot, Rune M8, PowR Bot and Dre amBot do better? (yes I purposely didn't spell it right 😂).

      Love, 

      RileyZ
        • Like
      • 23 replies
    • Over the last three weeks, I've been working on upgrading our server infrastructure. It's finally ready and is now live!

      Why?

      Increased reliability - less server errors


      Increased availability - less downtime


      Increased security - keeping us and you secure


      Increased capacity - ability to serve you better


      Increased speed - less waiting for things to load


      Faster development - server and service updates will come faster


      What are the changes?

      Move from a single AWS EC2 instance to AWS ECS (Elastic Container Service)


      Distributed computing


      Load balancing


      Git management of server files and filesystem


      Redis caching


      How?

      AWS ECS (with 10 EC2 instances)


      AWS ElastiCache (Redis)


      AWS Load Balancing


      AWS EFS (Elastic file system)


      Please bare with us as I continue to tune the server for maximum performance. Slow loading speeds may occur temporarily. I thank everyone for their patience.

      Please post on this thread if you experience any issues other than slow loading times.
        • Like
      • 51 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
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...