Halo Fanon:Not Canon Friendly

Defining Canon Friendliness
Halo Fanon is built on the concept of writing within the Halo universe. Therefore, following Halo canon is key to writing mainspace articles on Halo Fanon, because Halo canon is what separates this wikia from other fan fiction wikias. Established canon should be regarded during the writing of articles.

Contradiction
If an article contradicts something already stated in canon, then the article is considering as breaking canon.

Dates
Certain things happened at certain times in the Halo universe. Authors should make sure to check dates relevant to their article before posting.

Naming
The UNSC and Covenant have specific ways they name things. While there are exceptions in some fields, in others, there are not.

Rank and Position
Rank and position go hand in hand. Generals almost never see frontline combat, and Privates never lead regiments. When attributing a rank to a character, make sure that what they do makes sense in light of that rank. Furthermore, Zealots do not command ships; Ship Masters do. Make sure that the rank you attribute is from the correct branch of ranking. Both the UNSC and Covenant have a clear set of ranks for combat and for naval forces.

Grouping
Certain groups are already well defined in the Halo universe, and when attributing a character to a certain group, authors should check to make sure the character meets the requirements to have been in that group.

Behavior
While individual characters do not have to behave in a certain way, one should ensure that the UNSc and Covenant, as a whole, behave in the way they normally do when writing fan fiction. For example, the Covenant are imitative, not innovative, and so if a member of the Covenant invents something by meddling with a Forerunner artifact further than the San 'Shyuum deemed fit, other members of the Covenant would deem this as heresy.

God Modding
God Modding is when an author's article is overpowering and/or has no real weaknesses. The article may also be unrealistic and may also have its canon friendliness disputed, due to the previously stated distinguishing reasons. Authors should avoid making their characters too powerful or without any weakness, as this is not only unrealistic, but also unfair to other users, especially when participating in Role Playing.

Unrealism
If an article is unrealistic for conventional matters not necessarily having to do with Halo itself, the article can be considered as breaking canon, since Halo operates in a universe that abides by realism.

Lack of Halo
Authors should make sure they are actually writing in the Halo universe. Articles that have nothing to do with Halo, while not necessarily a breach of canon, break a separate rule, Rule 3: Fanon should be Halo related. These articles should be immediately marked with a 3 and a vote to move them to the author's namespace started on the page's talk page.

Other
Identifying breaches in canon include, but are not limited to the above list. Certain things that would seem to break one of the above problems might be explained in such a way as to make sense, and there are things that break canon that are not explicitely named here. These are just a general rule of thumb for identifying breaches in canon.

Exceptions to the Rule
Sometimes, articles break the canon of media that wasn't released when the article was created. If this happens, authors should try to fix the problem, but if the problem is not fixable, they are exempt from the normal rules of canon friendliness.

Not Canon Friendly
When any user sees something they believe breaks canon, they should put a Template:NotCanonFriendly at the top of the page, and then explain what the breach is in that page's talk page. This allows the author the chance to both attempt to justify the article and fix the article, if the mistake is not justifiable and was due to lack of knowledge. Users should keep in mind that not everyone can know everything, and should make sure to offer constructive criticism rather than insulting. Stepping over the line can be considered a personal attack. The addition of the NCF template will let administrators know to look at the page and talk page. If they agree with the user, they will say so, but if they agree with the author, they will remove the NCF template. It is important to note that only administrators may remove an NCF template. The removal of this template by the author or other users is not allowed, and may only complicate matters.

Rule Breaker
If an author refuses to or otherwise does not fix a legitimate issue with an article for a period of one to two months, the NCF template is to be removed by an administrator, and a 4 is added, to reflect that the article is breaking Rule 4: No direct contradictions of definitively established canon. When this template is added to an article, a vote to move the page to the author's user namespace is also placed on the talk page. It is a community vote; if users feel that the article belongs in the mainspace, they should vote against. If they feel that the article does not belong in the mainspace, they should vote for. After a few weeks, if a majority of voters have voted for, the page will be moved to the author's use namespace by an administrator.

Deletion
Articles are almost never deleted on Halo Fanon, as we feel that it would be insulting to the author if we deleted their work, whether or not it belongs on the mainspace. The only times an article should be deleted are: author requests, if the page is blank, if the page is gibberish, or if the page was created to be disruptive or for spam/vandalism. Articles that break Rule 3 or Rule 4 should never be deleted unless one of the above reasons is true.