SkyrimForge.com
Mods
Authors
Forums
Wiki
Store
Paste
Sign in
Register new account
SkyrimForge.com Wiki
Knowledge Base
/
Policy
/
Project Acceptance Policy
r14
Source
Markup:
==Project Rejections ===Other Authors Work Any project uploaded without the explicit permission of the original author(s) will not be accepted on [[http://www.curseforge.com | CurseForge]]/[[http://www.wowace.com | WowAce]]. ====Forking/Cloning 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 [[http://www.opensource.org/docs/definition.php|Open Source Definition]] is forkable by definition. If you do want to fork a project that already is hosted on [[http://www.curseforge.com | CurseForge]]/[[http://www.wowace.com | WowAce]], 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. ====Fan Updates Please review the [[http://kb.curseforge.com/policy/abandoned-and-inactive-projects/ | Abandoned and Inactive Projects Policy]]. A fan update addon will not be approved. ====Removal of Project If the original author informs us of some misgivings, we 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. ===Terms of Use Violations Any addon/project which violates the terms of use for the game which it is being submitted for will not be approved. ====World of Warcraft Any addons with the following functions will not be approved: * Enabling special features for private servers. (You will be banned for uploading these.) * Spamming any form of public chat. This includes addons which spam [[http://en.wikipedia.org/wiki/ASCII | ascii]] art * Gambling addons * Botting/automation addons * Addons promoting a paid program of some sorts * Addons requiring you to pay for the entire addon * Addons which are nothing more than a macro which can be run by using a slash command * Addons 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 ===Executable Files Please review the [[http://kb.curseforge.com/policy/executable-files/ | Executable Files]] policy for more information. ===WowAce [[http://www.wowace.com | WowAce]] is a community of developers, and as a result there are higher standards for approval. ====Requirements This list is not meant to be a clear distinction between if you upload your project to [[http://www.wowace.com | 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 [[http://kb.curseforge.com/projects/pkgmeta-file/ | .pkgmeta]] file instead. If your AddOn does not meet any of these requirements, it will be moved to [[http://www.curseforge.com | CurseForge]]. ==Changes Required ===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 Libraries must have a documented API which clearly identifies how to use the library. Please see the [[http://kb.curseforge.com/projects/docmeta-file/|.docmeta]] page for more information on how to use luadoc. If you need assistance, feel free to join IRC for help.
Markup Type:
The type of markup for this entry.
Click here for details
.
BBCode
Markdown
Plain Text
Safe HTML
WikiCreole
<div><img src="//secure-us.imrworldwide.com/cgi-bin/m?ci=us-603339h&cg=0&cc=1&ts=noscript" width="1" height="1" alt="" /></div>