Skip to content
View in the app

A better way to browse. Learn more.

OSBot :: 2007 OSRS Botting

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Molly

Members
  • Joined

  • Last visited

Everything posted by Molly

  1. Np, I understand the situation is frustrating. The script will be updated to v2.2, about to push the update. When you see v2.2 on the paint you will know its safe to run. This could take a bit of time, a dev/admin has to update the SDN before the script update occurs. The issue with looting has been fixed with a work around, the issue is actually caused by the following situation: -Big stack of loot(4+ items). -Item desired to be looted is at or near the bottom of the list of items when you right click the pile. The work around will insure that if the looting does fail, the bot will blacklist that tile for some time so it will not keep attempting to loot the item. The interact command for some reason will still attempt to interact for roughly 20 seconds before returning a false however(I will be reporting the issue to the devs as it is a client, not script issue), to counter this issue and avoid deaths set your eat hp to something reasonable, don't have it only eat when its already low health.
  2. Okay, so I have issues with a script of mine looting under the following conditions: -Big stack of loot(4+ items). -Item desired to be looted is at or near the bottom of the list of items when you right click the pile. Looting works fine for every other imaginable scenario, however when those conditions are met the bot will click on the tile on the minimap multiple times(assuming it's attempting to loot?), this goes on for around 10-15 seconds before it moves on from the interact command in my code. What I have done as a temporary fix is added an if statement that is essentially: if(item.interact("Take"){ log("success"); } else { log("failed, blacklisting this tile); //adds tile to a blacklist, which resets every 30-45 seconds } This solution works fine for blacklisting tiles I don't want the bot to bug out on because of the problem. The issue however is the 10-15 seconds of basically downtime while the bot attempts to execute the interact command, it doesn't just try once and return false, it tries multiple times before returning true or false. Does anyone have any suggestions that would help me out?
  3. Just wanted to stop in and let you know how the update is coming along, pathing has been reworked to include more waypoints to prevent stucks(tested and working well). Issue with looting occurs when there are 2 of the same item on the ground, it seems to be a client issue and not script related, I am making a work around.
  4. Thing's happen that can break scripts, there is nothing that I can do outside of fixing the script when it is broken, which I attempt to do within 24 hours of bug reports. I'm not sure why you decided to run it over night after we spoke about the issue and it had yet to be fixed, I would advise not running it on any other accounts until I post here later today confirming a fix and the version number is updated when running the script.
  5. Thanks for the bug report, will fix it within 24 hours.
  6. Molly replied to Molly's topic in Thieving
    I would break every few hours, do other things as well to level the account. A level 3 thieving all day looks like a bot. Auto login is not script related, that function is handled by the client.
  7. Molly replied to Molly's topic in Thieving
    Looking into issue now. Edit: I am having no trouble at all with the bot, master farmer thiever is eating just fine. Make sure you are running it in Draynor and the gui is filled out correctly, I would be more than happy to do a teamviewer session with you to fix any issue you are having.
  8. Magic of all things too, as if you can't just afk splash to 99 and avoid the risk of a botting ban entirely....
  9. I was wondering this too. Do you intend to crash it so you can buy up a bunch of low priced items and merch them, or are you just doing it to say you can?
  10. Molly replied to Molly's topic in Thieving
    Thanks for the feedback man, bring option is for when pickpocketing master farmers, it is the amount of food to bring. The script does have a fair amount of antiban, though the chance for it to activate may be a bit low, which is a very easy fix. Pickpocketing intervals are random so occasionally it may pickpocket twice within a second(hope I understood what you meant, if I misunderstood it please let me know). The final 2 issues,GUI and paint issue, are easily fixed. Thanks for pointing out specifics normally I either get feedback of "this works great" or "this doesn't work" with no real description of whats good/bad, nice to have some constructive feedback. Yes.
  11. Thanks, I'll take a look into this asap.
  12. Any program that plays the game for you without the need for you to provide input can get you banned.
  13. Molly replied to Joseph's topic in Archive
    While true this can easily be countered, if scripts are made to simulate actual human behavior as opposed to maximum efficiency they will generally be harder to detect. You will still have the guys that run a plank maker for 20 hours a day and get banned because of it but it will help the people who bot intelligently. The people who change up what they bot, and don't bot for extensive periods of time will become far harder to detect as those patterns will take significantly longer to form. To take this one step further, if one were to develop scripts where a profile could be loaded in, such that the human behavior that is simulated is unique per user then detection would decrease even further.
  14. Sorry I was wrong that does actually work, forgive me its 4 am and I am exhausted lol. I'm not exactly sure why you are having difficulty looting. I'll look over your code real quick and see if I can spot something.
  15. Ahh ok, I reread the OP and it looks like the way you're reading in data only the very last string entered is put into temp.
  16. Try this: for (int i = 0; i < temp.length; i++){ if (groundItems.closest(temp[i]) != null) { GroundItem loot = groundItems.closest(temp[i]); loot.interact("Take"); } } Obviously you'll want some other stuff, like to check if your inventory is full, failsafes to make sure it does loot etc.
  17. Instead of: nextAttackLevelXp = XP_TABLE[currentAttackLevel + 1]; xpTillNextAttackLevel = nextAttackLevelXp - currentAttackXp; You could do: xpTillNextAttackLevel = skills.experienceToLevel(Skill.ATTACK);
  18. Molly replied to Jack's topic in Others
    I lul'ed.
  19. Sorry for the slow response, working fine for me. Only fix needed was changing the names of a few herbs for price grabbing due to Zybez changing the way they named clean herbs. http://imgur.com/HaF788v
  20. Osbot wouldn't exist, because if all of us were sent back to our mental state at the time of our starting of runescape that means the devs would have no or very little knowledge of programming(assuming they are in their early-mid 20's or younger). /thread
  21. I'm pretty stoked for it, sadly I have a class in the morning I can't miss so it's going to kill my gains =(.
  22. I'm not shaving my nuts this month, does that count? Inbox me for pics!
  23. The word "kid" is an insult.
  24. Molly replied to Molly's topic in Thieving
    NOW ACCEPTING OSRS GP AS PAYMENT: 3M Inbox me to pay with osrs gp, I will provide you with my skype.
  25. Something like: if (willowTree != null && !myPlayer().isAnimating()) Should ensure that you only chop a tree when your character is not already animating. As for your second question I''m not sure exactly what you are asking.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.