Welcome to TRiBot Forums

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

tried ex

Registered
  • Content count

    65
  • Joined

  • Last visited

  • Feedback

    0%

Community Reputation

-1 Poor

About tried ex

  • Rank
    Botter
  • Birthday 11/23/1993
  1. sfsss
  2. add me on skype if u need to buy
  3. bump sfs
  4. Hey Everyone. I have a ton of gold for sale right now and hoping to sell most of it today! Price is 2.4/M! Skype: matt.pbot I'm not going first, so don't bother trying to make me, as I'm done messing around with little kids!
  5. Just bought 40m 07 gp. I went first in 2 trades, thanks!
  6. Idk why, but my bot is randomly dying/stopping a lot. I come back up stairs to my computer to find it out logged out and sitting at dragons. It also dies a lot, but not sure why because I saw the bot just sit there and not eat when it had 6 lobs left. I still love the bot tho.
  7. Just bought the script. Waiting for A PM M8
  8. Hey runite, im posting to enter the contest. =]
  9. Does the client still interrupt the script when a strange plant comes up? or does this issue still exist?
  10. Trilez, you have to make it so the client doesnt automatically stop the script after random failed attempts. I say this because for example, if you are using a range guild script, there is the target window that comes up which the script closes. But if a random appears as soon as the target box goes up, the client tries to solve the random through the target box. Please try to implement a way to fix this problem
  11. redownload the script
  12. Randoms are being worked on by the administration, they know them not being flawless hinder scripts' ability to run. Its not that the client cant solve randoms.....it tries to solve the random through the target window, when it should close the window first. I know it can handle most randoms because i had 50+ hour proggies on other scripts (not range guild scripts) I'll suggest the addition of an overridable script method that gets called before a random solver runs, with something like that I could close the window Try to get them to implement it asap, your script is really good, its just that problem thats holding it back
  13. Randoms are being worked on by the administration, they know them not being flawless hinder scripts' ability to run. Its not that the client cant solve randoms.....it tries to solve the random through the target window, when it should close the window first. I know it can handle most randoms because i had 50+ hour proggies on other scripts (not range guild scripts)
  14. n3ss is there anything you can do at all to fix the randoms problem? mabye contact trilez or a mod. Anything that you can do at all, instead of just letting the problem last. This script is good only if you are babysitting.....i like to leave scripts on by themselves without watching them. You have the scripter rank now, mods will listen to you!!