Jump to content

Alek

Ex-Staff
  • Posts

    7878
  • Joined

  • Last visited

  • Days Won

    200
  • Feedback

    100%

Posts posted by Alek

  1. Today is Thursday which means there has been a game update. This update schedule has remained the same way for over 5 years. Sometimes our auto-updater works, sometimes it doesn't. From now on whenever you have problems with the client on a Thursday, just be patient and try every few hours or so. Sometimes the update is automatic, sometimes it takes us a little bit of work, sometimes it takes us a lot of work.

    • Like 1
    • Sad 2
    • Heart 2
  2. Today is Thursday which means there has been a game update. This update schedule has remained the same way for over 5 years. Sometimes our auto-updater works, sometimes it doesn't. From now on whenever you have problems with the client on a Thursday, just be patient and try every few hours or so. Sometimes the update is automatic, sometimes it takes us a little bit of work, sometimes it takes us a lot of work.

    • Heart 1
  3. Today is Thursday which means there has been a game update. This update schedule has remained the same way for over 5 years. Sometimes our auto-updater works, sometimes it doesn't. From now on whenever you have problems with the client on a Thursday, just be patient and try every few hours or so. Sometimes the update is automatic, sometimes it takes us a little bit of work, sometimes it takes us a lot of work.

  4. Today is Thursday which means there has been a game update. This update schedule has remained the same way for over 5 years. Sometimes our auto-updater works, sometimes it doesn't. From now on whenever you have problems with the client on a Thursday, just be patient and try every few hours or so. Sometimes the update is automatic, sometimes it takes us a little bit of work, sometimes it takes us a lot of work.

    • Heart 1
  5. Today is Thursday which means there has been a game update. This update schedule has remained the same way for over 5 years. Sometimes our auto-updater works, sometimes it doesn't. From now on whenever you have problems with the client on a Thursday, just be patient and try every few hours or so. Sometimes the update is automatic, sometimes it takes us a little bit of work, sometimes it takes us a lot of work.

    • Heart 1
  6. Today is Thursday which means there has been a game update. This update schedule has remained the same way for over 5 years. Sometimes our auto-updater works, sometimes it doesn't. From now on whenever you have problems with the client on a Thursday, just be patient and try every few hours or so. Sometimes the update is automatic, sometimes it takes us a little bit of work, sometimes it takes us a lot of work.

    • Sad 1
  7. So a few things, OSBot (by default) will not execute the script unless you are fully logged in - so you don't need to rely on your custom method. It's possible that you are fully logged in, but the player data hasn't been sent yet (especially on populated areas/worlds). Normally this isn't an issue but you mentioned using low cpu mode, which may cause an issue. Try running OSBot without low cpu mode and see if that makes a difference.

    Also remove this:

    trader.isOnScreen() && trader.isVisible()

    You're using interaction event which has its own set of guidelines on how to interact with entities, which may conflict with your code (trust me). If you don't want OSBot to move the camera/walk to the entity then do something like:

    InteractionEvent event = new InteractionEvent(trader);
    event.setCamera(false);
    event.setWalking(false);
    execute(event);

    Something like that, I don't remember the exact syntax off hand.


    But back on topic, let me know how running it normally goes.
     

     

  8. Can you elaborate exactly what you are doing? Are you running the client on mirror mode, no randoms, low cpu? Are you using Worlds hop method or do you have your own world hopping method?  You said you're using getName() but your code snipped doesn't show it. 

  9. 14 hours ago, Tony said:

    I could be wrong but I was under the impression that Jagex doesnt always immediately ban upon detection. It doesn't seem out of this world to suggest that a lot of accounts that survive botting for a while didn't escape immediate detection but were just spared a few days/weeks to obscure their bot detection. I could be wrong but the fact that you were banned that fast being the script's fault seems like a false premise. Every script gets you banned eventually.

    An intelligent post, well explained.

    • Like 1
  10. 20 hours ago, sambist68 said:

    Never said I did, just quoted for the record all the setting I was using.

    I'm stupid for botting on my main, not for activating those settings. They may or may not make the bot less detectable, but I don't think they do any evil, unless you believe you will literally become unbannable lol.

    No, it literally does nothing - at all. Don't even consider it doing anything to make it less detectable. 

  11. 4 minutes ago, Folks said:

    I am not actually making a script with it, I am training a deep learning model for an into to machine learning class and i figured the easiest way to build a data set would be to automate it with a bot. ?

    Thanks a ton!

    Cool! I wish you best of luck it sounds like a lot of fun. 

    • Heart 1
  12. I did not get banned because I randomized my numbers during the sleep time, for instance sleep(random(3424.1231L, 94822.03992L)). This prevents my bot from being profiled and there's no way to detect me as a bot. Please share with your friends.

  13. I can't see the text files you attached. Also I don't entertain discussion of "bans" or "detection" unless you have either reversed the game and saw a detection concern, were a company employee at some point, or have a video/screenshot of the company making a claim as to what they use to classify/detect a bot.

×
×
  • Create New...