Skip to content

Submission name is unique and relevant

  1. The name (on the website, main plugin class, and file name) should be unique and be discernable from existing resources.
  2. The name should be relevant to the plugin's functionality.

Explanation

This guideline requires that all plugins should have a unique name that does not too closely match to other names of existing plugins. This is to avoid confusion between different resources and misinterpretation of functionality and purpose.

Condition 1

Plugin names should be easily discernable from other resources on the website. For example, Quick Smelt and Fast Smelt or Discord and Discords are too similar. Furthermore, developers should avoid appending adjectives to already existing names (e.g. Better Quick Smelt, Simple Admin Radar etc.), for two reasons. First of all it's stupid, and secondly it promotes every developer creating their own version of a plugin rather than contributing their changes to the original.

Condition 2

Names should also be relevant to the plugin's functionality to avoid becoming too generic. For example, Ban System and Server Vote are not good names. They are bad because vague names leave room for misinterpretation about the plugin's purpose and functionality. The other problem with generic names is that because the name is so general, it restricts what plugins with similar functionality can be called.

A simple way to check for uniqueness is to search the plugin name on the website and check that nothing too similar pops up in the search results.

Released under the MIT License.