Curse reserves the right to refuse to host any project.
Other Authors Work
If you have made legitimate changes to an existing project which has a license that would allow you to make said changes without violating any copyright law, the resultant project would be accepted provided that it has significantly diverged from the original; a project which is a verbatim copy of another project - whether owned by you or not - will not be accepted, regardless of its license.
Any license that follows the Open Source Definition is forkable by definition.
If you do want to fork a project that already is hosted on CurseForge/WowAce/BukkitDev, the recommended course of action is to clone the project and work from there. If you need to have a completely separate project, inform a moderator and we can work with you to assess the situation.
Please review the Abandoned and Inactive Projects Policy. A fan update of a project will not be approved, most times despite its license.
Removal of Project
If the original author informs us of some misgivings, the moderation staff will take it under consideration and make a judgment at our discretion. We want to preserve everyone's rights and make the best judgment overall.
Any project which contains copyrighted material - such as music - will not be approved.
World of Warcraft
Any AddOn with the following features will not be approved:
- Spamming any form of public chat. This includes AddOns which spam ASCII art.
- Written for a specific guild or server. Addons must be usable by everyone, on any server. This includes but is not limited to:
- Ninja looter/black list based for a specific server
- Guild DKP/raid attendance
AddOns which fit the following criteria will not be approved:
- Contains copyrighted music or sounds.
- Has functionality which can be entirely reproduced with a macro.
- Is written for private servers.
Addons must follow all of the following points set forth in Blizzard's World of Warcraft User Interface Add-On Development Policy:
- Add-ons must be free of charge.
All add-ons must be distributed free of charge. Developers may not create "premium" versions of add-ons with additional for-pay features, charge money to download an add-on, charge for services related to the add-on, or otherwise require some form of monetary compensation to download or access an add-on.
- Add-on code must be completely visible.
The programming code of an add-on must in no way be hidden or obfuscated, and must be freely accessible to and viewable by the general public.
- Add-ons must not negatively impact World of Warcraft realms or other players.
Add-ons will perform no function which, in Blizzard Entertainment's sole discretion, negatively impacts the performance of the World of Warcraft realms or otherwise negatively affects the game for other players. For example, this includes but is not limited to excessive use of the chat system, unnecessary loading from the hard disk, and slow frame rates.
- Add-ons may not include advertisements.
Add-ons may not be used to advertise any goods or services.
- Add-ons may not solicit donations.
Add-ons may not include requests for donations. We recognize the immense amount of effort and resources that go into developing an add-on; however, such requests should be limited to the add-on website or distribution site and should not appear in the game.
- Add-ons must not contain offensive or objectionable material.
World of Warcraft has been given a "T" by the ESRB, and similar ratings from other ratings boards around the world. Blizzard Entertainment requires that add-ons not include any material that would not be allowed under these ratings.
Please review the Executable Files policy for more information.
WowAce is a community of developers, and as a result there are higher standards for approval.
This list is not meant to be a clear distinction between if you upload your project to WowAce or not. This is meant as a guideline (for the most part).
- Be a member of the community: If you aren't active on the forums, or in IRC, then are you really a member of the community?
- Code base at a higher standard: Are you declaring all your variables to be global? Are you using upvalues to improve code efficiency?
- Documentation: Project must have decent documentation outlining what the AddOn does.
- Repositories: You must use a repository; file uploads are disallowed.
- Libraries: Hard-embedding libraries into your repository is unacceptable; use a properly-defined .pkgmeta file instead.
If your AddOn does not meet any of these requirements, it will be moved to CurseForge.
Needs a Better Description
- Use full, grammatically correct sentences.
- An English description is always required. If English is not your first language, try your best or ask for some advice/help from a friend who does speak English - you're playing an MMO; chances are you interact with someone who knows English well.
- Use proper spelling. Do not use (for example) "u" for "you", "ur" for "you're", "r" for "are", "pls" for please.
- Accurately describe the functions and behaviors of the project. This may only require a line or two, or it could encompass an entire page. Terms such as "simple" or "lightweight" are not descriptive, are overused, and as such should be avoided as superfluous buzzwords.
Needs a Better Name
A project's name should be distinctive. Using a generic phrase or a single common word for a project's name makes finding the project difficult for potential users and also makes the job of the project moderators extremely difficult, which can delay project approval for days or indefinitely.
- Some examples of unfortunate project names, with improved versions in parenthesis, are:
- Items (ItemsTracker)
- Inventory (InventoryManager)
- Shadowbolt (ShadowboltEnhancer)
- Action Bars (Whizbang Bars)
Libraries must have a documented API which clearly identifies how to use the library. Please see the .docmeta page for more information on how to use luadoc. If you need assistance, feel free to join IRC for help.
Libraries should not be AddOns in disguise. AddOns which "fix" Blizzard's UI, for example, should not be made into a library - embedding such a thing in another AddOn only serves to spread the "fix", does not add any functionality to the embedding AddOn, or adds functionality which has nothing to do with the AddOn itself and may even adversely affect its users (for example: LibBetterBlizzOptions is embedded in several AddOns which have nothing to do with configuration. Many users do not want the Blizzard Options panel altered, but are forced into it because AddOn authors embed it.).
Table of contents
- 1 Project Rejections
- 2 Changes Required
- Date created
- Oct 30, 2013