I've heard pre-compiled code is not allowed in the SDN. Does this mean we are not allowed to create our own API/SPI for OSBot distributed through JARs?

 

Assuming we were allowed to, are scripts allowed to extend upon a subclass of Script? Such as:

abstract class ExtendedScript extends Script {


}


@ScriptManifest(...)
public final class MyScript extends ExtendedScript {


}

I'm pretty sure I could test the second one myself if I were on a computer; sorry for the inconvenience.

 

Are there any exceptions, or possibly a way to get permission, for these actions?

you can extend a class extending Script (I do so myself), no problem with that whatsoever ^^

Edited May 22, 201510 yr by Botre

what, you just make an api in /dependencies and use whatever the fuck you want.  no need to compile it

what, you just make an api in /dependencies and use whatever the fuck you want.  no need to compile it

I didn't ask for a work around. This would be tedious for use in multiple projects, as well as clutter the project depending on the size of the API/SPI

I didn't ask for a work around. This would be tedious for use in multiple projects, as well as clutter the project depending on the size of the API/SPI

how is that a work around?  that is what is supported.  and how is having a dependencies package and a scripts package clutter?

how is that a work around?  that is what is supported.  and how is having a dependencies package and a scripts package clutter?

It's a work around for how it should be handled, which is why I also asked if there were any exceptions to this, such as getting permission. And the SPI I intend to release has 15+ packages. Adding that to a project consisting of only a few classes is definitely a problem in my eyes.

they won't make an exception for you 

they won't make an exception for you

That's real nice of you..

Hopefully they'd make an exception if they were to review the code and possibly have someone trusted jar it.

its not about the code, its about the rules and then they would have to make an exception for everyone.  which they aren't going to do

its not about the code, its about the rules and then they would have to make an exception for everyone. which they aren't going to do

The rules state:

"Authentication systems, script loaders, and distribution systems need prior approval from any Admin and/or Developer"

So I'm not 100% sure about that. I'll wait for a developer to reply

The rules state:

"Authentication systems, script loaders, and distribution systems need prior approval from any Admin and/or Developer"

So I'm not 100% sure about that. I'll wait for a developer to reply

we have asked for this before (many scripters),  and they said no.