Minecraft Fanon Wiki
Register
Advertisement

All contributors must follow these rules for the sake of the wiki and its users.

The Rules

Claiming that articles are "fake" is not allowed

Disparaging articles as "fake" shows us that you are not here to contribute to the Wiki, but instead you're just here to try and start an argument with the creators of pages, and that you simply could not be bothered to read the rules.

If you choose not to follow this rule, you will be banned - however, you're free to appeal (you should normally be able to do so on your message wall) and we will be happy to unban you.

(Note that this does not apply to creepypasta articles such as Herobrine where the subject has been claimed to be real)


Vandalism

Vandalism is making unwanted changes to pages that harm the Wiki. Blanking an entire page's content, replacing it with gibberish, adding paragraphs of nonsense or profanity, etc.

Note that it is NOT vandalism to remove content from your own pages, for obvious reasons.

Spam

Spam is leaving unwanted, pointless messages or creating unwanted, pointless pages.

Spam includes, but is not limited to:

  • Pestering staff to be promoted to chat moderator, rollback, or admin - We have a dedicated page for those interested in becoming staff.
  • Flooding the site with irrelevant or gibberish comments. (IE: Posting slight variations on the same comment on as many pages as you can find)
  • Flooding the site with irrelevant or gibberish pages.
  • Claiming that articles are "fake."
  • Uploading irrelevant images, except for those which are for use on user pages.

Harassment

Do not harass other users.

Shipping real life people

While we really shouldn't have to tell anyone not to do this, someone already has so we have to add a section here. Do not create pages, or blogs, or anything like that trying to "ship" real life people who are not in a relationship. This includes Youtubers and other social media personalities.

This is harassment and will not be tolerated here, you will receive an indefinite ban.


Flaming

Flaming is insulting and demeaning another user to an unreasonable degree.

Context is important and flaming in response to flame-bait made specifically to get that reaction may simply be deleted with no ban time.

Trolling and Flame-bait

Trolling and flame-bait are statements made solely to provoke flaming or similar reaction from another user. For instance, making a racist article in the hopes of causing an argument in the comments section.


Plagiarism

Plagiarism is the theft of content without attribution to the original creator. Do not plagiarize other pages, or any other site/wiki. If you are caught doing so, you will be permanently IP banned.

If you use someone else's work, you need to credit them by name. IE: If you take an image created by DinosaursRoar and use it in your article, then caption it "Credit to the original creators!" instead of "Credit to DinosaursRoar," you have not credited the original creator.

Note that this does NOT mean you cannot incorporate other user's content into your articles. It would not be plagiarism to, for example, create a new dimension and say that the Termite spawns there, while linking to the Termite page. It would be plagiarism, however, to take the image and content from the page and present it as your own original creation.

If you are unsure if something would be plagiarism, you can ask an admin, or simply ask permission from the original creator. If you don't know who the original creator is, you can use the "History" function (click the arrow to the right of "Edit" and select "History" instead) to see a list of every user who has ever edited a page.

Advertising

Advertising is not allowed. Whether that be for products, for other websites, other wikis, etc.

The following exceptions apply:

  • Attribution - You can (and must, if you do not have express permission to use the image) credit an image or idea to its original creator.
  • Your User Page - You may advertise your personal creations and content, as well as your accounts on other websites, on this page.
  • Partnered Wikis - Our Partners are exempted from this rule.

Falsely claiming to be a staff member

Do not falsely claim to be an admin, bureaucrat, chat moderator, or wikia staff member.


Misc.

  1. Do not ask for another user's password. The user who asks will be given a permanent IP ban. If the user gives another user their password, They will be Perma-banned, but will be allowed to create a new account.

Guidelines

Failing to adhere to these won't result in a ban, but we may delete pages that do not adhere to them.

Decrees of fanon

  1. Do not create pages about content already present within vanilla Minecraft or Minecraft: Dungeons.
    1. If the page was on the Minecraft Fanon Wiki before being added to the game (IE: Colored Glass, Beehive, Concrete, Berries), it does not need to be deleted, and should instead have the {{Canon}} template.
  2. This is a fanon wiki, so page content declaring "this is fanon" or "this isn't real" or "this isn't actually in Minecraft", etc, are not required. The {{Fanon}} template will be applied to pages to which many angry comments are being posted.

Quality

Pages should meet a standard of quality or they may be deleted. See the Page Quality Guidelines for more information. Editing an existing page and causing substantial problems (especially broken coding) may fall under Vandalism which could result in a warning or ban depending on the context.


Canons and stories

  1. Stories should meet a bare minimum requirement of 2,000 bytes, you can view the size of a page by adding ?action=history onto the end of a page url.
  2. All "active" stories of short length that remain unfinished and unedited will be deleted after a period of two months of inactivity has elapsed. This means that if you want to keep your story, you need to add to it at least every two months until it's finished. If they contain enough content, however, they will be large enough to have established themselves without the need for an update.
    1. If the story is long and high-quality (quality of grammar, plot, and spelling lend to this), it will most likely be marked as "canceled" instead of deleted, Canceled stories will be preserved for posterity and can be revived if so chosen by the author. The difference between a large fanon and a small one should be second nature, but if you are unsure contact a moderator.
    2. If the story is part of a larger canon (such as how Creatures of the Void and Craft To Rebel are both Sad's Fanon series), then this rule will often be waived.
    3. If the story or series is on hiatus, the time is increased to six months. If on hiatus, this six months is very fluid and can be remedied with an "I'm going to begin again in the next two months" and the like, however, this fluidity is allowed at the discretion of the moderators. If you keep promising you'll update in x months and never do, we may grow weary with you.
  3. At the end of the day, remember we are a fanon wiki and our goal is not to destroy your stories. We just want to prune the place of abandoned, low-quality stories without which we'd be better off. These rules are generally lenient and can be appealed most of the time, so we'll be happy to reinstate any deleted article if you ask, provided you're actually going to work on it.

Page guidelines

  1. If a page has less than one larger paragraph, or two smaller paragraphs, then it is a stub. Please add {{Stub}} or {{Boring}} to your article. This encourages people to edit!
  2. You can also use common sense to determine if a content-lacking article is a stub or not.
  3. Please use infoboxes on mobs, blocks, etc. if one is applicable.

Page Quality

Pages on the Minecraft Fanon Wiki should be of high quality or they may be deleted, this means:

  • Being well-articulated and legible
  • Containing necessary information
    • Articles should be long enough to convey the information required for the reader to understand the subject of the page. If your article about a mob only describes its health and not the damage it deals, its appearance, etc. then the article will seem incomplete. Of course, pictures can stand-in for even very detailed descriptions, and are preferred.
    • An example of how not to do this is B-Bomb. This article is abstract and strange enough that we thought it was funny and didn't delete it, but if it did not have an image attached this would probably not be the case.
  • Explaining its content in a straightforward manner
    • This is a bit more abstract of a writing nuance, but you should not "jump around" a lot in writing. This is more applicable to larger pages, such as those about mods. If you have a list of mobs added by an update, their health, spawning information, and descriptions should all be in the same place, not in different categories.
    • I couldn't find a bad example for this one, so here's a good example of how you should write articles describing more complex mechanics - Burglar; This article has lots to talk about but goes through things in a logical sequence, so you don't get lost or confused without necessary information while reading.
  • Covering one subject exactly, no more and no less
    • An article should have one subject, whether that's a mob, a biome, an update, a story, or a character. That subject can of course encompass other subjects, and lists are allowed, (IE: an article about a creeper mod will probably contain subsections on the creepers the mod will add), but unrelated or tangentially related subjects not dependent on each other should not be discussed on the same page. An article about bees containing info on beehives is fine, but if you have one idea about a new zombie and another about a new boat unrelated to them, it would be better to either make them separate pages or work them both into a mod or update.
    • An example of what not to do is Far Dragon (Archive). This page covers too many subjects (the far dragon, a structure it spawns in, various barely-related mobs) and gets sidetracked and long-winded too easily talking about them.
  • Should not contain broken coding. Mostly an issue when editing other people's articles or templates.
Advertisement