Template:History/doc

This template is for displaying historical changes to an item, mob or any gameplay features for Hypixel SkyBlock.

Inspiration
This template is inspired by the Minecraft's Wiki Template:History with date and automatic version support for Hypixel SkyBlock Wiki.

Head
Required at the start of the History section to properly open the table with a  tag.

Header
1
 * Syntax

The header returns which version of Hypixel Skyblock belongs to: SkyBlock Prototype or SkyBlock.

If you want to note something before the item was even released, skip the header and use the entry row.

produces
 * Example

Entry row
Each row represents a History date/version entry.

1

produces
 * Example

The date is in (almost) always required, as it provides context to when a change happened. If the date of a change wasn't officially announced, use Links to point to the source or leave no link.
 * Acceptable date format is YYYY/Month DD. Example: 2019/October 11.
 * Short (3 letter) month names are accepted. Example: 2019/Aug 2.
 * Day number for days between 1st and 9th can be written as both 01 and 1.
 * Instead of date, version number can be used. Example: 0.7.1 is the same as 2019/September 11.
 * In some cases, special aliases can also be used. List of available ones can be found here.
 * If the the exact date is unknown, leave the field empty or type in Unknown. To add a custom label, use Unknown;Label. The default label is "Unknown Date".
 * Dates recorded are according to Hypixel Server Time (5 hours behind UTC).

This field is not case sensitive. This means that any input, no matter if the letters are capital or not, will be valid.

produces
 * Example

produces
 * Example 2

The link is optional and is only used when the change isn't mentioned in Changelog. Declare an external link using the named parameter.


 * Example
 * June 10 is not the official patch date, therefore would've broke if left without an external link.

produces

For a change without a source (not recommended), set to NONE.

produces
 * Example

Version should be automatically applied based on the date input. If there's a new patch version, add it to Module:History/Aliases. There are 2 possible inputs to this parameter:
 * any string. The displayed version will always be displayed as the specified in this parameter.
 * NONE (not case sensitive). The version will be forcefully hidden.


 * Example
 * June 11 is the 0.1 patch, still shows up if we don't declare it.

produces


 * Example 2
 * June 11 is the 0.1 patch, but since we declared, the version will show up as 0.5.2.

produces


 * Example 3
 * June 11 is the 0.1 patch, but since we declared, the version will not show up.

produces

Multiple changes
If there are multiple changes within a numbered version/date, just add it as another parameter at the end.

produces
 * Example

Footer
Required at the end of the History section to properly close the table with a tag.

Full Example
produces