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


  • Content Count

  • Joined

  • Last visited

  • Days Won

  • Feedback


erickho123 last won the day on July 28

erickho123 had the most liked content!

Community Reputation

2,452 Excellent

About erickho123

  • Rank
    Back and going ham =)
  • Birthday 01/16/2013


  • Sex
  • Location
    Gender fluid
  • Bio
    Welcome to my profile. I have been a premium script writer over at TRiBot for nearly 2 years. It's been a blast, and ever since then I've been able to accomplish many achievements.

    I have achieved:
    - 9k+ posts
    - 200+ feedback
    - Over 30k+ users using my script
    - $100,000 worth of trades on TRiBot
    - Support team
    - Proud author of many original and unique scripts on TRiBot
    and much more!

Recent Profile Visitors

32,933 profile views
  1. Megabank refuses to reply and has banned for scamming. Sorry for your loss, consider accepting BTC or another irreversible payment method in the future.
  2. Sounds like you dont have account selected in account manger? Try 30-35 second delay in the GUI settings. Seems to work for most. Also, try this new option I just added. (I suggest only enabling one or the other), but there is now an option to stay logged in for x amount of seconds before it world hops. In the mean time, the script will still buy/sell items. So now instead of sleeping, the script will operate.
  3. I hear if you set delay to around 20 seconds, it should work. Apparently you get 10 world hops, and every 30 seconds, you get another. I don't know how true this is. It works fine for me, but there was a bug in the IGN world hopper. I just fixed it. Can you try again? Also, you may have to increase the login delay. There was a bug with IGN world hopper, should be fixed.
  4. @megabank, please respond. As well, do you have pictures of the unauthorized transaction? PM me it if you are not comfortable posting here. Also, private messages on tribot would be helpful
  5. As people are aware, Jagex seemed to nerf world hopping by limiting number of logins and increasing the exceeded max logins timeout by 5+ minutes. The latest update that I just pushed slows down world hopping (with antiban), adds sleeps between hops, and also waits longer before clicking login to prevent refreshing the login cooldown. These options will become optional in the future, once more data is collected. Hopefully with this update, y'all will be able to run your shopping bots again! Edit: Looks like the longer click before clicking login won't work at the moment, because TRiBot added support for the login message (finally), but now it clicks it every 5 secs... Will file a client report about it lol Edit 2: It's now optional and you can determine how long it should sleep for now. It is in world hop settings.
  6. Yeah, monitoring closely.. Looks like they might've unintentionally nerfed world hopping buying. May also experiment with slowing down world hopping, but even with slow consistent world hopping, u can still get hit with the login prompt
  7. You can try using your own clicking methods if the default tribot API clicking method is too inaccurate for you. Or you can increase mouse speed
  8. Yes, there are multiple ids for items with same name. In fact, this is why I opted to use ids over names, because there are multiple items with same name that a user can have. For example, noted items have same name. The list is simply to help you find item ids, but you can always grab the EXACT item id of your inventory by going on top of TRibot, clicking debug and then inventory. This will overlay the exact item ids over your items in your inventory. I'm not saying you're retarded or stupid, but the reason why it could not find the strength potions is because the wrong item id (or rather wrong verision of the item) was inputted. i actually understand why item ids can be non userfriendly, so that's why I added the automatically import items for ya. Also, I just ran the script. I recommend restarting your TRiBot client because the script is working fine. Sometimes the client proposes issues that messes with EVERY script, and restarting the client once or twice fixes the issue. There wasn't a script update or runescape update to justify the script randomly breaking internally, so it might just be a client error. The script itself is very stable and hasnt been broken from any kind of runescape update in ages.
  • Create New...