It's time to combat broken scripts. We can use the forum to do this.

[liverare]

• OSBot users are required to log into their forum accounts to use the bot.
• Each script stored on the SND has a thread post associated with it.

It shouldn't be hard to implement a feedback feature within the bot itself where users can rate and review your script, hit 'send' and have that information be posted directly to the script's thread page under the OSBot user's forum account.

 

But hey, that's just me thinking outside the box.

[zawmbee]

People are the problem. Nobody reports bugs. If people reported bugs and we had staff actively checking for bug reports it'd work great. Even better if the staff would show no favoritism and disable (+ take off safe) any script that has a confirmed crippling bug until the script writer updates it.

[Kalispel]

I think there should be more than just notice of whether the script is broken. Maybe I'm wrong but there seems to be no consequence for unattended scripts that are on the sdn. Having a script on the sdn should be a privilege and you should have to maintain your scripts or be penalized.

[Alek]

There are a lot of issues with what you are suggesting, many of which we've already experimented with over the years. Contact the SDN Manager about a broken script (free or premium) if:

-The core of the script is broken OR its a premium script with a broken feature AND

-You reported the problem to the scripter via PM OR on the script thread AND
-The scripter has not made any attempt to update it in 2 weeks

 

 

DO NOT fill up any of our inboxes if you haven't done all of those things above, it's a sure way to lose your messaging privileges.