Minecraft Discontinued Features Wiki:Style Guide

This article is the style guide for the Minecraft Discontinued Features wiki.

Although Wikipedia already provides a more general style guide, a more specific one is necessary for Minecraft Discontinued Features-specific guidelines. As such, only guidelines pertaining to the Minecraft Discontinued Features Wiki and its basic formatting rules are included here. If any contradiction arises, this page always has precedence over its subpages and the Wikipedia style guide.

Title
Page titles should use title case.

Examples:
 * Bedrock (Item)
 * Piglin Armor

Inclusion
The majority of pages on the wiki should focus on covering discontinued features. Discontinued features are any saved object in the game (items/entities/blocks/etc.) that were possible in earlier versions of the game but become unavailable in later versions, but the object can be updated to those later versions where it is unobtainable. The discontinued feature can be recontinued, deleted, or normalized by the most current version though. Future discontinued features are not yet discontinued but are allowed to be included. If a future discontinued feature does not actually become discontinued as predicted then it no longer can be included and must be deleted. Before creating a page make sure that there is a significant amount of information and that the majority of the information is true and tested, if the page needs to be expanded or requires testing use the respective template. If an article do not meet these expectations it may be deleted.

All discontinued features must be in the vanilla Java Edition of Minecraft. Bedrock Edition and other fork version features belong on the separate wiki. The definition of cheating is largely subjective and what exploits/versions are too far depends on the player. The wiki holds a very expansive view of vanilla but whenever it may be questionable relevant warnings should be written to help the reader find the features they agree are vanilla. The wiki allows these as vanilla:
 * Bugs/Exploits
 * Snapshots, Pre-releases, Release Candidates, and Combat Tests
 * Versions Before 1.0.0 (Beta, Alpha, Infdev, Indev, Classic, Pre-Classic)
 * April Fools' Versions (Beta 1.4, 2.0, 15w14a, 1.RV-Pre1, 3D Shareware v1.34, 20w14∞)
 * Downgrading Versions - going to an older version of the game
 * Minecraft China Java - the variant of Minecraft made to follow Chinese laws on censorship, playtime restrictions, and other requirements
 * MinecraftEdu - the Forge mod bought by Mojang that was made from Beta 1.4 to 1.8.9 for education
 * Basic File Manipulations - Renaming world name, renaming level.dat to special_level.dat/vice versa, and deleting level.dat are currently allowed
 * Official Map Discontinued Features - Discontinued features found in maps created by Mojang
 * Converters - Converters that allow Classic file format to be brought into Indev file format and Indev file format to Infdev file format are allowed.

These are not allowed on the wiki:
 * Any feature that requires mods, external editors (like NBTExplorer), or bukkit/spigot
 * Cross World Commands are mentioned only on that page but should not mentioned anywhere else
 * Features from Classic 0.24_SURVIVAL_TEST to Classic 0.24_SURVIVAL_TEST_03, Indev 0.31 20091223-1 to Indev 0.31 20100122, or Infdev 20100227-1 to Infdev 20100325 do not save

Some other pages are allowed but all should be related to discontinued features. The other pages allowed are:
 * Disambiguation pages to help the reader navigate from an ambiguous search to the desired page.
 * Version pages covering all features ending in a version range
 * Meta pages covering types of discontinued features
 * Lists of specific types of discontinued features
 * A few tutorial & community pages
 * Pages listing discontinued features that meet certain specifications or are in a specific category

Version Formatting
Versions on articles should be consistently formatted, usually using Mojang's name for the version. However, Mojang has not given a name for every version and sometimes gives multiple names for the same version. All mentioned versions must have been released. Development versions do not count even if there is video or image proof that Mojang produced them. This includes privately released versions such as Combat Test 8a and Alpha v1.2.0 (Preview) unless they are later leaked such as Combat Test 7a. Versions that were released but are now missing should stil be mentioned.
 * The four pre-Classic versions are rd-132211, rd-132328, rd-160052, and rd-161348
 * Classic versions should begin with "Classic" to signify it was during this period
 * Examples: Classic 0.0.12a, Classic 0.24_SURVIVAL_TEST, Classic 0.25_05 SURVIVAL TEST, Classic 0.28_01
 * Classic servers should begin with "Classic Server"
 * Example: Classic Server 1.3
 * Classic 0.30 should be: Classic 0.30c, 0.30s, 0.30c-renew
 * Indev versions were not labeled by Mojang. They should begin with "Indev" and if it is a 0.31 Indev it should begin with "Indev 0.31" then followed by year, month, day with no spaces. If there were multiple versions in the same day they should be followed by a dash (-) and then the number for which place it was
 * Examples: Indev 0.31 20091223-2, Indev 0.31 20100202, and Indev 20100212-2
 * Indev 0.31 20100113 (Creative) has the added parentheses for the missing version
 * Infdev should begin with "Infdev" and uses the same date formatting as Indev
 * Examples: Infdev 20100327, Infdev 20100420, and Infdev 20100625-2
 * Infdev 20100629 should be called Alpha v1.0.0
 * Alpha versions should begin with "Alpha" and have a v followed by the numbers. Common mistake: there is no . or space between the v and the first number (Alpha v1.0.1 not Alpha v.1.0.1 nor Alpha v 1.0.1).
 * Examples: Alpha v1.1.2 and Alpha v1.2.0
 * Alpha servers should begin with "Alpha Server"
 * Examples: Alpha Server 0.1.2-1 and Alpha Server 0.2.2_01
 * Beta versions should begin with "Beta" to signify this version span
 * Examples: Beta 1.2, Beta 1.6.6, and Beta 1.7_01
 * Beta 1.6 Test Build 3 should have each words' first letter capitalized
 * Prereupload and reupload should be followed by a dash (-) and then the number for which place it was.
 * Examples: 13w06a-1 and 13w06a-2

Block and Entity Renders
Infoboxes should generally contain an isometric render of the page's content. To make these images, you can use the Isometric Renders mod created by glisco.

To create a render with Isometric Renders, the command  can be used. More information on the mod's functions is available in its wiki.

Screenshots
Rules:
 * 1) If player needs to be in screenshot, it should have Steve default skin
 * 2) Item tooltip, potion effect box, data from   command should fit whole canvas.
 * 3) Unnecessary background should be erased.