Guidelines: How to get your submissions approved. (Updated: Feb 3, 2013)

So, the file's title cannot contain anything else than the version of the file? Or can it contain other logical stuff, like the project name with the version? Like, "Skillz v5.5"? Just asking since it isn't stated clearly in the guidelines that having the project name in filetitle isn't allowed, just that it isn't required. However, a mod just sent me a PM telling I should remove the project name from all the file-titles of my already approved files/projects.

Thats just how I understood the guidelines, pardon me if I am reading it wrong.

What about if there was a Skillz api? Would that be "Skillz api v1.0" or just "v1.0"? Or "api v1.0"?

Just the version with the title. For the API it would also be just "v1.0". Also, it is clearly stated in the guidelines that having the project name in the title isn't allowed, since it provides a specific format.

Oh, I must've missed that page. The guidelines I was referring to was the one pyraetos posted.

Though it did bring up a few more guestions:
Wouldn't having a project with files in order like: "v5.5" "v1.0" "v5.4" "v0.9" "v5.3" "v0.8" be confusing? How would they know its the api? Open the files page and look at the filename? Is filename allowed to have "api" in it?

Also, isn't that page conflicting what pyraetos just said about the filename? Seen the link you provided says the filename must contain the MC version and Bukkit version in square brackets?

@Sanzennin @chaseoes

After a talk with @NuclearW, it has been decided that we will tolerate the PluginName vVersion format, even if the correct format is vVersion. Thank you for your understanding.

oh, thank you, and sorry to bug you guys about it. It just seems to be what a large portition of devs like doing.

Oh come on, seriously?

Yep, feel free to PM an Administrator if you doesn't find it fair.

Sorry about that.

If you do have to continue someone's plugin with a fork, make sure you can prove you have the author's permission AND that it falls under the license he chose. Both these things have to be true for a submitted fork to be accepted.

Thank you so much for this really helpful guide. It helped a lot

if sorry. i will do that next time

I believe you need to add the following to the guidelines:

1) A clear indication of whether for-pay plugins (or plugins with both free and for-pay features) are allowed.
2) A clear indication of whether anti-tampering or other security features are allowed. Specifically features intended to support the legal rights of authors that used a license that protects their rights to the code and restrict permissions to modify.
3) Any other obvious and non-obvious rules that file reviewers follow in determining whether the code is acceptable or not.

I recommend this because I found my plugin rejected for the reason "This is absolutely not allowed!" with no further explanation. The plugin will eventually be enhanced with a set of premium for-pay features. As such it must be possible to identify pirated uses of the premium features, have automated security, and other features to catch and prosecute pirates. The section in question is an early form of this, by reporting the plugin's presence to me (and me only) when I login to a server.

The way I see it either the reviewer goofed or there are unpublished guidelines being applied during the review process. Either way... the rules need to be clearer.

These recent changes to the original post should help clear things up, thanks.

Yes, that cleared things up some of the questions.

Does the rule forbidding for-pay plugin features (in addition to the free features) apply to using the CraftBukkit library or only to publishing plugins in the Bukkit site?

For example, can a for-pay or hybrid free/for-pay plugin (that is NEVER posted or mentioned in the Bukkit site) be made using the CB library? Does the CB library allow such use?

Thanks, fixed.

Please note that when using BukkitDev, you are not allowed to sell plugins or services, or advertise jobs, plugins, services, or anything else for real world money. This includes comments on all pages, forums, conversations, and everything else.

Please read the new section on auto-downloaders.

Addresses like that don't point to the actual files, only the page with the file description.

http://dev.bukkit.org/media/files/599/557/AntiCheat.jar would be the direct link.

Doing it that way avoids file screening completely, unless you're prepared to upload the file and then wait until the file is approved before changing the text file. In that case it's a far worse solution than the "silly" RSS scraping.