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


Popular Content

Showing content with the highest reputation on 12/10/2018 in all areas

  1. 1 point
    Around the forums you may see the phrase "bot smart," this is a guide with various steps for you to follow while botting to reduce the chances of a ban. It should be said, botting is against the rules and by doing so there will always be a risk involved. These tips are not intended to be used with goldfarming setups or accounts, most of this is speculation based on my own personal testing and data gathering. Botting Rules (If you intend to bot smart) You must follow these steps, else you will not bot smart. Do not bot on an account you can not stand to lose. Botting is inherently risky and a ban is always going to be possible. You must decide whether what you stand to gain from botting is worth the risk. Only you can make this decision. Do not bot on fresh accounts. A fresh account refers to any newly registered account, or any old account which has not been played regularly in recent times. Fresh accounts are watched much more closely, likely as they pose more of a risk to the economy as they are used for gold farming a lot. Hand train the first 300~ levels and do some quests! Botting should supplement your game play. Botting is no longer supposed to get you from 1-99 Agility, running a bot this long will just about guarantee a ban. You must switch up what and where you are botting and don't bot the same skill for multiple hours. You should play legit, its easier to determine a human than a bot. As supplementary info to the above: you should play legit, Jagex knows when accounts are 90%+ botted and will permaban these accounts without a warning ban, if you play legit some then often your bans will only be 48 hour temp bans. Like I said why are you playing RuneScape if you're not here to actually play it? Understand the ban routine, and what it really means. When your account gets banned, it does not mean you just got caught and banned. It really means they caught you at some point, likely within the past 7 days, and waited some time to collect more data (such as how your character acts) which could help them detect other bots in the future. Do not bot on an account coming off a temporary ban or it will be permanent next time. Join in on chats going on around you. If you're at your PC while botting (maybe you're doing some work) then you can participate in clan discussions, and respond to people ingame. An account that randomly talks whilst botting is still less likely to get permabanned than if you never interact at all. Also enable Auto-Responder in TRiBot settings and it will respond to level inquiries, etc. Don't always pick the optimal spots. Are you woodcutting? Perhaps doing it at Draynor village with 20 other people isn't the best place. Assuming 15 of those other people are bots, the 5 legitimate people will get very annoyed and report all of you for slowing their XP down. You should pick a spot where your XP might be slower, or the bank might be a little further, but you have less people around to worry about. Do not use RSBot/Epicbot ever! Jacmob and Mod MMG specifically stated that their botwatch system is specifically tailored to RSBot and Epicbot which are both based on old RSBot 4 code, most of their interactions or hooks are outdated and they don't have any active API work being done. In short: it is much more easy to get caught botting using RSBot and Epicbot. Miscellaneous Rules Here are some further tips: Never post your RSN on a botting website. Jagex Staff and Player Mods will frequent these boards and have been known to ban people if they have sufficient proof. If you've just had a 2 day ban, the next one will be permanent. AND your account will be watched closer. You should not continue botting this account. If you're botting on a VPS you should use a VPN. No one is playing on a VPS legitimately, and it's not hard to figure this out from the IP alone. Providing you're not on a Windows VPS your operating system should not be too much of a giveaway. However, the fact you're playing on a machine without a monitor attached is probably not hard for them to notice either. Do not click Runescape links on forums. When you click a link it will send data of the page you came from, also known as tracker cookies. Banned? Clean yourself off Got banned? Clean yourself off before you continue. What we mean by this is, you need to wipe down anything that Jagex may use to associate your new account with your previous one. However, this is speculation and may not help. Clear your Jagex Cache ( support.runescape.com/hc/en-gb/articles/205842582-How-to-clear-your-RuneScape-Cache-on-a-Windows-PC ) You can clear browser cookies and attempt to acquire a new IP address but these likely won't help unless goldfarming.
  2. 1 point
    There's no problem with using the pre-defined filters within the "Filters" class. As long as you're not creating your own Filters, it's fine. If you need to create a new filter, use Predicate instead.
  3. 1 point
  4. 1 point
    Bought 3 proxies from @Fluffee, 1 shared, 2 private, and all working perfectly. Had terrible luck with past proxies (bans and whatnot), but none so far with these. Would highly recommend this service. Very quick with responses and willing to help you with any problems that may arise.
  5. 1 point
  6. 1 point
    Hey guys, After a long break, I decided to make a progressive chopper as a first script to re-start off with scripting. Got myself 1-66 woodcutting while testing it. Progress: Screenie 1 Screenie 2 Screenie 3 Source code: Github Activate it over here. Current features Supports normal trees, oak & willow. Automatically switches tree in Lumbridge area. Power-drops all kind of logs Upcoming features Bank support in Draynor/Falador/Varrock (most F2P area) New dropping pattern (keyboard alt + clicking) Better paint and antiban Dynamic signatures/tracking system + hiscores Mule support A Surprise is to be announced later on. Code improvements and suggestions are appreciated Best regards UKF
  7. 1 point
    I will only cover the critical issues: When getUserData is called, there is no guarantee that the required game data has been loaded. The script will show incorrect values if it's started on a newly opened client. A small delay should be added in the script's main loop. It makes more sense to update the variable action_state at the beginning of the loop, instead of having it on the last line. Storing the result of getActionState() in the action_state variable, then using this cached value is better than calling the method 5 times in the main loop, whilst the variable remains unused. tree.getDefinition() != null && tree.getDefinition().getName() != null - There is no guarantee that the second RSObjectDefinition will be non-null. This value should be cached, null checked, and only then it would be safe to use. But in this particular case, you can delete the entire line because it doesn't serve any purpose other than increasing the likelihood of the script crashing. All the static sleeps must be immediately removed. Thanks for your contribution. Looking forward to seeing your progress in scripting.
  8. 1 point
    A small update has been applied to hopefully improve mound clicking accuracy.
  9. 1 point
    Update 08/12/2018: - Pushed an update that should now close unexpected dialogue when miss clicking an object. - Mythical capes are now supported after a request from a user. Due to how this object works, you must start with the cape in your inventory. It will not bank for it, and it must also be the only trophy space built in the loaded region. Oak dungeon doors should be added next update. I'm 2 levels away .
  10. 1 point
    And there it is, 99 smithing from this script 60 -> 99 running 24/7 with steel bars, week long progress report, decent amount of profit, will be using this again