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


Premium Scripter
  • Content Count

  • Joined

  • Last visited

  • Days Won

  • Feedback


Everything posted by Einstein

  1. if (item.length > 1) { doSomething(); } else { doSomethingElse(); } In the above code, the if block is executed if there are 2 or more items in the inventory. In any other case, the else block is executed. Since you can't have a negative amount of items in the inventory, "any other case" means having 0 or 1 items in the inventory. Any of those values will result in the else block being executed. As far as I can tell, you are trying to make a decision based on the availability of a certain item. If so, you could either do what @Zully suggested and evaluate the expression item length >= 1 , or check if there are more than 0 items available: item length > 0 They both translate to: "if there is any item in the inventory, then...".
  2. Thank you for the report. Can you please send me a screenshot with the exact location (tile) where this bug is occurring?
  3. I agree that continuing the course after the player runs out of food is a problem, and a solution to it will be included in the next patch.
  4. The value is already randomized. This will be added in the next release. Toggling run is handled by ABC2 and it should have a broader spectrum of values. @Bottingman9000 Thank you for the rest of the reports. Hello Mr. Karuz0. You're welcome. Thank you for using my software. At the time of writing there is no additional support for waterskins. The script will simply stop after it runs out of water. If you would like to limit the amount of pyramids that will be kept in the inventory, simply get more waterskins to fill up the inventory. The number of free inventory slots will determine the maximum amount of pyramids kept in the inventory before selling them.
  5. Not yet but it will be included in a future release. Of course.
  6. A facility encouraging the consumption of alcoholic beverages. https://oldschool.runescape.wiki/w/The_Sheared_Ram
  7. - Naton has been detected - Nice job man, the repository really needed such script. The proggies are also very impressive.
  8. Nope, it's Jagex that is banning you. Jokes aside, detecting this script through data mining would require at least several hours of playing data to analyze. If you've been banned within the first 10 minutes, it's nearly impossible that it was due to the script and there might be other factors that determined this outcome. Once again, fresh level 3 accounts in F2P are not exactly the best choice if the goal is avoiding detection.
  9. Yes, it is. I've already explained it in my previous reply to your comment:
  10. This is the most common outcome for fresh level 3 accounts, especially in F2P.
  11. Not necessarily. Follow a Woodcutting guide and select an appropriate tree for your level. However, I highly suggest that you do not exceed 4 hours per day (the less amount of time, the safer). Use breaks and train other skills every few days. Keep in mind that the average legitimate RuneScape player can barely do the same activity for two hours straight, without getting bored.
  12. This fail-safe allows the script to accurately determine whether the account is in F2P or P2P, information which is used internally for several things. It's already handled by TRiBot and it's called "fatigue". Tick manipulation will not be added to this script, or any of my scripts for safety reasons. Sure. First of all, level 99 is definitely achievable, many users have managed to get to this level. However, you must be very careful with the amount of hours / day in order to minimize the chances of detection. Don't try to achieve it as fast as possible. 34k experience / hour is not "painful", because you don't have to stay in front of the screen while the script is running, and you can do something else instead. Sure, it might take 2 months to reach your target, but I would rather be patient and keep my account relatively safe.
  13. Not all Java versions are compatible with Looking Glass. Refer to this guide:
  14. Thank you for the report. This issue will be addressed in a future release. Dropping is based on my own recorded data, on which I spent 2 hours manually dropping logs. It's not "random", because humans are not random. But it does have a certain deviation from the sample pattern, which is applied every time the script drops a new item. Of course it seems like this. Humans are unable to see differences of tens of milliseconds just by looking at the cursor. If you are instead referring to the fact that the dropping sounds are generated at a fixed rate, once every 600 milliseconds, that's because items cannot appear on the ground between game ticks. This is not related to this script, or TRiBot in general. This is how RuneScape is coded.
  15. Then scripting shouldn't be any challenge. TRiBot is capable of executing scripts written in Java. If you are not already familiar with the language, I highly suggest learning it. In your case it shouldn't take more than a weekend. After you're sufficiently proficient with Java, skim through our API: https://tribot.org/doc/ Avoid using any frameworks when you are writing your first scripts, and instead focus on the fundamentals. Learn about the various types of in-game entities that you can interact with. Write a few basic scripts that perform easy tasks such as picking potatoes or cutting down trees and banking the logs. Increase the complexity of your scripts gradually, as you gain more knowledge and experience.
  16. Are you sure that's the message being displayed? What is your woodcutting level, and what is the axe you are attempting to use? Do you run the script in normal or progressive mode?
  17. Thank you for the suggestion. The script does not interact with the bank in any way, at the moment.
  18. Try increasing this number to 500MB per client, and only use one tab. This limit can only be set when starting TRiBot, on the same window that prompts you to enter your username and password.
  19. @ColoredHacks What is the maximum heap size allowed for the clients?
  20. Walking is handled by the client and I do not intend on changing this. If the possibility of getting reported due to high competition is a concern, please use the script in remote locations with world hopping enabled. If you configure this feature to 0 players tolerance, it will hop as soon as someone gets nearby, making reporting nearly impossible. Choosing the next target is also handled by the client, by the anti-ban compliance utility to be more specific. I consider this method very valuable when it comes to preventing detection due to it's partial unpredictability. This will not be changed in any future releases.
  21. The script will simply use what it has, prioritizing the cheapest method: staff > runes > teleport tabs > no teleport If there are no teleporting items available, the script will not teleport. Currently, the bank is never accessed in any way by this script. I said 'currently' because the upcoming golfarming mode might need to do so, in order to gather any additional marks that might be kept in the bank.
  22. Unfortunately, login related issues are occurring on the client side and this script has no control or influence over them.
  23. VIP is being displayed automatically for all the VIP-E users. If however you have more VIP days than VIP-E days (shown on this page), I don't think you'll be able to get a refund, but you could upgrade to VIP-E after the current month is over, by paying the difference ($1.5).
  24. pls d0nt abuse this method & crash the market
  • Create New...