Jump 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.

Novak

Members
  • Joined

  • Last visited

Everything posted by Novak

  1. I need around 3 beta testers for my tanning script. Your job will be to: -report bugs -get proggies > 3 hours -give suggestions -anything else i need If you are a beta tester and you are successful at these things, you will get a free copy of the script when it goes on the SDN. Things to know: -the jar will be obfuscated. don't like it, don't ask for a beta spot. -it will contact a website to get a boolean of whether the script is still in beta. if the boolean is false, then the beta is over and the script will no longer run. post here/add me on Skype to discuss. Skype is in my siggy
  2. the_legend
  3. The first person to get a 10 hour proggie with Auto Magic Pro wins 500k. Post it here, then pm me to arrange payment. Alching/Stunning is probably your best bet, as superheat may have a few bugs as well as stun-alching. Good Luck!
  4. tbh mine isn't even updating, i guess we will have to wait until a dev sorts this out
  5. almost ready for release! Just getting the 2 hour proggy
  6. *cs on twitch :P
  7. what OS X version do you have? it opens fine for me on 10.10.1
  8. plss stop making videos like you are good
  9. Enchanting finished, should also finish stunning tonight, look for a release soon!
  10. when you sign in it is automatically loaded from the SDN. just hit start script and they should pop up automatically
  11. Update: Coming along smoothly, should be done this weekend!
  12. Novak replied to scape's topic in Resolved
    antiBan.unregisterAllBehaviors(); right in the docs
  13. Novak replied to Korra's topic in Spam/Off Topic
    lmfao what
  14. Update, Superheat core complete, testing next day or two
  15. in the OP i state i am using a for loop that sleeps until inventory.contains is no longer true, so it wont exit that loop until it is false OR it times out at 5 seconds
  16. no. im saying the inventory.contains does not update its value(true/false) for a long time after it is actually true/false. example: i deposit item A into the bank from my inventory. when the item disappears, inventory.contains should be false. instead, it is still true for another couple seconds, slowing down the script
  17. wants a quest script. /thread
  18. sure, but you are arguing over a minimal cpu hit which is not what i am asking. I am asking why .contains is getting updated so late after the inventory has changed. calling it over should not affect what the output of the call is and also: yours says if inventory contains item: sleep for 5 seconds, because there is no condition for the for statement except that i is less than 100.
  19. no, but is it really faster than the manual mouse moving I wrote using mouse.move? and does it check to make sure the items have come/left the inventory within 50ms? please explain how it calls it 100 times? the 100 is just for the timeout, if i is less than 100 AND our inventory still contains the item, then sleep for 50. Obviously if the item has left the inventory then the for statement no longer executes because the second condition isn't true.
  20. still literally the same thing as OP, it will still be slow cause its using the same .contains method, and the inventory will not be empty after depositing
  21. but thats not the point, my point is why does it take so long for it to update, this method worked perfect for osb1, it would respond as intended.
  22. that is literally the same thing as my OP, just with an unneeded if statement

Account

Navigation

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.