The Great Big Fucking Policy Rewrite

<tabber>
|-|Article Policy=
__TOC__
== A.1: Article Criteria ==
=== A.1.1: Article Creation ===
All warriors that meet criteria and feature in completed battles should have articles. Creating articles for warriors without articles that a user intends to use in a reserved battle is encouraged, but not necessary. If a user posts and closes a battle featuring warriors that still do not have articles, it is their responsibility to make the necessary articles.
=== A.1.2: Titling ===
#Articles must have grammatically correct titles. The title for a warrior's article should be what they are best known as in the real world. (e.g., Thomas Anderson and Edward Teach are Neo and Blackbeard, respectively). In cases where there are multiple well-known real-life names, the title should be the most formal one (e.g., Captain America is Captain America, not Cap).
##Naming convention depends on the type of warrior in question. Strictly fictional warriors follow the western standard of the given name followed by the surname. Real-life and fictionalized versions of real-life warriors follow their local custom standard (e.g., Sasaki Kojirō (Fate)). It is up to a page's creator to use reasonable discretion to determine whether or not including a middle name or surname is appropriate. 
##Warriors that have pseudonyms or aliases can be given redirect pages titled with said alternate names.
#In the event of multiple articles having the same name, including signifiers in parentheses is necessary. The signifier should be the most distinct choice possible, even if a more official but less distinctive option is available. If an acceptable abbreviation is available, it should be used. For example, the Captain America featured in the Marvel Cinematic Universe is titled as Captain America (MCU) rather than Captain America (Marvel Cinematic Universe) or Captain America (Earth-199999).
##Real life or mythological warriors with fictional counterparts on the wiki should have no signifier at all and only their same-named counterparts must be identified with one.
##If a warrior originates from an adaption and only has one adaption of note, it is acceptable and preferred for the signifier to simply be the type of media for conciseness (e.g., Jon Snow (TV Series)).
#If one feels the titling of a page is inappropriate, they may make their case for a different titling via Discord policy discussion and a forum post on the wiki. The page should not be renamed until a decision is reached so as to prevent edit wars (see A.5).
=== A.1.3: Page Contents ===
#All warrior articles must meet the Warrior Page Criteria. Mandatory elements include a brief biography (approx. 250 words), an infobox, categories, and headings for each of the battles the warrior has taken part in. These headings should be displayed in chronological order, excepting in the case of rematches. At the end of each battle's section, there should be a link to the corresponding blog post where the vote count can be verified. See Creating an Infobox for details on creating and using infoboxes.
#Warrior articles do not exist for their own sake, but rather to showcase completed battles. Thus, warrior articles without any battle status should not be made and, if they are, shall be marked for deletion. The only exception to this is warriors who have battles that were closed and were later declared invalid or unfair. In this case, the article should have "None." entered into the reserved section of the infobox.
#Expired battle reservations (see B.13) can be deleted from an article at the discretion of any editor.
=== A.1.4: Expert's Opinions ===
#After a battle has been closed, a brief explanation on the reasoning behind the battle's outcome (the "expert's opinion") should be placed after the simulation of every written battle on a page.
#If the battle's author personally writes an expert's opinion for said battle, then it may not be edited without their express consent. If the author does not write an expert's opinion, any user may write one themselves based on the reasoning of the voters. The author of the battle reserves the right to alter this explanation at any time.
=== A.1.5: Plagiarism ===
Using text word-for-word from another media source, including Wikipedia and other wikis, for biographies on articles should not be done. The editor that originally introduced the plagiarized content has the responsibility to replace the content with original work. Articles that have plagiarism should be marked with the {{Plagiarize}} template until the matter is resolved. If the matter is not fixed in a reasonable period of time, the offending content will be deleted.
=== A.1.6: Targets for Deletion ===
Articles that do not meet policy will be marked with the ({{Delete|reason goes here}}) template until the issues are resolved or the article is deleted at the discretion of the staff.
=== A.1.7: Automatic Deletion ===
An article is liable to be deleted immediately if it meets one of the following criteria:
*It has excessive grammar, spelling, or coding errors to the point of illegibility.
*It is inappropriately used to post an entire battle, as all battles should be displayed on blog posts.
*It features a warrior that does meet the warrior criteria and does not already have a closed battle.
*It is clearly a work of spam or trolling.
== A.2: Categories ==
#Each warrior article must be placed into all applicable existing categories. Each category page should feature a brief description to help editors decide whether or not a category is appropriate. If you feel an article should be in a category that does not exist, please consult the staff before creating it. A potential category must have at least fifteen applicable articles before it can be created.
#A warrior should be placed in a media-related category if they either originate from the type of media in question (e.g., Film Warriors for Darth Vader (Legends)) or the type of media is in reference to an adaptation of the warrior's original source that is more well-known (e.g., Video Game Warriors for Geralt of Rivia).
#A warrior should be placed in an activity-related category (e.g., Covert Warriors, Time Travelers, and Vigilantes) if they regularly engage in such activity in their canon as warriors.
#In the case of warriors from open-ended video games with a wide variety of options for customization (e.g., The player could make The Last Dragonborn applicable to Vampire Warriors and Berserker Warriors, but this is not required by any main quest.), the article should only be in categories that are made applicable by mandatory actions for the player.
#Real warriors should not be placed into any category that describes a warrior's morality (e.g., Evil Warriors and Anti-Hero Warriors). Deadliest Fiction is completely and utterly neutral on the subject of the morality of historical figures.
#Warriors that originate from religious and mythological sources should be placed in the Mythological Warriors category. Such warriors should not be in any category that would suggest that they definitively did or did not exist (e.g., Real Warriors, Fictional Warriors, and Fantasy Warriors).
#If one feels a trend of category use is inappropriate, they should make their case via the Discord server or a forum post. No action should be taken until a decision is reached.
== A.3: Rematches ==
#If a rematch has occurred or permission has been granted for one, both the original battle and the rematch will be on the warriors' articles. The rematch should be identified as such and displayed directly underneath the original battle. The article's battle status will display only the status of the latest rematch, whether it be an outcome or a reservation.
#If a battle that has been rematched is declared invalid or unfair and disregarded, the rematch, if still valid, should not be identified as a rematch.
== A.4: Original Characters ==
Original characters, also known as OCs or user warriors, are not to be given pages. Battles between OCs and proper warriors with pages are not to be present on any pages. OCs include:
*a character who is created by a user and does not exist in any published work.
*a fusion of multiple distinct canon versions of a character, known as a "composite."
*a team made up of multiple characters whose canons do not intersect.
The following do not count as OCs:
*a representation of a character whose existence and abilities are canon, but does not have a defined personality (e.g., Commander Shepard).
*names and personalities given to otherwise generic characters for the purposes of a written battle (e.g., Adventurers (Final Fantasy XIV)).
*a non-canon version of a character who is presented as an option for the player in an interactive medium (e.g., Evil Cole MacGrath).
== A.5: Edit Wars ==
An edit war is when multiple users disagree about the content of an article and repeatedly override each other's edits. If an edit war occurs, a staff member should lock the page until the matter is resolved. The offending users are liable to be banned for a length of time left to the discretion of the staff member taking action. Users with differing opinions on an article's content should discuss the matter through comments or the Discord server before edit wars happen.
== A.6: Editing Other Users' Battles ==
Editing another user's battle is permitted only if one has received express permission from the original author, is removing a dead link, or has received specific authorization from a consensus of the administrators. Under all other circumstances, it is strictly forbidden. Violation of this policy is grounds for an immediate ban, the length of which is left to the discretion of the admin taking action.
|-|Battle Policy=
__TOC__
== B.1: General ==
All battles must be written in blog format. This allows users the chance to criticize/offer their opinions about the warriors. Battles written on pages will be deleted after a span of 1-2 days at the discretion of the administrator to give the user a chance to move the information. An incomplete battle blog will be deleted one week after its last edit. Do not have unfair match-ups. If the general audience or administrators agree that the battle is unfair, it will be disregarded e.g., Assyrian Soldier vs. SWAT. Multi-man battles are judged this way based on each warrior against each opponent. For help creating battles or blogs see Creating a Battle.
== B.2: Canon Battles ==
Battles that have already occurred in warriors' canon (e.g., Darth Vader vs. Obi-Wan Kenobi) are forbidden, excepting that a user can demonstrably prove that the version of the battle they desire is clearly materially different from the one that occurred in canon.
== B.3: One-On-One Battles and Group-On-Group Battles/Battle Royales ==
The completion of a battle that features two warriors as members of opposite teams OR as participants in a battle royale does not preclude those two warriors from being used against each other in a one-on-one battle in the future or vice versa. For example, if Batman has already fought against Captain America, both may still be present as members of their respective teams in a future battle between the Justice League and the Avengers.
== B.4: Warriors ==
Any characters posted by the user in a battle will be considered a warrior out of our good faith policy. However, if a user discovers that a character is not truly a warrior, then all articles relating to that character will be edited to reflect this, and all battles with that character will be closed.
=== How to Tell ===
To tell whether or not your character is a warrior, see the definitions below; a character has to match at least one of the following criteria:
1) Fights for a living*
2) Fights on a daily basis*
3) Has being a fighter a core part of their character*
4) Leads other fighters in battle
5) Has superhuman powers allowing them to fight, and has used those abilities for that purpose
6) Commands a warrior/weapon like unit to fight
7) Is a representation of a user on this wiki
*Simply killing people does not count as "fighting" or "being a fighter."
Prohibited characters include:
* Any character that does not meet the criteria
* Cartoon characters that have not truly engaged in combat
* World leaders that don't fall under the warrior criteria and don't hold any military positions that aren't directly tied to their status as leader of the nation
== B.5: Voting ==
=== B.5.1: For the Author ===
All battles must be open for at least three days before being closed. A battle may not be closed if it has zero votes, not including the author's own. If a battle receives no activity for sixty days, it is free to be removed from the reservations on the relevant pages. Authors are allowed to set their own criteria for which votes they will accept. Disregarding votes that meet these criteria simply because the author disagrees with the voter's conclusion is not allowed.
If a battle is closed and the votes are tied, the author may either declare a victor or end the battle in a tie. The author is allowed to give themself a vote if they like. However, this precludes the author from declaring a victor in the case of a tie, as this would essentially be giving themself two votes. The one and only exception to this is in an elimination tournament, where there must be one victor, so the author is allowed to determine the outcome if there is a tie.
If any of the above policies are violated in a battle, the author of the battle will be issued a warning. In case of repeat violations, the user will receive a ban, the length of which is to be determined by the acting admin.
=== B.5.2: For the Voter/Audience ===
If you are going to vote, please use the voting method the author provides and states you should use. When voting, please try to provide a good and strong reason why that warrior should win.
== B.6: Battle Royales ==
A battle royale is any battle that features at least five warriors or teams of warriors. If it wouldn't count as an orgy, it doesn't count as a royale. Royales are presented on warrior pages uniquely, using a dedicated section of the infobox and being identified by whatever title the author chooses. After the conclusion of a royale, all participating warriors or teams of warriors must be identified and properly linked either in the written battle or in the expert's opinion and ranked according to the royale's outcome.
== B.7: User Battles ==
User battles are fictional battles between two or more users, ie. Cfp3157 vs WanderingSkull. If you are planning to write a user battle, please consult the user(s) you will be facing in your battle. They must provide the weapons, training, or any forms of debate they will be using. Failing to list the appropriate weapons/provided items will result in a deletion of that battle. In order to prevent the wiki from being flooded by a torrent of user characters, individual user warriors do not qualify for pages.
== B.8: User Tournaments ==
In order to run a User Tournament, the user proposing to run the tournament must post a proposal in the Challenge Arena board. Afterwards, the user has one month to get approval from a majority of the admins/bureaus. If and only if this is achieved, the user may then post sign-ups and start the tourney. Only two tournies may run at any one time.
== B.9: Rematches ==
Rematches can be done with the original author's approval. If the author disapproves, the user requesting the rematch can override the author by gaining the publicly written support of either five users or three users including one staff member. If the original author has had his disapproval overridden, but still feels that a rematch should not be done, he is allowed to gain the publicly written support of other users against the rematch. The side with the highest number of supporters wins, with ties going to the original author. In the case of inactive or retired authors, the three supporters rule still applies, and an admin approval is needed as well.
If at any point, even after a rematch is done, sockpuppets are found to have been used as supporters, the side using them automatically has their position revoked. If the rematch was already done and found to have been invalid, then the original outcome will be posted in the battle status and the section will have a notification that the rematch was considered void due to sockpuppetting for votes.
In the case of rematching a battle that was a collab between two or more users, all users involved in the collab must give their permission in order for the battle to be rematched. If one of the original collaborators wants to rematch the battle they must get the support of all the other users involved in the collab before they are allowed to rematch. If collab partner/s disagree or are inactive then a rematch request must be made, following the same rules lined out above. In case of a tie in such a scenario, the rematch will not have passed.
There is a limit on how many times an author can rematch their own battle. This includes rematches of their own battles and a rematch of another user's battle. After their first rematch, they must go forward with the traditional rematch proposal process. This same rule would apply to a user seeking to rematch their battle that was the rematch of another user's battle. Ex. If User 1 posts Battle 1, User 2 succeeds in acquiring a rematch of it and posts Battle 2, User 2 must go through the rematch proposal process for Battle 3.
== B.10: Nerfing and Buffing ==
Wizards, super heroes, god warriors, force users, and other warriors with natural abilities cannot be limited to a certain set of powers. All powers canonically used by that warrior are to be accounted for in all of his/her battles. Linking to other sites that provide a full list of the warrior's abilities is allowed. Furthermore, using said warriors from a time period in which they do not have certain powers is not nerfing, so long as all their other equipment and powers is from that point in time.
In addition, it is also a violation of policy to buff, or increase, a warrior’s powers or abilities to points above where they are in canon. This includes, but is not limited to: giving them weapons they never used, powers they did not have access to, or applying game mechanics (i.e., increased durability that is not a canon power) as abilities.
Regarding warriors or abilities have conditional visibility, such as Stands in JoJo's Bizarre Adventure or Shinigami from Bleach, there are ways to ensure fairness that do not fall under buffing or nerfing. If the warrior's opponent has an ability or experience which is similar to the requirements to view the warrior or ability in question, it would not be considered nerfing or buffing to assume they can.
Using the Stands example above, a character is likely able to see Stands if they have an ability of explicitly magical origin. Using the Shinigami example above, a character is likely to be able to see a Shinigami if they are able to see ghosts, see other otherworldy beings normally invisible to humans, having soul- or ghost-related powers, or can see beings with similar composition to Shinigami.
If this reasoning is used in a challenge, it is on the challenger to demonstrate why the given explanation is invalid, or to demonstrate why the warrior's abilities fall outside of this definition.
== B.11: Fairness/Validity Challenges==
"Unfair" means that the battle swings far in favour of one warrior as represented in the battle itself, not the votes. It is not exclusive to one warrior overpowering the other(s) enough that there is zero chance of them winning. Battles that are "one-sided" are unfair. "Invalid" means that the author of the battle has provided or deprived a warrior of a weapon, power, or other attributes that they did not have access to in canon. Use of a composite warrior, a combination of versions of a warrior from multiple separate canons, is also grounds for invalidation. If material is published following the closing of a battle that establishes new canon information pertaining to a relevant warrior that would render the battle invalid/fair, this is not acceptable grounds for a challenge.
The process for declaring a battle as unfair or invalid is as follows:
*First, one person, hereafter known as "the protester", brings up the idea of the battle being unfair/invalid, providing a link to the blog in question and stating their reasoning. This should be done either in the forums or in the comments of the battle itself if it is ongoing. Battles may not be closed while there is an ongoing challenge.
*Second, the protester must then get three other users, including at least one staff member, to clearly state their support to the protester's terms. If the original author of the blog agrees with the protestor, the battle may be disregarded immediately. Users who disagree with the challenge may also voice their opposition by voting against the challenge. The side with the highest number of supporters wins, with ties going to the original author. In place of staff support, if the challenge gets net support from five users, the match is disregarded. 
*Finally, after a week has passed, if the challenge has received sufficient support, the battle will be disregarded. It should be removed from the relevant warriors' battle statuses and moved to the disregarded section of their pages along with a brief summary of why it was disregarded.
Disregarded battles can also be revalidated by following the same procedure: a protester must state their reasoning as to why they believe a disregarded battle is fair/valid and receive the required amount of support. 
If material is published that reveals new canon information that would render a closed battle invalid, the battle should not be challenged for validity on these grounds.
== B.12: Reservations ==
Users are allowed to reserve match-ups between warriors thereby preventing other users from doing that battle without gaining permission from the user who currently has the battle reserved. In order for a battle to be reserved, it must be claimed somewhere on the site. A sandbox, userpage, or on a warrior page is acceptable, on a separate site is not. Reservations only last for 18 months. Past that, the battle is re-opened for use by anyone. Three months of inactivity forfeits all reservations. No more than 20 reserved battles are allowed for one user at any one time. 
|-|User Policy=
__TOC__
== U.1: Rights ==
All users, regardless of position or history, have certain rights on this wiki.
* All users must be respected
* No one receives special treatment, even sysops
* All users may contribute their own ideas on blogs, and all users are free to respond to said ideas in a respectful way.
== U.2: Good Faith ==
We ask that all users be respectful and accurate in their edits. Any users who vandalise or add false information will be given one warning by the admin team, and continued misbehaviour will result in a ban, the length of which is up to the discretion of the admins.
== U.3: Insulting/Trolls ==
Any personal attacks or insults towards users are considered “flaming”. Anyone who the admin team finds guilty of flaming will be given one warning. After that, any more flaming will result in an immediate ban, the length of which is up to the discretion of the admins.
== U.4: Sandboxes ==
To avoid confusion, it is highly recommend that users keep unfinished battles and code testing in a sandbox rather than a blog page. To create a sandbox, simply create a new page called [[User:/Sandbox]].
== U.5: Sockpuppeting ==
Sockpuppeting is the act of creating another Fandom account and using it while your original account is still active, or in an attempt to circumvent a ban. If any user is discovered to be sockpuppeting, all of their accounts will receive an immediate and permanent ban. Sockpuppeting may also result in reporting the user to Fandom staff.
== U.6: Rezzing ==
Blogs and posts in the forums and the discussions that have not received any comments for sixty days are considered to be dead. Commenting on a dead post, known as rezzing, will result in a warning. Should the rezzer ignore this warning and rez again, they will recieve a two-week ban, followed by a month ban for a second offense, and a permanent ban for the third offense.
|-|Chat Policy=
__TOC__
Deadliest Fiction has an official Discord server where users can talk about wiki related matters and also socialize with other users. Here are rules and policies associated with it.
== C.1: Joining the Discord ==
#New users who enter the Discord must provide a corresponding Fandom username which will be displayed as their screen name on the Discord. A new user has one hour to provide this information and will be kicked if they fail to do so. Joining and failing to provide one's account a second time will result in a ban. The user must then contact a staff member and provide their account to get reinvited to the server.
#The account provided by the user must have at least 10 edits on Deadliest Fiction within a month of joining. If the edits are not met, requests to join will be denied until they are made.
#Inactive users will be kicked. "Inactivity" is defined as a period of no activity for three months or more on both the wiki or the server.
#Users who are banned on the wiki will be muted on Discord for the duration of their ban. Permanently banned users will be banned from the Discord as well.
== C.2: Spam ==
Repetitive posting done to the detriment of other uses is considered spamming. On the discord, first offenders of spamming will be kicked alongside a strict warning. Continued disregard of the rule will result in a ban for an amount of time decided by an admin, bureaucrat, or other discord manager. 
== C.3: Language ==
Limited cursing is allowed. Words like shit, damn, hell, bitch, and fuck are fine to use in limited quantities. Excessive use of curse words is grounds for a kick or a ban at the discretion of the chat mod. Note that the use of these words in flaming or insults will result in kicks and bans similar to those seen in C.2.
== C.4: Sexual Content ==
New and existing users who post overtly sexual language, images, or links will be instantly banned. Weather said ban is permanent or is able to be repealed is at the discretion of the administration team. Anything of an explicit sexual nature, either in images or language, addressed to actual users will result in an immediate ban, and the rest of the administration team will consider whether it is permanent or not
</tabber>