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.

FrostBug

Scripter III
  • Joined

  • Last visited

Everything posted by FrostBug

  1. We have a winnar
  2. about 75 I think
  3. Started a trial Strange, first time I've ever seen this. Did you use different settings than you normally do (kill order for example, or a different 'correct tomb last' setting?) Also, was it actually the correct tomb (for dharok)?
  4. Interpret it as you will. I haven't tried it on the new mirror release yet, but I don't see any reason it shouldn't work anymore. 24 hours
  5. I think mirror client is now at the point where I'll start running tests with this script. I will also start to look into bug reports from mirror client related bugs.
  6. Started a trial for you
  7. Your memory appears to be completely maxed out (lower right corner). That'll freeze any script. Try allocating it more memory
  8. You can't sort a hashmap.. It's hashed.. A priority queue would be your best bet IMO, depending on the situation ofc. Make a wrapper class to hold your 2 ints, let the wrapper class implement the comparable interface (compare by key value), and they'll be automatically sorted as you insert them into the PQ
  9. Alright, here's what's gonna happen. All of you are gonna restart your scripts right now (hit the refresh scripts button to be sure) And then they're gonna run without any problems! If there are any problems after that, please fill in the bug report template located in the first post. Thanks
  10. That's not up to me, unfortunately. I have no authority to do so Version 1.2.9c has been committed to the SDN. this version contains temporary workarounds for the broken client hooks, as well as some more workarounds for the 2.3.77 interaction bugs. These will have to be reverted once the client hooks are fixed; but that should not break the script.
  11. I was merely testing you.. You passed
  12. Well.. I had assumed he was black Now.. there was mention of photographs? Surely you'll provide said evidence?
  13. legit
  14. Hadn't even noticed
  15. the bugs have both been approved and can be tracked here: http://osbot.org/forum/topic/76612-2377-charactergetinteracting-broken/ http://osbot.org/forum/topic/76494-2377-tab-switching-for-interactions/ We can probably live without a fix for the 2nd bug, as I've already committed workarounds for them. We cannot continue until the hook for checking who an NPC is interacting with is fixed.
  16. Update: I've pushed more workarounds for the 2.3.77 client bugs. However, after the runescape update today, a hook has broken. As a result of this, the client is unable to tell what npcs are interacting with, and in turn, the script cannot determine which brother is yours. Hooks are usually fixed relatively quickly, tho. You don't.
  17. dis is a pretty qt ladybug :3 But it's not a frostbug ;o. Frostbugs are blue/cyan
  18. I've committed some workarounds for the interaction bug in client version 2.3.77, specifically for some interactions when digging and banking. The version number is 1.2.9a, and once again, we will have to wait for the SDN manager to update the SDN.
  19. The SDN is down atm. That error occurs on every single SDN script.
  20. Seems there's a pretty fatal bug with a couple of vital API interaction methods in the client. I'll post a report to the devs in the appropriate section for now, since I unfortunately don't have time to go thru every interaction and add a workaround (not that it would take particularly long, but it's really late already) If you still have client version 2.3.75, you should still be able to run the script fine with that. Sorry for the inconvenience
  21. Version 1.2.9 is now live
  22. I imagine this would have been hard on you, if not for the fact that you are extremely patient
  23. For some reason it's still not live; I'll try to get in contact with the SDN manager

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.