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.


$5 Donor
  • Content count

  • Joined

  • Last visited

  • Feedback


Community Reputation

241 Excellent


About FALSkills

  • Rank
    Extreme Botter


  • Sex

Recent Profile Visitors

1,813 profile views
  1. Description of the bug (be specific): The client will run into OOME most likely due to memory leaks. I am running a script using the following code: @Override public void run() { while(true){ sleep(5000); } } and refer to it as "empty script" below. How often the bug occurs: It varies upon method and location, however it seems to always happen eventually. Triggers of the bug (if known): Areas with a high volume of objects (jungle areas, swamp areas) seem to cause the client to run out of memory quicker. Java version: 8u101 Max Heap Size: 386 (I’ve tried increasing it, it only prolongs the inevitable.) TRiBot client version: 9.303_6 Looking Glass (yes/no): no Operating System: Windows Server 2008 R2 Enterprise, Standard, Datacenter. Windows Server 2012 R2 Enterprise. Probably the others as well, however those are the only ones that I have tested. Script Name: N/A TRiBot Old-School or RS3: Old-School Client Debug: The client does not have enough memory to copy it from it. I have included screenshots of debugs below. Bot Debug: Screenshots (if any): With empty script: https://gyazo.com/b568a342ad2ba4651609401855bf9ac6 Plenty of other pictures that I could provide, but here’s another: https://gyazo.com/2d2dd6a248f21784d421a32341298456 And a heap dump, however I’m not quite sure what info is useful to you so let me know and I can upload it somewhere. https://gyazo.com/9f162db7b174b631a4e741c122409356 I am happy to gather whatever additional information may be necessary. This issue has been a pain for a few months or longer now.
  2. Performance-wise it works. It isn't flawless and it isn't super efficient, but it works. There is much discussion in regards to its efficacy, and I personally think that it does indeed reduce the banrate significantly. However it comes at the cost of being 2-3x less CPU efficient as well as memory issues which causes it to deprecate and crash within a day usually.
  3. If you are trying to bot a main, it's quite unsafe unless you have experience. If you are trying to bot for money, you will probably lose money unless you have or get experience. There are always exceptions though.
  4. Yeah botwatch is down currently or weath is out of the office, either way now is not a good time to determine banrates as it will likely go back to normal soon.
  6. ABC2 actions occur much more frequently if trackers are being generated.
  7. Tribots webwalking only really works well in f2p areas, and even then some areas have been updated in game but not on the walker. Walking class is fairly good for walking short distances however it isn't the best for navigating around terrain/in game paths. You ideally would use a variety of the walking classes which include Walking, WebWalking, PathFinding, and DPathNavigator. The Projection class can also be useful.
  8. It actually uses more than double a regular client, probably closer to triple with both the regular client and a LG-compatible client (OSBuddy)
  9. Instead of using multiple tabs, use multiple clients.
  10. Locks from tutorial island are typically from a combination of: Botting tutorial island Using a flagged proxy to do tutorial island Sounds like you are (potentially) doing both!
  11. Pretty sure those are a waste of time to bother changing. I mean I assume bans will happen with most of the accounts I run since I run many mass methods, however I also run accounts that haven't been banned in 1.5 years+
  12. Bump
  13. I'm not sure, but you can try higher numbers and see how it works out!