Jump to content

Einstein

Premium Scripter
  • Content count

    1,692
  • Joined

  • Last visited

  • Days Won

    87
  • Feedback

    100%

Einstein last won the day on June 20

Einstein had the most liked content!

Community Reputation

750 Excellent

About Einstein

  • Rank
    E = mc²

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. You can achieve that by using the break handler. Edit: 'd
  2. Einstein

    Cant type in GUI

    Minimize and maximize TRiBot. If it still doesn't work you will need to restart the client.
  3. Einstein

    CLIENT NOT WORKING (HELP PLEASE)

    Try deleting the whole .tribot folder and restarting the client twice. On Windows, the folder is located here: C:\Users\UserName\AppData\Roaming\.tribot Make sure to backup accounts.dat and other files you might want to keep.
  4. Einstein

    Still cannot bot

    Problem solved via PM. User had to download JDK 102, OSBuddy cross platform version and allow TRiBot to execute (antivirus/firewall).
  5. Einstein

    Still cannot bot

    It's not excluded that every proxy provider you've tried already had their IP range flagged. Most likely this is the reason for your ban, but this is a good opportunity to make an experiment regarding Looking Glass usage. Looking Glass makes code level client detection virtually impossible. If you're still getting banned within minutes, while using Looking Glass than it's confirmed that your providers are blacklisted. Please go ahead and try it. I am very interested in the outcome. Here is how to get started with Looking Glass, if you can't get it started send me a PM or add me on Discord Einstein#9305.
  6. Einstein

    Still cannot bot

    Bans that occur within minutes generally indicate a flagged IP address. Even with their advanced data analysis system, they cannot precisely determine if a player is a bottling or not based on a few minutes of script input. Since they clearly didn't ban you based on the script's heuristics, they either did it based on your address (or other unique identifiers), or they actually managed to somehow detect the client on the code level, which could be disastrous. Edit: I am very interested in this. @asiliukas123 can you please bot using Looking Glass and tell me if you're getting the same results?
  7. Einstein

    Tribot Chat

    https://discordapp.com/terms
  8. Einstein's Woodcutter has been updated. Custom random event dismissing system. The new implementation takes into account all the anti-ban delays. It's much more reliable and it is guaranteed to keep the script running, even if it fails to dismiss the random from the first attempt. Beaver support: the script will not drop it if you already have a follower and it appears in your inventory New axe switching handling that will only deposit your axe, instead of all the worn equipment. @sgt p0wned Thanks for the suggestion. Infernal axe support: Woodcutting / Wielding / Special Attack The walking utility has been updated with a fail-safe system. Enjoy!
  9. Both choosing the next clicking target and deciding if and when the bot should walk to the anticipated target are still chosen by ABC2, and I do not plan to alter this behavior in the future. As far as I can tell, ABC2 does not choose a random target from the given array, but instead it returns the closest target: usually, but not always - just like a real human would do. My new algorithms are not choosing the next clicking / anticipated target, but instead they are choosing the tile to click in order to walk towards the already chosen target. They replaced fixed tile clicking, which is many, many times better in terms of preventing detection, because humans are a lot less accurate and precise. The new functions are attempting to replicate this lack of accuracy and precision, as well as the human tendency to aim for the center of a target:
  10. Einstein

    [Windows] Delete hooks.dat and the Jagex Cache

    I'm glad you like the script's name
  11. Windows script that deletes hooks.dat and the Jagex cache TRiBot can break on multiple levels. Script issue Client incompatibility with a new RuneScape release Networking problems Underlying JVM problem Other user-caused errors Most of the time, inexperienced users that encounter any kind of problem on any level, that makes the client load but prevents the script from working, are jumping to the conclusion that the script itself is broken, and they proceed to spam on its thread, or in some cases, they even start additional threads in which they ask how to fix the script. A very large number of those problems can be easily fixed by deleting a few files and restarting the client twice. Since the overwhelming majority of the users that do the things described above are very inexperienced with computers, here is the easiest way possible to delete all the files just by double clicking an icon. Download: This script will: Close all running instances of TRiBot Delete hooks.dat Delete the Jagex cache Prompt the user to open TRiBot again and then close it, ensuring that the client was restarted twice
  12. Updated Today's update comes with improvements in the script's anti-ban. Some very important changes were made. I expect to see a drastic decrease in ban-rates. In-human pattern I have identified a huge flaw in the code that generated a profoundly in-human pattern. Although it consisted of a single line of code, the fact that it was executed frequently and consistently when a certain condition was met, made it relatively easy to detect. This was completely removed in today's update. New tile choosing algorithm - Tree not on screen The new algorithm takes into account the number of tiles occupied by the tree (in this case 4). The occupied tiles are also selected by the algorithm, because the result does not represent the exact location of where the player should be; it represents the tile on which the script is going to walk towards, usually by clicking the minimap, until the tree appears on the screen an it can be clicked. As can be seen, the script will click more often (but not always) in the center, because this is how humans are usually walking towards their target. ← Minimap ↓ Game screen New algorithm for next anticipated target The tile choosing algorithm for the next anticipated target has been changed as well. The tiles occupied by the tree (or the stump) are excluded, because the output of the algorithm represents the exact tile on which the player should be on. Camera movement Has been temporarily removed, and it's currently being handled only by TRiBot's anti-ban. Rest assured: no input at all is many times better than in-human like input. This week I will be working on a special utility that will imitate the way in which humans are moving the camera to find their off-screen target. This will take some time to develop, because there are a lot of variables that need to be accounted for and it also requires collection and analysis of real human playing data. Camera movement will be re-introduced as soon as this utility is ready and I am completely convinced that I successfully managed to replicate the way in which real humans move the camera towards their target. Today's update consisted of very important changes, and I expect to see a drastic decrease in ban-rates.
  13. Do you get any message in the bot/client debug? Try starting TRiBot in Console Mode and post the results.
  14. Einstein

    Looking glass cannot find OSbuddy client.

    Only certain JDK versions are compatible with Looking Glass. If you updated your Java, the newer version is not guaranteed to work. Your antivirus / firewall might prevent Looking Glass from functioning as well. I wrote a guide on how to use this feature and how to solve the commonly encountered problems: Here are a list of Java versions that other users manage to hook Looking Glass with:
×