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.

SDN Scripts Randomly Stopping/Not Working

Featured Replies

I've made this post before but it got locked and removed for some reason? This is a huge issue and is causing many people to yell at scripters for something that isn't even their fault. A quick overview of what's going on:

  1. Scripts do one loop and then stop (ex. click on a tree to cut it and then not do anything, pick one piece of flax and stop, etc)
  2. Script may work for an hour or so but then just stop
  3. Some features work, while others do not (despite working perfectly fine when run locally)
  4. The script works completely fine on select client versions, but not others

This bug does not apply to all scripts, just certain ones. If I can run my local script completely fine, but then get on the SDN and bug out DESPITE it being the exact same code I'm using, there's definitely something wrong. On select occasions I've even just made a small modification to my script, such as adding a comment (has no effect on the scripts execution) and then got it recompiled. What do you know, it worked perfectly after that besides NOTHING getting changed.

 

If anyone can add extra insight into the matter please post below.

Edited by Swizzbeat

I've made this post before but it got locked and removed for some reason? This is a huge issue and is causing many people to yell at scripters for something that isn't even their fault. A quick overview of what's going on:

  1. Scripts do one loop and then stop (ex. click on a tree to cut it and then not do anything, pick one piece of flax and stop, etc)
  2. Script may work for an hour or so but then just stop
  3. Some features work, while others do not (despite working perfectly fine when run locally)
  4. The script works completely fine on select client versions, but not others

This bug does not apply to all scripts, just certain ones. If I can run my local script completely fine, but then get on the SDN and bug out DESPITE it being the exact same code I'm using, there's definitely something wrong. On select occasions I've even just made a small modification to my script, such as adding a comment (has no effect on the scripts execution) and then got it recompiled. What do you know, it worked perfectly after that besides NOTHING getting changed.

 

If anyone can add extra insight into the matter please post below. I've also had this bug be confirmed by @Zach in the chat.

 

Scripts seem to work far way better when they're local. I'd probably prefer scripts to remain local. Saves a lot less hassle.

 

  • Author

Scripts seem to work far way better when they're local. I'd probably prefer scripts to remain local. Saves a lot less hassle.

 

Premium scripts cannot be local for obvious reasons :p

Premium scripts cannot be local for obvious reasons tongue.png

 

Yeah, forgot to mention that. I mean, Non-Premium scripts which are uploaded to the SDN should remain Local. The adding is still simple. All your doing is moving the file to a folder. It's so advanced these days you won't even need to go through the whole compiling process.. Premium scripts, well that's a different matter.

Too bad some people are to retarded to drop a jar in a folder... ^

  • Administrator

I've also had this bug be confirmed by @Zach in the chat.

 

When did I even confirm that bug? Looking at chat logs, it seems that I confirmed there was a problem with something deadlocking, which affects both local and SDN scripts. Let's not take a bug that was confirmed and turn it into something that only affects SDN scripts...

  • Author

When did I even confirm that bug? Looking at chat logs, it seems that I confirmed there was a problem with something deadlocking, which affects both local and SDN scripts. Let's not take a bug that was confirmed and turn it into something that only affects SDN scripts...

Ok, local scripts as well?

Recently Browsing 0

  • No registered users viewing this page.

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.