Jump to content
Sign in to follow this  
Qtulu

What should I delete after ban? [random.dat + jagex_cl_oldschool_LIVE.dat]

Recommended Posts

Deleting random.dat + jagex_cl_oldschool_LIVE.dat files after your account was banned is a good way to lessen the chance of other bans when using the same machine (PC/VPS/whatever) + multiple accounts.

In Windows, you can find them here: C:\Users\[Your computer account name]

Also, I'd like to ask more experienced botters if deleting the whole 'jagexcache' folder found in that same folder is of any help or pointless.

Thank you!

Q

Share this post


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

I've found that deleting any of the cache files are completely unnecessary.

^ This. This is purely superstition. Instead, look at what you did on your account and try to change it up. The only proven way to reduce bans is to continuously use trial and error on your botting practices.

  • Like 2

Share this post


Link to post
Share on other sites

Unless someone has deobfuscated files in those folders, we will never know exactly what data is stored there. I don't think there is any harm in deleting them though, since they will be re-generated when you run runescape again. What you should do however is change your IP address and not buy membership with the same paypal email address if that is your method of payment.

  • Like 1

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
Sign in to follow this  

  • Similar Content

    • By acezeps
      Quick one here.
      Botted 99 str 88 att 75 def 99 range and 94 mage + all skilling stats for barrows gloves and i got a 2 day ban a few months ago.
      I just found out now about Auto clicking rapid heal at nmz and i was wanting to get 95 att and 90 def. 
      I know slightly randomized auto clicking is not that detectable but i was wondering how detectable it would be with my account being flagged. The fact that its randomized and i wouldnt be suiciding nmz makes me think its not that risky if im doing it for 2 hours considering i nmz legit for 2 hours anyways, just getting annoying clicking twice every minute while trying to watch a movie or something
      Let me know what you think boys. 
       
    • By YoHoJo
      More Runescape Botting Guides at https://RSBotSpot.com
      Join our Runescape Botting Discord chat channel here
      Original/Updated Article here at RSBotSpot
      This guide contains affiliate links
      How to Use TRiBot Looking Glass & Bot though the Official Runescape Client
      TRiBot’s Looking Glass feature allows you to bot through the official Runescape client by hooking onto and controlling it. Looking glass also supports proxies for botting & other clients like OSBuddy.
      While there’s no evidence that TRiBot is detectable, this feature was released as a form of antiban for users worried about the potential detectability of botting clients. Botters seem to be torn 50⁄50 about the effectiveness of Looking Glass on bans, but it never hurts to have some extra protection. This guide will cover how to use TRiBot Looking Glass to bot through the official Runescape client!
      1. Install Java Development Kit (JDK)
      Download and install JDK here. I will be using 32 bit JDK 8u151.
      Java Development Kit Download
      At the time of writing, only Java 8 is supported. 2. Load Runescape & TRiBot
      Load Runescape up to the login screen, and TRiBot up to the client select screen.
      3. Start Looking Glass
      On TRiBot, click the “New Client (Looking Glass)” button.
      Hooking TRiBot to the Official Runescape Client
      4.(Optional) Set a Proxy
      If you’re using a proxy for runescape botting, now’s the time to apply it. To do this: right click the client’s tab on TRiBot, and select “Set Proxy”.
      TRiBot Looking Glass Set Proxy
      That’s it, you’re done!
      Your TRiBot client is now hooked onto the official client, and you’re ready to start botting Runescape!
      Helpful Links:
      You can find out more about TRiBot’s Looking Glass feature on it’s release thread here You can find out more about using proxies with TRiBot Looking Glass here You can find more working Java/Client version combinations reported here  More setup guides: By Einstein
      Note: Some threads are only visible to TRiBot VIP users. Our Favorite Runescape Botting Proxy Providers
      We've tested and had great results with Runescape botting proxies from:
      Blazing Proxy (Use code RSBOTSPOT to save 5% recurring!)(CHEAPEST) Virmach (Use code SAVE20 to save 20% on your first order!) Proxy Fish (Use code OSBOT20 to save 20% on your first order!) Your Private Proxy Our Other Guides:
      All About Proxies for Runescape Botting How to Create and Register Runescape Bot Accounts Through a Proxy How to Use Proxies With TRiBot How to Expand your Goldfarm with a Botting VPS How to Unlock your Runescape Bot Account
    • By Zulrahkiller20
      The pest control script  is not working properly and Tri scripter is not replying to my messages. What you suggest me to do?
    • By DaFukWasDat
      I believe Jagex relies purely on the amount of the time played, my evidence for this:
      1) People report being banned for using a script, yet another person will not, this should be seen as evidence that they cannot detect the script pattern or odd behavior, or the bot client.
      (For example, I ran a ranging guild script which others had warned got them banned, I ran it for at least 12 hours total, with breaks, and was never banned)
      2) The only time you hear someone say they was banned, is followed by them saying that they botted for a DAY (24 hours), which suggests they ran the script for much longer than 4 hours.
      3) Ask yourself, when have you banned within a couple of hours of using a script? Most likely never.
      4) Jagex uses J mods to manually ban players, why would they do this if their automatic bot detection system was working?
      5) I coded a macro, very basic, using pulover's macro creator (AutoHotKey) which would just fire/repair the cannon, as well as eating food when health got too low, the clicks were always in the same spot and the same time apart, I ran the script for HOURS, at least 4 in total (I was babysitting it), and was never banned.
      6) Adding on to what was previously said, I also currently use a macro which switches my amour (Void Range/Ava/God Book/Rune Cbow > Void Melee/Fire Cape/Gmaul) and then it uses the special attack (all within 1 seconds :P), the mouse jumps all over the screen, moving at speeds not humanly possible, I've used it for months and still have not received anything for it, most games would detect this but RuneScape does not, you would've thought their amazing bot detection system would pick that up right?
      7) It is already known that breaks reduce your chance of being banned.
      Anyone got more to add?
      To put this to the test, I'm going to attempt to get 99 strength and 99 ranged, I'm only going to bot for max 6 hours per day, taking breaks every 1 hour 45 minutes, for 30 minutes.
       
      It's either this, or Jagex adds you to a list, and once you've botted too much that's when they ban you (I doubt this, they would more likely give you a 2 day ban).
    • By TravBot
      Howdy All
      Currently attempting to bot for the first time and using a premium hunter script, striving for that 99 and right now sitting on 84 =-) I feel i am careful when i come to botting my character, i mainly watch my botting screen because i play my other two accounts as normal|<< nerdy i know. so i am able to reply to all who speak to me within moments, along with having break handler set up and every now and again mouse clicking around the screen to change my mouse data patterns around.
      I ask this because of course 99 Hunter is great money, id much more envy the fashionscape of the 99 hunter cape and would onward play the character manually and level combat for a edge 13 pray g maul pker, noob life i know but sue me.
      Will i get to live out this little account dream set up or is it most likely in the end most botted accounts lose the battle against jagex =p
      If anyone has any info inside on the matter would be awesome if you discussed below.
      Happy botting <3 hahah
       
  • Our picks

    • This release will:

      Fix login bot after today's game update (Thanks @JoeDezzy1)


      Fix latest in-game world hopping issues (Thanks @erickho123)


      Compact Settings UI and set location relative to TRiBot (Thanks @JoeDezzy1)


      Fix an older implementation of GrandExchange#getWindowState (Thanks @JoeDezzy1)


      Improve the preformance of NPCChat by only searching in certain interface parents (Thanks @JoeDezzy1)



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      LG support for RuneLite


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 13 replies
    • This release will:

      Fix bytecode manipulation in order to prevent the modification of parameters within the Filter and Condition classes themselves (thanks @wastedbro)


      Fix NPE caused by non-null value in GE API (thanks @erickho123)


      Add and fix equals methods for api2007.types (thanks @JoeDezzy1)


      Modify Mouse#leaveGame to make the mouse leave the game from top, left, right, or bottom (thanks @erickho123)


      Add Entrana area to Ships API (thanks @erickho123)


      Fix raid prayers index/settings in Prayer API (thanks @erickho123)



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 29 replies
    • This update will:

      Implement better canvas locking/synchronization mechanism


      Fix small Login API bug


      Remove the requirement for xbooting Java classes


      Use ExecutorService to perform canvas work in parallel


      Add "Account Management" game tab to GameTab API (thanks @Encoded)


      Fix NPCChat#getMessage (thanks @Encoded )


      Fix NPCChat#selectOption (thanks @Encoded )


      Fix Banking API after today's update (thanks @Encoded )


      Fix in-game world hopper after today's update (thanks @Encoded )



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 38 replies
    • This release includes:

      Fix updater bug which was causing a bunch of issues


      TRiBot will no longer require manual hook fixes every time the RS client updates - the updater has been fully patched for objects


      Hooked login fields


      Improved the login bot


      Ability to recognize the banned/locked messages again


      Ability to read the current input for username and password fields


      If the username or password is already entered correctly, it won't be erased


      If only part of the username or password is already entered correctly, it won't be erased. The login bot will fill in what's missing.


      If there are a few invalid characters after a valid substring of your username/password, only (approximately) those invalid characters will be erased. The login bot will then proceed to fill in the missing characters.





      Coming soon:

      Skull icon fix


      Improve screen rate and responsiveness of the RS client (both regular client and LG)


      Much more
      • 33 replies
    • This release includes:

      Fix shift clicking option selecting


      Fix high paint delay settings saving


      Update prayer IDs for the quick select menu


      Remove RS3 support


      Fix hooks



      RS3 Support Removed

      The RS3 client hasn't been updated since our Old-School version of TRiBot was released, as many of you may have noticed. Keeping all of the RS3 code in the client made the client as a whole harder to maintain, larger, slower, and messier. As hardly anyone still uses the RS3 client, and since the RS3 API was hardly functioning, we made the decision to completely remove it from TRiBot.

      For the average user, this means that the client will be smaller, cleaner, and faster. Future updates will also take less work meaning there will be more frequent updates.

      If you were one of the few users still using the RS3 client, we apologize for the inconvenience. No future support for RS3 is planned. There are many other botting clients which has support for RS3, so we recommend finding an alternative if you wish to continue botting on RS3.
      • 25 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×