Minecraft Wiki
Don't have an account?
Register
Register
Minecraft Wiki
Minecraft Wiki
7,425
pages
in: Minecraft Wiki talk page archives

Talk: Community portal/Archive 32

< Minecraft Wiki talk:Community portal
Back to page
Sign in to edit
(Extending the duration to 4 months)
Tag: missing signature
Line 1,110: Line 1,110:
 
| [[Bedrock Edition beta 1.16.210.59|beta 1.16.210.59]] || 1.16.210.59 || || 1.16.210.59 || 1.16.210.59
  
| [[Bedrock Edition beta 1.16.210.59|beta 1.16.210.59]] || 1.16.210.59 || || 1.16.210.59 || 1.16.210.59
 
|}--<span style="font-family:Minecraft">{{ItemLink|id=woodland explorer map|User:SkyEye FAST|SkyE}}<span style="font-size:10px"> | [[User talk:SkyEye FAST|Talk]] · [[Special:Contribs/SkyEye FAST|Contributions]] · [[Special:Logs/SkyEye FAST|Logs]]</span></span> 06:51, 17 February 2021 (UTC)
  
|}--<span style="font-family:Minecraft">{{ItemLink|id=woodland explorer map|User:SkyEye FAST|SkyE}}<span style="font-size:10px"> | [[User talk:SkyEye FAST|Talk]] · [[Special:Contribs/SkyEye FAST|Contributions]] · [[Special:Logs/SkyEye FAST|Logs]]</span></span> 06:51, 17 February 2021 (UTC)
  +
  +
{{Clear}}
  +
== Minecraft Dungeons ==
  +
<div class="bulletless">
  +
[[File:Dungeons.svg|left||frameless|30px]] This section has been created to separate Dungeons wiki related topics and proposals from the sea of other topics in this portal, mainly for my own convenience. If this is of issue then please notify me of such so that I am aware to not do so in future. [[User:Raybeano99|<span style="color:#833ea8">🍍 '''Raybeano99'''</span>]] ([[User_talk:Raybeano99|Talk]]) 09:45, 16 February 2021 (UTC)
  +
  +
=== Extension to Style Guide ===
  +
:[https://canary.discord.com/channels/447104142729674753/715105427104202854/810562877483384842 Related discussion in Wiki Discord (2021-02-14)]
  +
As the dungeons wiki continues to expand there has become a desire and a need for a Style Guide that caters specificity to aspects that likely are not evident in general MCW pages or MC and MCE wikis. WIth [[MCD:Flames of the Nether]] and a large free update rapidly approaching bring a large quantity of new content, I believe it would be beneficial if we had something to guide Dungeons editors, including myself, to ensure consistency, convenience, and quality of pages and files.
  +
  +
This specific style guide can touch upon image naming schemes for dungeons equipment images (See: [[User:Raybeano99/MCD_EquipStyle]]), common page layouts for general articles, equipment articles, mission articles ect., inform about commonly used templates and appropriate scale values for using them, and probably much ,much more that I, myself, have not even thought about.<br>
  +
Preferably, this is to be viewed as an extension with tweaks upon the existing [[MCW:STYLE]] rather than a transcluded/duplicated page with some modifications. I have a few ideas on how this could be implemented:
  +
  +
'''Style 1''' - Append onto existing [[MCW:STYLE]] page.<br>
  +
* A new section could be created and enveloped within a distinctive #f4efe6 coloured box and text to ensure viewers recognise that the contained information is specific for the Dungeons WIki. Alternately, dungeons specific information are appended onto existing sections and subsections.
  +
* {{DuMiscSprite|Positive}} Clear that the information is an extension rather than a replacement or equivalent.
  +
* {{DuMiscSprite|Positive}} Centralised - Come one, come all, all ye need lies within a single page of wonderful info.
  +
* {{DuMiscSprite|Positive}} Most exposure to all editors of the wiki - More feedback, critique, and viewpoints from editors to ensure that the style guide is constructed up to a high standard. Also more users are likely to view it.
  +
* {{DuMiscSprite|Positive}}{{DuMiscSprite|Negative}} Flow, bit of a double edge - Centralised page would allow the whole [[MCW:STYLE]] to be read without trying to find other places for info. However, this may flow too well. Users may not recognise the section as dungeons specific, even with crystal clear visual elements and text, and apply the information onto non-dungeons pages, or miss/disregard the information altogether.
  +
* {{DuMiscSprite|Negative}} Expansion concerns - The existing style guide may become formidably long over time as the dungeons specific section expands and adds detail.
  +
  +
'''Style 2''' - A subpage of [[MCW:STYLE]]. <br>
  +
* A page to contain the dungeons specific information. linked by a visually-distinct hatnote on the [[MCW:STYLE]].
  +
* {{DuMiscSprite|Positive}} Still clear that the information is an extension rather than a replacement or equivalent.
  +
* {{DuMiscSprite|Positive}} Expansion concerns are no longer a concern.
  +
* {{DuMiscSprite|Positive}} Flow concerns mitigated - Information not all in one place thus the distinction that the information is for dungeons specifically is more clear.
  +
* {{DuMiscSprite|Positive}} Moderate exposure to all editors of the wiki - Likely less exposure than '''style 1'''.
  +
* {{DuMiscSprite|Negative}} There must certainly be a clear negative somewhere but I am unable to think of one.
  +
* <code>MCW:Style Guide/Dungeons</code>, <code>MCW:Style Guide/MCD</code> perhaps?
  +
  +
'''Style 3''' - A page within the [[Minecraft Dungeons]] namespace. <br>
  +
* A page to contain the dungeons specific information close to home in the dungeons. linked by a visually-distinct hatnote on the [[MCW:STYLE]].
  +
* {{DuMiscSprite|Positive}} Style - All the visual glory of the dungeons is applied onto the page.
  +
* {{DuMiscSprite|Positive}} Expansion concerns are no longer a concern.
  +
* {{DuMiscSprite|Positive}} Flow concerns mitigated - Information not all in one place thus the distinction that the information is for dungeons specifically is undoubtedly clear, especially with the dungeons namespace.
  +
* {{DuMiscSprite|Negative}} Least exposure to all editors of the wiki - Probably less exposure than '''style 1''' or '''style 2'''.
  +
* {{DuMiscSprite|Negative}} Probably another negative exists but I am unable to think of one.
  +
* <code>MCD:Style Guide</code> perhaps?
  +
  +
I have personal preference for the dungeons style guide extension to become its own page in some form that '''style 2''' and ''' style 3''' provides.
  +
  +
* 🤔 Would this lead to further specificity for other MCW pages such as the portal, tasks and projects? Would that be a concern? Could further pages make things more cumbersome and difficult?
  +
[[User:Raybeano99|<span style="color:#833ea8">🍍 '''Raybeano99'''</span>]] ([[User_talk:Raybeano99|Talk]]) 09:45, 16 February 2021 (UTC)
  +
  +
: '''Style 1'''
  +
:: I don't fully agree with this approach. Pertaining to keeping different kind of information simultaneously can be difficult to navigate and may lead to some confusion. A similar problem to this is the difference of information between Java and Bedrock. So as to resolve, the community decided to use {{tl|in}}/{{tl|only}} whenever the provided information contain disparities. This solution should not be used in terms of information that are fundamental to the wiki, like style guides. Another solution such as adding a background color or new section wouldn't help as much. Furthermore, similar styling to background color has already been defined and it requires new knowledge for people to realize the distinction.
  +
: '''Style 2'''
  +
:: I totally agree in separating the page from the main style guide. By separating the page, there will be more freedom for expansion whilst not polluting the current page with MCD guides. Regarding misdirections, they are enough to be resolved by using a hat note or message box. For page name, I would say that Minecraft_Wiki:Style_guide/Minecraft_Dungeons is good enough.
  +
:::Before talking about extensions to the style guide, maybe the editors of Minecraft Dungeons articles could work harder to follow the basic style guidelines that already exist, such as not using title case in headings, not capitalizing things in text that aren't proper nouns, refraining from filling articles with indiscriminate lists of trivia (which I have worked hard to clean up), and so on. The last thing we need is new guidance that conflicts with or creates exceptions to guidelines we already have. [[User:Amatulic|Amatulic]] ([[User talk:Amatulic|talk]]) 02:38, 1 June 2021 (UTC)
  +
  +
: '''Style 3'''
  +
:: It would be more appropriate to put meta information in the Minecraft Wiki namespace. As for MCD:Style, I guess it can be used as a redirect to the MCW namespace for shortcut. Also I wouldn't personally be bothered with the design aspect of the page.
  +
: In addition, I feel like the sidebar could have the style guide to link specifically when you are in the MCD namespace. Thus resolving the concern of exposure of the page, especially to MCD editors. Other maintenance/community pages like community portal, projects, etc. shouldn't be a concern, at least for now. – [[User:ItsPlantseed|ItsPlantseed]] ⟨[[User talk:ItsPlantseed|₰]]|[[Special:Contribs/ItsPlantseed|₢]]⟩ 11:20, 16 February 2021 (UTC)
  +
  +
::: Having a dynamic sidebar that alters to suit the namespace the user is in would be a brilliant implementation and not just for the style guide exposure. I do recall a discussion in the discord where an issue that prevents namespace dependent sidebars from functioning was mentioned. I suppose until that is resolved, we can’t poke the sidebar in a dynamic fashion. Could have Dungeons Style Guide be under Style Guide until that fix arrives.
  +
  +
::: Style 1 could certainly end up becoming messy and unclear for all members involved, I agree with your views.<br>
  +
::: Style 2 & 3 design aspect is agreeably low priority and appropriate location should have possess weight. Some design aspects can be determined by the page through the source so things can be solved on that front.<br>
  +
:::<code>Minecraft_Wiki:Style_guide/Minecraft_Dungeons</code> with <code>MCD:Style</code> and <code>MCW:Style Dungeons</code> as redirects perhaps? Maybe only the one redirect shortcut is required. [[User:Raybeano99|<span style="color:#833ea8">🍍 '''Raybeano99'''</span>]] ([[User_talk:Raybeano99|Talk]]) 14:55, 16 February 2021 (UTC)
  +
  +
=== Centralised Datapage ===
  +
:[https://canary.discord.com/channels/447104142729674753/715105427104202854/807011683569893386 Related discussion in Wiki Discord (2021-02-04)]
  +
In the Dungeons namespace, there are multiple pages that duplicate the same information that must be kept updated, consistently styled, and worded correctly. For instance:
  +
* [[MCD:Enchanting]], [[MCD:Weapon]], [[MCD:Armor]], and [[MCD:Artifact]] share the same information with the main pages for the individual pages of the specified thing (ie: [[MCD:Burning]], [[MCD:Sword]], [[MCD:Crossbow]], [[MCD:Grim Armor]]) and, with respect to equipment, [[MCD:Drops]], [[MCD:Daily Trials]], the main page for a individual location (ie: [[MCD:Creeper Woods]]) and, in future, [[MCD:Difficulty]] to an extent.
  +
Some of these pages present the information in different styles to match the context of these pages.
  +
  +
To make numerous edits across multiple pages is tiring, time-consuming, introduces error, and new editors may be unaware of the different information location. A centralised place to edit this frequently used information will be immensely helpful. One edit to induce into many edits. <br>
  +
I am unaware on how to construct such a thing and implement it in a way that is accessible to locate, trivial to edit, future-proof, and easy to implement into pages.
  +
  +
Please share your thoughts on this and how such a thing could be constructed. A dedicated [[Sandbox]] page with subpages could be created for testing purposes. <br>
  +
[[User:Raybeano99|<span style="color:#833ea8">🍍 '''Raybeano99'''</span>]] ([[User_talk:Raybeano99|Talk]]) 09:45, 16 February 2021 (UTC)
  +
: UPDATE: Consideration for the use of Cargo. Discussed at [https://canary.discord.com/channels/447104142729674753/715105427104202854/826112836451041321 Wiki Discord 2021-03-2021]
  +
  +
=== Wiki channel in the Official Dungeons Discord ===
  +
This is a thought that has been swimming around in my mind for some time. The Dungeons wiki does not have a huge quantity of editors that are immensely experienced with the game and its internals. There is also, unfortunately, a partial community consensus that any dungeons wikis are untrustworthy and information from them is to be treated with caution. This is something we need to resolve and gain the trust in the community.<br>
  +
The [https://discord.gg/minecraftdungeons Official Dungeons Discord] hosts a large quantity (but not overwhelmingly large!) of experienced players that educate, advise, and guide others but are unfamiliar with wiki editing. I believe there to be a fiction when learning how to edit the wiki with there being a few places to learn such with huge exposure. This wiki, MediaWiki Wiki, Help Wiki and the [[MCW:Discord]] (side note: I am very glad the wiki hosts a Discord Server.) are all brilliant places to start learning how to wiki edit however, they are not frequently seen or you need to ask around and explore to find them.
  +
  +
As a moderator of the dungeons discord, I have been able to internally propose the idea of a wiki dedicated channel - a place for dungeons folk to comfortably discuss wiki pages and information without worrying about unintentionally misinforming other players or being disruptive to existing channels. Information and links directing to wiki rules, help wikis, frequently used templates, and some wiki editing tools (ie: the [https://docs.google.com/spreadsheets/d/16PSoRB1my7Sf4iiBLSoK90PsTL9nzJf2NgKt5cijgrw/edit?usp=sharing generate spreadsheet] on [[User:Raybeano99]] userpage) will be made available as a pinned message. Speculation and general chat will not be permitted in the channel and will be held to a high standard. Specialised roles have not been discussed and will be handled internally.<br>
  +
The internal proposition was to gain feedback and thoughts from the rest of the admins and the moderators before establishing further communications. Unfortunately, the response turnout has been unexpectedly low however, none have made an explicit deny to the channel implementation. Hence me making communications here to gain your thoughts whether ye be a passer-by, an editor, admin or above to ignite the idea again. <br>
  +
I am in belief that implementation would not immediately yield desired output... could be slow, could be nothing, maybe something worth the attempt. Can always be removed quicker than the time taken to make the channel. Reverting and backtracking is not a concern
  +
  +
* {{DuMiscSprite|Positive}}{{DuMiscSprite|Negative}} Exposure - More people experienced with the game will be informed of the wiki's existence and can contribute! This could also increase the frequency of disruptive, defacing edits.
  +
* {{DuMiscSprite|Positive}} New place to learn - Another place for editors to gain assistance from other editors.
  +
* {{DuMiscSprite|Negative}} Communication fragmentation - This, personally, is a huge concern. Could be mitigated by instructing users to provide the discord message link of the first substantial message in a conversation in the talk page of the page in discussion.
  +
* 🤔 What about Wiki Discord's #dungeons-wiki channel? - Something to be considered is if the implementation of a wiki channel on the official discord would have any impact on the existing Wiki Discord.<br>
  +
[[User:Raybeano99|<span style="color:#833ea8">🍍 '''Raybeano99'''</span>]] ([[User_talk:Raybeano99|Talk]]) 09:45, 16 February 2021 (UTC)
  +
: Neutral to weak oppose. Agree with the three points (except I'd say the first point is more positive than negative, rather than positive/negative to an approximately equal degree). I'd also like to add a fourth point (which is a rather major one for me). As I understand, the Dungeons server is run by Mojang, who may have a conflict of interest against the community in a number of aspects. As such, I'm not very positive about game developers controlling communities. Mojang in specific isn't a company I trust given some historical actions and additional information. --[[User:AttemptToCallNil|AttemptToCallNil]] ([[User talk:AttemptToCallNil|talk]]) 18:23, 8 April 2021 (UTC)
  +
  +
=== Tabbed Mob pages ===
  +
: Alt title: Merge “base” and “variant” mobs into a singular page.
  +
  +
Mobs {{in|dungeons}} have different tiers (a term used by [https://help.minecraft.net/hc/articles/360044268272-Minecraft-Dungeons-Patch-Notes 1.8.0.0 patch notes] referring to apocalypse plus changes) that exhibit the same behaviour but with, generally, increased statistics. For example. {{MCD|Zombie}} is tier I, the dagger variant of {{MCD|Armored Zombie}} is tier II, and the sword variant of {{MCD|Armored Zombie}} is tier III.
  +
  +
Rather than visually appending the information upon the “base” mob (as it would encumber the page), or, what is currently the case, separate pages for Tier I and Tier II&III, a single page could implement a tabbed experience that would allow viewers to select which tier of mob they wish the page, section, or specific component to display.
  +
  +
Perhaps something similar to the [https://terraria.fandom.com/wiki/Template:Npc_infobox infobox] used at
  +
[https://terraria.fandom.com/wiki/Blue_Slime Terraria's Blue Slime]
  +
but fashioned so it that would influence the information on the page. This could be under the page title, attached to each section, or applicable components such as tables.
  +
  +
Unsure on whether tabbed consolidation should include Jungle and Frozen variants of Zombie, Skeleton, and Creeper…these are tier I mobs but with additional and/or modified attacks. Could that be considered significantly altered behaviour?<br>
  +
Also are charged creepers considered a higher tier of creeper? Also husks and drowned? Ancients?
  +
  +
* {{DuMiscSprite|Positive}} Reduction of duplicated or fragmented applicable information.
  +
* {{DuMiscSprite|Positive}} Makes explicit that the mobs are related
  +
* 🟡 Less pages for near identical mobs and thus less entries on {{MCD|Mob}}. Could possibly be beneficial?
  +
* {{DuMiscSprite|Negative}} Potential to decrease accessibility.
  +
* {{DuMiscSprite|Negative}} Likely to increase complexity of page source and hinder visual editors.
  +
  +
[[User:Raybeano99|<span style="color:#833ea8">🍍 '''Raybeano99'''</span>]] ([[User_talk:Raybeano99|Talk]]) 17:34, 2 April 2021 (UTC)
  +
</div>
  +
: Oppose, I don't think this is a useful way of using tabs. Tabs tend to cause accessibility and technical problems as you said (I'd also add that links to anchors in non-default tabs may not work). Fandom staff keep telling editors that research has shown tabs are not an effective way of conveying information as tabs other than the first will be ignored by a large portion of readers. I'm not sure about your third point, I'd say this isn't a factor at all. About the second point, is "fun related" a typo for "unrelated"? I'm not sure what "fun related" means. --[[User:AttemptToCallNil|AttemptToCallNil]] ([[User talk:AttemptToCallNil|talk]]) 18:29, 8 April 2021 (UTC)
  +
:: Typo… not sure how fun got in there. Has been corrected.<br>
  +
:: Yeah I could envision folk not recognising the tabs as clickable and missing the information enclosed within them thinking about it more. Wondering if there are other ways that the merge could be achieved… or perhaps the standard information suffixing might not be as encumbering as initially imagined. Would love any different ideas. [[User:Raybeano99|<span style="color:#833ea8">🍍 '''Raybeano99'''</span>]] ([[User_talk:Raybeano99|Talk]]) 18:54, 8 April 2021 (UTC)

Revision as of 13:57, 15 June 2021

This page is an archive of past discussions for the period of January to April 2021. Do not edit the contents of this page. 
If you wish to start a new discussion or revive an old one, please do so on the current talk page.

Consistency in "Pre-Release" Capitalization

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.
Article titles should follow the official name. Pre-release and Pre-Release spelling appear in different dates. However, feel free to create redirects from r -> R and vise versa.Humiebeetalk contribs 21:25, 10 January 2021 (UTC)

While editing the server.properties page, I noticed that there is considerable inconsistency in how "Pre-Release" is capitalized across the wiki. Some pages choose to uppercase the "R" in "Release", some do not. Some choose to redirect the opposite case, some do not.

For example, 1.14.4 Pre-Release 1 is an uppercase "R" and trying to navigate to "1.14.4 Pre-release 1" fails. On the other hand, 1.16.4 Pre-release 1 is a lowercase "r", and trying to navigate to "1.16.4 Pre-Release 1" similarly fails. Some pages (e.g. 1.15 Pre-release 5) have a redirect but many do not. The net effect of this is that editors have no idea which capitalization is "correct", or even which one will work correctly. It leads to overall inconsistency and unnecessary redirects across the Wiki.

My suggestion is for the Wiki to come to a consensus on which capitalization should be used. Personally, I feel that "Pre-Release" with an uppercase "R" should be preferred, as that is what Mojang uses in its official communications. Once consensus is reached, incorrect pages should be moved to the correct title, and any errant capitalization in article bodies fixed.

AMNOTBANANAAMA (talk) 23:48, 5 January 2021 (UTC)

The name of pre-releases follow the name in-game, so  Weak oppose The Great Spring (talk | contribs) (Tagalog translation) 23:50, 5 January 2021 (UTC)
If the decision is to prefer "pre-release" as the page names I am fine with that, as long as it is consistent. The current inconsistency is my primary concern, ultimately which one is chosen is less important to me. AMNOTBANANAAMA (talk) 00:01, 6 January 2021 (UTC)
For example, if you want to put this at the start it would be
“

1.16.4 Pre-release 1 (known as 1.16.4-pre1 in the launcher) is the first pre-release for Java Edition 1.16.4, released on October 15, 2020, which adds the social interactions screen and fixes two bugs.

 „
instead of
“

1.16.4 Pre-Release 1 (known as 1.16.4-pre1 in the launcher) is the first pre-release for Java Edition 1.16.4, released on October 15, 2020, which adds the social interactions screen and fixes two bugs.

 „
The Great Spring (talk | contribs) (Tagalog translation) 00:10, 6 January 2021 (UTC)
We follow the in-game names, so they are not to be moved. However, feel free to make redirects for the opposite capitalization. Dhranios (talk) (Join the wiki videos project!) 09:32, 6 January 2021 (UTC)

More Facts In Did You Know...

On the main page, the Did You Know... section always has the same 5 facts. I think it would be neat if there was a large pool of random facts and every time the page loads, it picks a random 5 from that list. Any thoughts would be appreciated! || Remember this thing? File:Nether Reactor Core Revision 1.png Because I do. --Ninji2701 03:17, 27 December 2020 (UTC)

The did you know relies on a certain template, Template:DidYouKnow. It does not always have the same facts, it refreshes every day. There are not 5 facts, here are all the facts. If you want to add more facts, you can add them in the editcopy. Keep in mind you can edit the editcopy and add what you think is good, but it will not show up on the front page until an admin decides they belong there. Blockofnetherite Talk Contributions 04:45, 27 December 2020 (UTC)
Oh, cool! I guess this topic is totally irrelevant then. || Remember this thing? File:Nether Reactor Core Revision 1.png Because I do. --Ninji2701 13:50, 27 December 2020 (UTC)

Repurpose

I personally think that the template should show more than 5 facts. It could show 7 facts instead of 5. The reason is that the Minecraft Wiki/editcopy page shows too few facts on the template, so if we increase a little bit the amount of facts this can be solved. Thejoaqui777 (talk) 23:12, 18 March 2021 (UTC)

5000 content pages milestone

I just wanted to say that I noticed, as of now, Special:Statistics lists exactly 5,000 content pages on this wiki. Amatulic (talk) 03:00, 16 January 2021 (UTC)

I noticed that a few days back, so you aren't the first to see this. James Haydon (talk) 04:02, 16 January 2021 (UTC)
BDJP007301 created the 5000th article yesterday. Also, does this also includes deleted pages? TheGreatSpring (talk) 04:22, 16 January 2021 (UTC)
It does not, hence why it has become this milestone several times already. Dhranios (talk) (Join the wiki videos project!) 05:53, 16 January 2021 (UTC)
Well there are subpages of articles which are not articles (many of them are templates only meant to be transcluded on one page) which are counted as articles, which means there are probably less than 5,000 "proper" articles. (Note that redirects, project pages, template pages, category pages, file pages, user pages, etc. are not counted as articles. )Fadyblok240 (talk) 17:36, 21 January 2021 (UTC)

Articles about Mojang employees: A proposal

Reviving both this discussion from 2015 and this discussion from 2019-2020, I feel like it should finally be time to take action regarding articles about Mojang employees, whether they are notable or not. I'm using the Wikipedia policy on biographies of living persons as a blueprint for this, so bear with me here.

  • We should try to include as much information on employees that is publicly available through reliable sources, whether it be through LinkedIn profiles, interviews with publications such as news sites, or simply through the Twitter accounts of the employees themselves. As long as the information is available publicly, it should be documented on the wiki, sourced back to the article or tweet in question.
  • However, there has to be a limit as to what information should indeed be allowed on here. Of course, its general understanding that emails, addresses, and phone numbers are never to be added to articles out of respect for privacy. In regards to concessions that have been made in the past, such as the situation with Ez, or retracting information that had been OK up until recently, such concessions should be reviewed as to whether they should remain as is, or be considered null and void pending as to when this policy does become active.

Understanding that this is a style guide policy, I figured it would be best to instead post it here, considering that this policy would cover several hundreds of employees of one company.

The proposed change to the policy is as follows, which would be separated from the "Notability" section and split into its own section (new additions in bold):

“

Articles about people are only allowed if the person in question is a developer of Minecraft and/or either a part of or closely related to Mojang Studios. The article should cover information about the person that is publicly available through reliable sources, and should remain neutral and fair to the person. Self-published sources, such as tweets or books, are not allowed unless the person is the one who authored or published it. Edits to the article about the person may be reverted / deleted if they contain phone numbers, email, or postal addresses.

 „

This is just a stepping stone. I am open to any additional input regarding any further changes to this. BDJP (t|c) 19:19, 2 February 2021 (UTC)

I still think this should be taken further, and say that articles should only exist for notable employees where the majority of the content is about their work. We shouldn't encourage going into details about personal lives and such, which having all these stub articles does.  Nixinova   T   C   19:29, 2 February 2021 (UTC)
Definitely keep the personal life stuff to a minimum at best. BDJP (t|c) 20:42, 2 February 2021 (UTC)
In my opinion, we should keep any pages that have a lot of content (pages without stubs) but pages with stubs should be put into like a draft. Anyone is free to make a page but it needs more content. As for not having like personal details, I also support that but a notable exception would be Helen Zbihlyj as she directly put a little bit of her personal life on her user page as it is a primary and the most reliable source possible. I would like the employee pages to also have more about their work as well and all those stub articles can be clumped into an Employees article.
All in all, I  Support keeping all pages which have enough content and  Removing or converting any pages with a stub and have no content (for instance, Peter Hont which is just one of the many pages that has no info, only saying that they work in Minecraft Dungeons.) For birth dates, I really don't see any harm if they posted it on twitter or some other social media thing. Also I wish to  Remove all pages with no sources as well.Humiebee (talk) 21:35, 2 February 2021 (UTC)
I’ve created an example of how an expanded article would look here. BDJP (t|c) 01:02, 9 February 2021 (UTC)
I  Support the revised article.Humiebee (talk) 03:05, 15 February 2021 (UTC)
I'm going to wait on any further comments for a week, but if there are no further objections then I will implement this on the bio page. BDJP (t|c) 14:36, 19 February 2021 (UTC)
Support the new proposal, but it would make absolutely no sense for the new guideline to be part of the style guide but not part of the notability guideline. What about splitting the notability guidelines from the style guide? Fadyblok240 (talk) 23:12, 19 February 2021 (UTC)

Are pufferfish passive, neutral or hostile

Personally, I think that pufferfish are passive because they can't chase you but some users change "Passive" to "Neutral" or "Hostile". Are pufferfish passive, neutral or hostile? TheGreatSpring (talk) 08:08, 7 February 2021 (UTC)

Per Talk:Pufferfish#Pufferfish behavior, we stated that they are passive, so I think that they should stay as Passive. Thejoaqui777 (talk) 22:55, 7 February 2021 (UTC)

Splitting PS4 history

Recenty, RondiMarco splits the PS4 part from the LCE section without discussion. Can we split the PS4 part or not? Any thoughts? The Great Spring (talk | contribs) (Tagalog translation) 12:11, 6 January 2021 (UTC)

 Neutral, while it is done the same with PE and bedrock, PS4 is a legacy console edition, as it was also replaced by bedrock. I don't see harm in doing it this way, nor harm in reverting it. Dhranios (talk) (Join the wiki videos project!) 12:13, 6 January 2021 (UTC)
 Oppose PS4 is part of LCE, no reason to split its history.  Nixinova   T   C   19:29, 7 January 2021 (UTC)
 Comment I get your point, but the PS4 edition outlasted all the other Legacy Console editions, and was the only legacy console version to have the Texture Update. James Haydon (talk) 19:32, 7 January 2021 (UTC)
Barely, only for like 10 updates.  Nixinova   T   C   21:27, 10 January 2021 (UTC)
True, they only spanned 1.14, or Bedrock Edition 1.8.0 - 1.13.0.Humiebeetalk contribs 21:30, 10 January 2021 (UTC)
 Weak support becuase of consistancy with pe and be but it is part of lce and is diffferent than pe and be as they are separated until the Better Together Update but ps4 IS part of lce. Idk, I would keep it though.Humiebeetalk contribs 21:45, 30 December 2020 (UTC) 22:21, 7 January 2021 (UTC)

Something discussing renewability of the Lava Bucket and other items that are not renewable in snapshots but are going to be in the full release

Yes, I know that the ip constantly got reverted for changing it, they did have a good point but the wiki uses current status, not upcoming status. The ip got reverted with understandable edit summaries and I personally would revert the ip. They were doing it in good-faith though. Something odd about that is that the template is the {{upcoming}} template, implying that the thing that is upcoming IS upcoming in <version>. In the case of 1.17, the full release. Now the wiki trys to be as informative as possible and trys to give the reader a clear understanding. In my opinion, I am  Semi-weak support. It would be confusing for the reader if they watched like say for example, xisumavoid and went to the minecraft wiki. They would notice that the renewability of lava buckets would be incorrect, misleading the reader. Note that I mean No‌[until JE 1.17]/Yes‌[upcoming: JE 1.17] Any thoughts?Humiebeetalk contribs 22:35, 7 January 2021 (UTC)

The same can be said the other way around. If we end up saying yes in 1.17, while it's not in the snapshots yet, people who open the snapshots will be presented with misinformation.
It's better to stick with the current latest release and snapshot info, not the whole planned update. (Plans can change, after all...) Dhranios (talk) (Join the wiki videos project!) 23:33, 7 January 2021 (UTC)
True... but it would be more helpful in general becuase more Java Edition players use Java Edition 1.16.4 than .Humiebeetalk contribs 23:37, 7 January 2021 (UTC)
For those people, those templates don't really concern them. When the update releases, they'll check the update page instead and go from there. Dhranios (talk) (Join the wiki videos project!) 23:40, 7 January 2021 (UTC)

Wanted Page: Moving minecart

The minecarts that move are supposed to be mobs / entities, right? -THENOMNOM (talk) 00:26, 11 January 2021 (UTC)

Yes. They are entities. TheGreatSpring (talk | contribs) (Tagalog translation) 00:28, 11 January 2021 (UTC)
Minecarts themselves are already entities. Moving minecrafts are no different, just that they are moving, similar to a player walking. So no need for a new pageHumiebee (talk) 00:39, 11 January 2021 (UTC)
Exactly, in the same way as evoker fangs. They only damage they player and have no real behavior nor do they interact with them. James Haydon (talk) 00:51, 11 January 2021 (UTC)

Should Caves & Cliffs features in Bedrock Edition be considered from 1.17.0 or from 1.16.210 in history sections

There's a bit of a inconsistency with Caves & Cliffs features in added in the betas of 1.16.X in the form of Experimental Gameplay, for example, this is the history section for pointed dripstone:

Upcoming Bedrock Edition
1.17.0
{{Extension DPL}}<ul><li>[[Honeycomb|Honeycomb]]<br/>{{distinguish|Honeycomb Block}}
{{Item
| image = Honeycomb.png
| renewable = Yes
| stackable = Yes (64)
}}

'''Honeycombs''' are [[item]]s obtained from [[bee nest]]s and beehives.

== Obtaining ==
{{See also|Tutorials/Honey farming}}
When a bee nest or beehive at {{cd|honey_level}} 5 is [[shear]]ed, it drops 3 honeycombs and angers any [[bee]]s inside, causing them to attack. Having a lit [[campfire]] or lighting a [[fire]] underneath the nest or hive prevents the bees from becoming hostile.

A [[dispenser]] with [[shears]] inside can be used to shear the nest or hive without angering the bees. A honeycomb item drops out after using the shears.

== Usage ==

=== Signs ===

{{Control|Using}} a honeycomb on a [[sign]] or a hanging sign prevents the sign from being edited.

=== Waxing ===
{{Control|Using}} a honeycomb on a [[block of copper]] changes the block into its waxed variant, preventing oxidation of the copper.

=== Crafting ingredient ===
{{crafting usage}}

== Sounds ==
{{edition|java}}:
{{Sound table
|sound=Beehive shear.ogg
|subtitle=Shears scrape
|source=neutral
|description=When honeycombs are collected from a beehive
|id=block.beehive.shear
|translationkey=subtitles.block.beehive.shear
|volume=0.8
|pitch=1.0/0.9/0.8
|distance=16}}
{{Sound table
|sound=Wax on1.ogg
|sound2=Wax on2.ogg
|sound3=Wax on3.ogg
|subtitle=Wax on
|source=block
|description=When a honeycomb waxes something
|id=item.honeycomb.wax_on
|translationkey=subtitles.item.honeycomb.wax_on
|volume=1.0
|pitch=1.0/0.9/1.1
|distance=16
|foot=1}}

{{edition|bedrock}}:
{{Sound table
|type=bedrock
|sound=Beehive shear.ogg
|source=block
|description=When honeycombs are collected from a beehive
|id=block.beehive.shear
|volume=0.8
|pitch=0.8-1.0}}
{{Sound table
|sound=Wax on1.ogg
|sound2=Wax on2.ogg
|sound3=Wax on3.ogg
|source=neutral
|description=When a honeycomb waxes something
|id=copper.wax.on
|volume=1.0
|pitch=0.8-1.2
|foot=1}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Honeycomb
|spritetype=item
|nameid=honeycomb
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Honeycomb
|spritetype=item
|nameid=honeycomb
|id=591
|form=item
|foot=1}}

== Advancements ==
{{load advancements|Wax on;Wax off}}

== History ==
{{History|java}}
{{History||1.15|snap=19w34a|[[File:Honeycomb JE1.png|32px]] Added honeycombs.
|Honeycombs can be used to craft [[beehive]]s.}}
{{History|||snap=19w41a|Honeycombs can now be used to craft [[honeycomb block]]s.}}
{{History|||snap=Pre-release 3|[[File:Honeycomb texture change 1.15pre2 to 1.15pre3.gif|32px]] The texture file of honeycombs has been slightly changed. The color channel of transparent pixels are now filled to black. The in-game texture has not been changed.}}
{{History||1.17|snap=20w45a|Honeycomb can now be used to craft [[candle]]s and [[waxed copper]].}}
{{History|||snap=21w11a|Honeycomb can now be used to wax copper blocks by right clicking or dispensing honeycomb onto the block.}}
{{History|||snap=21w14a|Honeycomb can now be used to wax oxidized copper blocks.}}
{{History|||snap=21w19a|Honeycomb can no longer used to craft candles.}}
{{History|||snap=Pre-release 1|Honeycomb can once again used to craft candles.}}
{{History||1.20|snap=23w12a|[[Sign]]s and hanging signs can now be waxed with honeycomb to prevent them from being edited.}}

{{History|bedrock}}
{{History||1.14.0|snap=beta 1.14.0.1|[[File:Honeycomb BE1.png|32px]] Added honeycombs.}}
{{History|||snap=beta 1.14.0.4|[[File:Honeycomb BE2.png|32px]] The texture of honeycombs has been changed to match {{el|je}}'s.}}
{{History||Caves & Cliffs (experimental)|link=Bedrock Edition 1.17.0|snap=beta 1.16.210.57|Honeycomb can now be used to craft [[waxed copper]].
|Honeycomb can now be used to wax copper blocks by right clicking or dispensing honeycomb onto the block.}}
{{History||1.17.0|snap=beta 1.16.230.52|Honeycomb can now be used to wax oxidized copper blocks.}}
{{History||1.17.10|snap=beta 1.17.10.22|Honeycomb can now be used to craft [[candle]]s.}}
{{History||Next Major Update<br>(Experimental)|link=Bedrock Edition 1.19.80|snap=beta 1.19.80.22|[[Sign]]s and hanging signs can now be waxed with honeycomb to prevent them from being edited.}}

{{History|foot}}

== Issues ==
{{issue list}}


{{items}}

[[cs:Plástev medu]]
[[de:Honigwabe]]
[[es:Panal]]
[[fr:Rayon de miel]]
[[ja:ハニカム]]
[[ko:벌집 조각]]
[[pl:Plaster miodu]]
[[pt:Favo de mel]]
[[ru:Пчелиные соты]]
[[zh:蜜脾]]
[[Category:Renewable resources]]</li><li>[[Spyglass|Spyglass]]<br/>{{Item
| title = Spyglass
| image = Spyglass.png
| durability = 
| rarity = Common
| renewable = Yes
| stackable = No
}}
 
A '''spyglass''' is a [[tool]] used to zoom in on distant objects.

== Obtaining ==
=== Crafting ===
{{Crafting
  |B1=Amethyst Shard
  |B2=Copper Ingot
  |B3=Copper Ingot
  |Output=Spyglass
  |type=Tool
}}

== Usage ==
[[File:Steve scoping Spyglass.png|right|100px]] [[File:Alex scoping Spyglass.png|right|100px]]

To use a spyglass, the player selects it from the hotbar and clicks {{control|use}} while looking in the desired direction.

Spyglasses are used to zoom in on a specific location in the player's field of view (FOV). The spyglass changes the FOV to {{frac|1|10}} of the FOV set in [[options]]. By default, the FOV is set to 70° in ''Java Edition'' and 60° in Bedrock Edition, resulting in an FOV of 7° in ''Java Edition'' and 6° in Bedrock Edition through the spyglass. The player's FOV can be set from 30° to 110°, so the spyglass FOV can  range from 3° to 11°. Regardless of the situation, or status effects the player has, using the Spyglass always shows a FOV {{frac|1|10}} of the FOV set in [[options]].

A square vignette is applied when in use, similar to the effect when wearing a [[carved pumpkin]]. Pressing {{key|F1}} removes the vignette,{{only|java}}<ref>{{bug|MC-203575||The spyglass overlay goes away when pressing F1|WAI}}</ref><ref>{{bug|MCPE-125869||Spyglass's overlay don't go away even if the player toggles Hide GUI on/ Pressing F1|}}</ref> similar to a carved pumpkin. 

Hazy distant objects remain hazy when viewed in the spyglass. Mobs too distant to render also do not render in the spyglass. The spyglass shows a magnified view of what the player already sees.

The player is slowed down while watching through the spyglass. When the player uses the spyglass continuously for {{convert|1|minute|game tick}}, the interface is automatically closed.

If the player has a certain effect on their screen like [[fire]], the spyglass does not remove that effect on the player's screen.

[[File:Spyglass Zooming.gif|thumb|center|A spyglass being used to zoom in on a [[block of gold]] starting from normal FOV (70°).]]

== Sounds ==
{{edition|java}}:
{{Sound table
|sound=Spyglass use.ogg
|subtitle=Spyglass expands
|source=player
|description=When a player uses a spyglass
|id=item.spyglass.use
|translationkey=subtitles.item.spyglass.use
|volume=0.5
|pitch=''varies'' <ref group=sound>Can be 1.15, 1.33, 1.4, or 1.55</ref>
|distance=16}}
{{Sound table
|sound=Spyglass stop.ogg
|subtitle=Spyglass retracts
|source=player
|description=When a player stops using a spyglass
|id=item.spyglass.stop_using
|translationkey=subtitles.item.spyglass.stop_using
|volume=0.5
|pitch=''varies'' <ref group=sound>Can be 1.0, 0.8, or 0.9</ref>
|distance=16
|foot=1}}

{{edition|bedrock}}:
{{Sound table
|type=bedrock
|sound=Spyglass use.ogg
|source=player
|description=When a player uses a spyglass
|id=item.spyglass.use
|volume=0.5
|pitch=1.15-1.55}}
{{Sound table
|sound=Spyglass stop.ogg
|source=player
|description=When a player stops using a spyglass
|id=item.spyglass.stop_using
|volume=0.5
|pitch=0.8-1.0
|foot=1}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Spyglass
|spritetype=item
|nameid=spyglass
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Spyglass
|spritetype=item
|nameid=spyglass
|form=item
|foot=1|id=626}}

== Advancements ==
{{load advancements|Is it a Bird?;Is it a Balloon?;Is it a Plane?}}

== History ==
{{History||October 3, 2020|link={{ytl|DBvZ2Iqmm3M|t=25m21s}}|[[File:Spyglass JE1.png|32px]]<!-- [[File:Spyglass scope (pre-release).png|32px]]--> Spyglasses are revealed at [[Minecraft Live 2020]]. They were originally named "telescopes" and had an oval vignette.}}
{{History|java}}
{{History||1.17|snap=20w45a|[[File:Spyglass JE1.png|32px]] Added spyglasses.
|[[File:Spyglass scope JE1.png|32px]] The scope texture is currently a circle with glare spots.}}
{{History|||snap=20w46a|[[File:Spyglass scope JE2.png|32px]] The scope texture is now a [[glass]] square with a [[copper]] border.}}
{{History|||snap=20w48a|[[File:Spyglass JE2 BE1.png|32px]] The spyglass is now a 3D model instead of a flat sprite.
|[[File:Spyglass (texture) JE2.png|32px]] The texture of the spyglass has changed.
|A spyglass in use is anchored better to the player's "eye" when viewed in 3rd person.}}
{{History|||snap=21w05a|Copper ingots are now renewable via [[drowned]], making spyglasses renewable.}}
{{History|||snap=21w10a|[[File:Spyglass (item) JE3 BE1.png|32px]] Spyglasses have a new texture in the inventory. The 3D model is still used in the hand, similar to [[tridents]].}}
{{History||1.17.1|snap=Pre-release 1|[[File:Spyglass (texture) JE3.png|32px]] The texture of the spyglass model has changed.}}
{{History|bedrock}}
{{History||1.17.0|snap=beta 1.17.0.50|[[File:Spyglass JE2 BE1.png|32px]] [[File:Spyglass (item) JE3 BE1.png|32px]] Added spyglasses.}}
{{History|||snap=beta 1.17.0.52|Spyglasses are now available without enabling [[experimental gameplay]].}}
{{History|foot}}

== Issues ==
{{Issue list}}

== Trivia ==
*If {{command|item replace}} is used to place a spyglass on a player's head, the item appears stuck to the center of the player's face.

== Gallery ==
<gallery>
Villager Spyglass.png|Spying on [[villager]]s through a spyglass.
After using the spyglass at FOV 30 F1.png|Hiding the HUD removes the spyglass overlay.
Panda eating a spyglass.png|When eaten by a [[panda]], spyglasses cause [[missing texture]] particles to be produced.<ref>{{bug|MC-206684}}</ref>
JE 1.17 Development Telescope.jpg|The spyglass was originally called the telescope.
JE 1.17 Development Telescope 2.jpg|The telescope's overlay was originally round instead of square.
File:Ari Spyglass.jpg|How the spyglass looks in the third person.
Steve scoping Spyglass JE1.png|Steve using a spyglass before its 3D model was added.
Alex scoping Spyglass JE1.png|Alex using a spyglass before its 3D model was added.
File:Mangrove Portal.jpg|An [[allay]] peeking into view of [[Noor]]’s spyglass.
</gallery>

== References ==
{{Reflist}}

== External Links ==
*[https://www.minecraft.net/en-us/article/taking-inventory--spyglass Taking Inventory: Spyglass] – Minecraft.net on February 17, 2022

{{Items}}

[[Category:Renewable resources]]

[[de:Fernrohr]]
[[es:Catalejo]]
[[fr:Longue-vue]]
[[it:Cannocchiale]]
[[ja:望遠鏡]]
[[pl:Luneta]]
[[pt:Luneta]]
[[ru:Подзорная труба]]
[[zh:望远镜]]</li></ul>
beta 1.16.210.56Pointed Dripstone Base (D) JE1 BE1 Pointed Dripstone Middle (D) JE1 BE1 Pointed Dripstone Frustum (D) JE1 BE1 Pointed Dripstone Tip (D) JE1 BE1 Pointed Dripstone Tip Merge (D) JE1 BE1
Pointed Dripstone Base (U) JE1 BE1 Pointed Dripstone Middle (U) JE1 BE1 Pointed Dripstone Frustum (U) JE1 BE1 Pointed Dripstone Tip (U) JE1 BE1 Pointed Dripstone Tip Merge (U) JE1 BE1 Pointed Dripstone (item) BE1 Added pointed dripstone.

However, this is the history section for goats:

Bedrock Edition
1.16.200
{{Extension DPL}}<ul><li>[[Cooked Cod|Cooked Cod]]<br/>{{redirect|Cooked Fish|cooked salmon|Cooked Salmon}}
{{Item
| title = Cooked Cod
| image = Cooked Cod.png
| renewable = Yes
| heals = {{hunger|5}}
| stackable = Yes (64)
}}
'''Cooked cod''' is a food item obtained by cooking [[raw cod]].

== Obtaining ==

=== Mob loot ===
====Cod====
[[Cod]] always drops 1 [[Raw Cod|raw cod]] when killed, unaffected by Looting.<ref>{{bug|MC-212795||Salmon & Fish mobs are not affected by Looting}}</ref> If it is killed while on [[fire]], it drops 1 cooked cod instead.
====Dolphins ====
When killed, [[Dolphin|dolphins]] drop 0–1 raw cod. The maximum amount is increased by 1 per level of [[Looting]], for a maximum of 0-4 with Looting III. If killed while on fire, they drop cooked cod instead.
====Guardians and elder guardians====
[[Guardian]]s and [[elder guardian]]s have a 40% and 50% chance, respectively, to drop raw cod when killed. {{IN|java}}, cooked cod is dropped if a guardian is on fire when killed.

Guardians and elder guardians also drop a 2.5% chance to drop a random fish, with 60% of them being raw cod, which drops as cooked if the guardian was on fire. The chance of getting the fish drop is increased by 1% per level with [[Looting]] (for a maximum of 5.5% with Looting III), but the type of fish is not affected.
====Polar bears====
[[Polar bear]]s have a 75% chance of dropping 0–2 raw cod when killed. The maximum amount can be increased by 1 per level of Looting, for a maximum of 0-5 with Looting III. If killed while on fire, they drop cooked cod instead.
===Chest loot===
{{LootChestItem|cooked-cod}}

===Cooking===

Cooked cod can be obtained by cooking [[raw cod]] in a [[furnace]], [[smoker]], or [[campfire]]. 

{{smelting|Raw Cod|Cooked Cod|0,35}}

===Trading===

Novice-level Fisherman [[Villager|villagers]] have a 50% chance to sell 6 cooked cod for 6 raw cod and 1 [[emerald]].

== Usage ==

=== Food ===

To eat cooked cod, press and hold {{control|use}} while it is selected in the hotbar. Eating one restores {{hunger|5}} [[hunger]] and 6 hunger [[Hunger#Mechanics|saturation]].

=== Wolves ===

{{IN|Bedrock}}, cooked cod can be used to feed a wolf not at full health, healing by {{hp|5|mob=1}}. However, unlike other wolf food, cooked cod cannot be used to speed up the growth of baby wolves nor used to breed them.

==Sounds==
{{Sound table/Entity/Food}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showitemtags=y
|showforms=y
|generatetranslationkeys=y
|displayname=Cooked Cod
|spritetype=item
|nameid=cooked_cod
|itemtags=fishes
|form=item
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|shownumericids=y
|showforms=y
|showaliasids=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Cooked Cod
|spritetype=item
|nameid=cooked_cod
|aliasid=cooked_fish
|id=268
|form=item
|translationkey=item.cooked_fish.name
|foot=1}}

== Achievements ==

{{load achievements|Delicious Fish}}

== Advancements ==
{{load advancements|Husbandry;A Balanced Diet}}

== Video ==
<div style="text-align:center">{{yt|nPl0HUGPMcA}}</div>

== History ==

{{History|java alpha}}
{{History||v1.2.0|snap=<nowiki>?|slink=:Category:Information needed requiring unarchived version|[[File:Cooked Cod JE1 BE1.png|32px]] Added cooked fish, which restores {{hp|5}}.}}
{{History|java beta}}
{{History||1.5|Cooking fish now gives the '''Delicious Fish''' [[achievement]].}}
{{History||1.8|snap=Pre-release|Cooked fish is now stackable to 64.
|Cooked fish now fills {{hunger|5}} instead of {{hp|5}}.}}
{{History|java}}
{{History||1.3.1|snap=12w21a|Farmer [[villager]]s now [[trading|buy]] 9–12 cooked fish for 1 [[emerald]].}}
{{History||1.8|snap=14w02a|[[Trading]] has been changed: fisherman [[villager]]s now [[trading|sell]] 6 cooked fish for 1 [[emerald]] plus 6 [[raw cod|raw fish]].
|Farmer villagers no longer buy cooked fish.}}
{{History|||snap=14w04a|The name of cooked fish has been corrected from <code>cooked_fished</code> to <code>cooked_fish</code>.}}
{{History|||snap=14w25a|Cooked fish are now obtainable rare [[drops]] from [[guardian]]s and [[elder guardians]].}}
{{History||1.13|snap=17w47a|The different data values for the <code>cooked_fish</code> IDs have been split up into their own IDs.
|"Cooked Fish" have been renamed to "Cooked Cod".
|Prior to [[1.13/Flattening|''The Flattening'']], these [[item]]s' numeral ID were 349 and 350.}}
{{History|||snap=18w08b|[[Cod]], and other [[fish]], have been added as [[mob]]s, which [[drops|drop]] their cooked [[item]] form when killed with [[fire]].
|[[File:Cooked Cod JE2 BE2.png|32px]] The texture of cooked cod has been changed.}}
{{History|||snap=18w10a|Cooked cod now generates in [[buried treasure]] [[chest]]s.}}
{{History||1.14|snap=18w43a|[[File:Cooked Cod JE3.png|32px]] The texture of cooked cod has been changed.}}
{{History|||snap=18w47b|[[File:Cooked Cod JE4 BE3.png|32px]] The texture of cooked cod has been changed, once again to match {{el|be}}.}}

{{History|pocket alpha}}
{{History||v0.11.0|snap=build 1|[[File:Cooked Cod JE1 BE1.png|32px]] Added cooked fish.}}
{{History||v0.12.1|snap=build 1|Cooked fish now restores [[hunger]] instead of [[health]].}}
{{History||v0.16.0|snap=build 1|Cooked fish is now [[drops|dropped]] by [[guardian]]s and [[elder guardian]]s.}}
{{History|pocket}}
{{History||1.0.4|snap=alpha 1.0.4.0|Fisherman [[villager]]s now [[trading|sell]] 6 cooked fish for 1 [[emerald]] plus 6 [[raw cod|raw fish]].}}
{{History|bedrock}}
{{History||1.4.0|snap=beta 1.2.14.2|[[Cod]] and other [[fish]] have been added as [[mob]]s, which [[drops|drop]] their cooked [[item]] form when killed with [[fire]].
|[[File:Cooked Cod JE2 BE2.png|32px]] The texture of cooked fish has been changed.}}
{{History||1.5.0|snap=beta 1.5.0.4|[[File:Cooked Cod JE4 BE3.png|32px]] The texture of cooked fish has been changed.}}
{{History||1.7.0|snap=beta 1.7.0.2|"Cooked Fish" has been renamed to "Cooked Cod".}}
{{History||1.11.0|snap=beta 1.11.0.4|Fisherman [[villager]]s now have a 50% chance to [[trading|sell]] 6 cooked cod for 6 [[raw cod]] and 1 [[emerald]].}}
{{History||1.16.100|snap=beta 1.16.100.52|Cod now drop their cooked cod when killed with fire.}}

{{History|console}}
{{History||xbox=TU1|xbone=CU1|ps=1.0|wiiu=Patch 1|[[File:Cooked Cod JE1 BE1.png|32px]] Added cooked fish.}}
{{History||xbox=TU5|Cooked fish is now stackable to 64.
|Cooked fish now fills [[hunger]] instead of [[health]].}}
{{History||xbox=TU69|ps=1.76|wiiu=Patch 38|"Cooked Fish" has been renamed to "Cooked Cod".
|[[File:Cooked Cod JE2 BE2.png|32px]] The texture of cooked cod has been changed.}}

{{History|new 3ds}}
{{History||0.1.0|[[File:Cooked Cod JE1 BE1.png|32px]] Added cooked fish.}}
{{History|foot}}

== Issues ==

{{Issue list}}

{{Items}}

[[Category:Food]]
[[Category:Renewable resources]]

[[de:Gebratener Kabeljau]]
[[es:Bacalao cocinado]]
[[ko:익힌 대구]]
[[pt:Bacalhau assado]]
[[ru:Жареная треска]]
[[th:Cod (ไอเทม)]]
[[zh:熟鳕鱼]]</li><li>[[Chain|Chain]]<br/>{{about|the block|the enchantment in Minecraft Dungeons|MCD:Chains|the armor tier named chainmail|Armor|the armor material called chainmail|Armor materials}}
{{Block
|image=<gallery>
Chain Axis Y.png | Y-axis
Chain Axis X.png | X-axis
Chain Axis Z.png | Z-axis
</gallery>
| transparent = Yes
| light = No
| tool = Wooden pickaxe
| renewable = Yes
| stackable = Yes (64)
| flammable = No
| lavasusceptible = No
}}

'''Chains''' are metallic decoration [[block]]s.

== Obtaining ==
=== Breaking ===

Chains can be mined using any [[pickaxe]]. If mined without a pickaxe, it drops nothing.
{{breaking row|Chain|Pickaxe|Wood|horizontal=1}}

=== Natural generation ===
Chains generate in [[bastion remnant]]s and sometimes in [[ruined portal]]s that generate in the Nether. They always generate above [[magma cube]] spawners, also found in [[bastion]]s.

Chains can also generate in [[mineshafts]]. They generate on the sides of a wooden bridge (a mid-air corridor) when the distance between the bridge and the highest solid block below it is higher than the distance to the lowest solid block above it. Chains here generate vertically in a pillar between the bridge and the ceiling. The lowest block of the pillar, connecting the chain to the bridge, is always an [[oak fence]].

=== Chest loot ===
{{LootChestItem|chain}}

=== Crafting ===
{{Crafting
|B1=Iron Nugget
|B2=Iron Ingot
|B3=Iron Nugget
|Output=Chain
|type=Building block
}}

== Usage ==
Chains can be used to suspend [[bell]]s, [[hanging sign]]s, or both types of [[lantern]]s (normal lanterns and soul lanterns), as the chain texture connects to the chain of the lantern seamlessly as if it were part of it, and it connects the hanging sign chains together. Chains do not require a supporting block to be placed whether it is on the top, next to it or at the bottom. It can exist completely free-standing in mid air<ref>{{bug|MC-178791}}</ref> and it can be rotated. Chains connect horizontally or vertically, but not across different orientations (so a chain with N orientation does not connect to a chain with E orientation in the adjacent block).
Horizontal chains one block above a surface may be walked over. Horizontal chains two blocks above a surface prevent players from traveling past them. Vertical chains block travel if targeted directly, but may be skirted.

Precision is required, but chains can be walked on, allowing for inconspicuous, although somewhat costly, bridges.

Chains can be pushed by [[piston]]s without being broken.

=== Crafting ingredient ===
{{crafting usage}}

== Sounds ==
{{Sound table/Block/Chain}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Chain
|spritetype=block
|nameid=chain
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|firstcolumnname=Chain
|shownumericids=y
|showforms=y
|generatetranslationkeys=y
|displayname=Block
|spritename=chain
|spritetype=block
|nameid=chain
|id=541
|form=block
|itemform=item.chain}}
{{ID table
|displayname=Item
|spritename=chain
|spritetype=item
|nameid=chain
|id=619
|form=item
|translationkey=tile.chain.name
|foot=1}}

=== Block states ===
{{see also|Block states}}
{{/BS}}

== History ==
{{History|java}}
{{History||1.16|snap=20w16a|[[File:Chain (item) JE1 BE1.png|32px]] [[File:Chain Axis Y JE1 BE1.png|32px]] Added chains.
|Chains generate in the newly added [[bastion remnant]]s, and can be found in their [[chest]]s.
|Chains currently use the generic metal [[block]] [[sound]]s.}}
{{History|||snap=20w17a|Unique [[sound]]s have been added for chains.}}
{{History|||snap=20w18a|Chains can now be [[waterlogged]].}}
{{History||1.16.2|snap=20w30a|The chance of finding chains in bastion remnant chests is decreased from 31.5% to 24.4%.}}
{{History|||snap=Pre-release 1|[[File:Chain Axis X JE1 BE1.png|32px]] [[File:Chain Axis Z JE1 BE1.png|32px]] Chains can now be placed in all orientations.}}
{{History||1.17|snap=21w07a|Chains can now generate in [[mineshaft]]s.}}
{{History|||snap=21w13a|[[File:Chain (UD) JE2.png|32px]] [[File:Chain (NS) JE2.png|32px]] [[File:Chain (EW) JE2.png|32px]] The model of chains has been changed so that the backside texture is mirrored.}}
{{History||1.20<br>(Experimental)|link=1.19.3|snap=22w42a|Chains are now used to craft [[hanging sign]]s.}}

{{History|bedrock}}
{{History||1.16.0|snap=beta 1.16.0.57|[[File:Chain_(item)_JE1_BE1.png|32px]] [[File:Chain Axis Y JE1 BE1.png|32px]] Added chains.}}
{{History|||snap=beta 1.16.0.63|Unique [[sound]]s have been added for chains.}}
{{History||1.16.100|snap=beta 1.16.100.54|[[File:Chain Axis X JE1 BE1.png|32px]] [[File:Chain Axis Z JE1 BE1.png|32px]] Chains can now be placed in all orientations.}}
{{History||1.20.0<br>(Experimental)|link=Bedrock Edition 1.19.50|snap=beta 1.19.50.21|Chains are now used to craft [[hanging sign]]s.}}
{{History|foot}}

== Issues ==
{{issue list}}
== Trivia ==
* A vertical chain, being a solid, but not a full [[block]], allows for many sizes of [[mob]]s and [[player]]s to pass alongside each piece horizontally.
* Despite its name, it cannot be [[crafted]] into [[chainmail armor]].<ref>{{bug|MC-178979}} - Invalid</ref>
* Chains do not stick together when moved by pistons, regardless of orientation.

== Gallery ==
<gallery>
Chained Stone Bricks.jpg|Chains and stone bricks.
Barbell.jpg|Chains and chiseled blackstone.
Barbell Evoker.jpg|An evoker lifting weights.
Chain with Lantern.png|A [[lantern]] hanging from a chain.
Chain with Spawner.png|A [[spawner]] hanging with a chain found in the bastion remnants.
</gallery>

== References ==
{{reflist}}

{{blocks|Building}}
{{Items}}

[[Category:Manufactured blocks]]
[[Category:Generated structure blocks]]
[[Category:Nether blocks]]

[[de:Kette]]
[[es:Cadena]]
[[fr:Chaîne]]
[[ja:鎖]]
[[ko:사슬]]
[[pl:Łańcuch]]
[[pt:Corrente]]
[[ru:Цепь]]
[[zh:锁链]]</li></ul></nowiki>
beta 1.16.200.52Goat BE1 Goat BE1 Added goats and kids, which are available only via Experimental Gameplay.
Goats make the sound of a player being hit.
Goats currently uses the vex's charging sound as a placeholder when preparing to ram charge.[1]
releaseGoats have been made inaccessible in the full release.
Upcoming Bedrock Edition
1.16.210
{{Extension DPL}}<ul><li>[[:Category:Armor|Category:Armor]]<br/>[[Category:Items]]</li><li>[[Boat with Chest|Boat with Chest]]<br/>{{ItemEntity
|image=Oak Boat with Chest.png
|extratext = View [[#Gallery|all renders]]
|stackable=No
|renewable=Yes
|flammable=Yes
|size='''{{IN|Java}}:'''<br>
Height: 0.5625 Blocks<br>Width: 1.375 Blocks<br>
'''{{IN|Bedrock}}:'''<br>
Height: 0.455 Blocks<br>Width: 1.4 Blocks

|networkid='''[[JE]]''': 1
}}
{{for|other kinds of boats|Boat (disambiguation)}}

A '''boat with chest''' is a single [[chest]] occupying the passenger seat of a [[boat]], and functions as such. As it can still be driven it can be used to transport [[item]]s over bodies of water.

== Obtaining ==
A boat with chest can be directly retrieved by attacking it, as it drops itself in item form, along with its contents.

[[Tool]]s and [[weapon]]s with damage above 4 can instantly destroy a boat with chest in one hit.{{only|Java}}

=== Crafting ===
{{Crafting
|head= 1
|Chest
|Matching Boat
|Output= Matching Boat with Chest
|type= Transportation
|foot= 1
}}

== Usage ==
A boat with chest can be used for the transportation of players, mobs and items, or as fuel when [[smelting]].

=== Fuel ===
A boat with chest can be used as fuel in a [[furnace]], it lasts 60 seconds, smelting up to 6 items.

=== Transportation ===
{{main|Boat#Transportation}}

Boats with chests can carry only one entity while regular boats can carry up to two.

== Behavior ==
[[File:All boats with chests.png|alt=This photo shows all the types of boats with chests.|thumb|240px|All types of boats with chests.]]
{{main|Boat#Behavior}}
Boats with chests share most behaviors with boats.

=== Item storage ===
[[File:Boat with Chest GUI.png|thumb|176px|The GUI of a boat with chest.]]
The inventory of the boat with chest has the same amount of slots as a single chest. Its inventory can be accessed by {{Control|Sneak|text=sneaking}} and {{Control|interact|text=interacting}} with the boat with chest, {{control|interact|text=interacting}} with the part of the boat with chest that actually contains the chest while another player or entity is inside the boat, or by opening the player's {{Control|inventory}} while inside the boat. This means that the player cannot access armor slots without exiting the boat.

When a boat with chest moves above, underneath, or beside a [[hopper]], its inventory is filled or drained accordingly. Due to the size of its hitbox, a boat with chest can be placed above up to 9 hoppers, allowing it to evenly split its items nine ways.

=== Naming ===
{{IN|java}}, unlike most other storage devices, a boat with chest renamed in an [[anvil]] does not display the custom name in its GUI.<ref>{{bug|MC-249408||Boats with Chests lose their name when placed}}</ref>

=== Piglin ===
As with other chests, opening or breaking a boat with chest causes nearby piglin(s) to attack the player.

== Sounds ==
{{Edition|Java}}:
Boats with chests use the Friendly Creatures sound category for entity-dependent sound events.
{{Sound table
|sound=Boat paddle land1.ogg
|sound2=Boat paddle land2.ogg
|sound3=Boat paddle land3.ogg
|sound4=Boat paddle land4.ogg
|sound5=Boat paddle land5.ogg
|sound6=Boat paddle land6.ogg
|subtitle=Rowing
|source=neutral
|description=While a boat with chest is rowed on land
|id=entity.boat.paddle_land
|translationkey=subtitles.entity.boat.paddle_land
|volume=1.0
|pitch=0.8-1.2
|distance=16}}
{{Sound table
|sound=Boat paddle water1.ogg
|sound2=Boat paddle water2.ogg
|sound3=Boat paddle water3.ogg
|sound4=Boat paddle water4.ogg
|sound5=Boat paddle water5.ogg
|sound6=Boat paddle water6.ogg
|sound7=Boat paddle water7.ogg
|sound8=Boat paddle water8.ogg
|subtitle=Rowing
|source=neutral
|description=While a boat with chest is rowed in water
|id=entity.boat.paddle_water
|translationkey=subtitles.entity.boat.paddle_water
|volume=0.8
|pitch=0.8-1.2
|distance=16
|foot=1}}

{{Edition|Bedrock}}:
{{Sound table
|type=bedrock
|sound=Swim1.ogg
|sound2=Swim2.ogg
|sound3=Swim3.ogg
|sound4=Swim4.ogg
|source=player
|description=While a boat with chest is rowed in water
|id=random.swim
|pitch=0.6-1.4
|foot=1}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|showitemtags=y
|showforms=y
|generatetranslationkeys=y
|displayname=Oak Boat with Chest
|spritetype=item
|spritename=oak-boat with chest
|nameid=oak_chest_boat
|itemtags=chest_boats
|form=item}}
{{ID table
|displayname=Spruce Boat with Chest
|spritetype=item
|spritename=spruce-boat with chest
|nameid=spruce_chest_boat
|itemtags=chest_boats
|form=item}}
{{ID table
|displayname=Birch Boat with Chest
|spritetype=item
|spritename=birch-boat with chest
|nameid=birch_chest_boat
|itemtags=chest_boats
|form=item}}
{{ID table
|displayname=Jungle Boat with Chest
|spritetype=item
|spritename=jungle-boat with chest
|nameid=jungle_chest_boat
|itemtags=chest_boats
|form=item}}
{{ID table
|displayname=Acacia Boat with Chest
|spritetype=item
|spritename=acacia-boat with chest
|nameid=acacia_chest_boat
|itemtags=chest_boats
|form=item}}
{{ID table
|displayname=Dark Oak Boat with Chest
|spritetype=item
|spritename=dark-oak-boat with chest
|nameid=dark_oak_chest_boat
|itemtags=chest_boats
|form=item}}
{{ID table
|displayname=Mangrove Boat with Chest
|spritetype=item
|spritename=mangrove-boat with chest
|nameid=mangrove_chest_boat
|itemtags=chest_boats
|form=item}}
{{ID table
|displayname=Cherry Boat with Chest
|spritetype=item
|spritename=cherry-boat with chest
|nameid=cherry_chest_boat
|itemtags=chest_boats
|form=item}}
{{ID table
|displayname=Bamboo Raft with Chest
|spritetype=item
|spritename=bamboo-raft with chest
|nameid=bamboo_chest_raft
|itemtags=chest_boats
|form=item
|foot=1}}
{{ID table
|edition=java
|firstcolumnname=Boat with Chest
|generatetranslationkeys=y
|displayname=Entity
|spritetype=entity
|spritename=boat-with-chest
|nameid=chest_boat
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|showitemtags=y
|showaliasids=y
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Oak Boat with Chest
|spritetype=item
|nameid=oak_chest_boat
|aliasid=chest_boat / 0
|id=646
|form=item
|itemtags=minecraft:chest_boat
|translationkey=item.chest_boat.oak.name}}
{{ID table
|displayname=Spruce Boat with Chest
|spritetype=item
|nameid=spruce_chest_boat
|aliasid=chest_boat / 1
|id=649
|form=item
|itemtags=minecraft:chest_boat
|translationkey=item.chest_boat.spruce.name}}
{{ID table
|displayname=Birch Boat with Chest
|spritetype=item
|nameid=birch_chest_boat
|aliasid=chest_boat / 2
|id=647
|form=item
|itemtags=minecraft:chest_boat
|translationkey=item.chest_boat.birch.name}}
{{ID table
|displayname=Jungle Boat with Chest
|spritetype=item
|nameid=jungle_chest_boat
|aliasid=chest_boat / 3
|id=648
|form=item
|itemtags=minecraft:chest_boat
|translationkey=item.chest_boat.jungle.name}}
{{ID table
|displayname=Acacia Boat with Chest
|spritetype=item
|nameid=acacia_chest_boat
|aliasid=chest_boat / 4
|id=650
|form=item
|itemtags=minecraft:chest_boat
|translationkey=item.chest_boat.acacia.name}}
{{ID table
|displayname=Dark Oak Boat with Chest
|spritetype=item
|nameid=dark_oak_chest_boat
|aliasid=chest_boat / 5
|id=651
|form=item
|itemtags=minecraft:chest_boat
|translationkey=item.chest_boat.big_oak.name}}
{{ID table
|displayname=Mangrove Boat with Chest
|spritetype=item
|nameid=mangrove_chest_boat
|aliasid=chest_boat / 6
|id=652
|form=item
|itemtags=minecraft:chest_boat
|translationkey=item.chest_boat.mangrove.name}}
{{ID table
|displayname=Cherry Boat with Chest
|spritetype=item
|nameid=cherry_chest_boat
|aliasid=chest_boat / 8
|id=658
|form=item
|itemtags=minecraft:chest_boat
|translationkey=item.chest_boat.cherry.name}}
{{ID table
|displayname=Bamboo Raft with Chest
|spritetype=item
|nameid=bamboo_chest_raft
|aliasid=chest_boat / 7
|id=662
|form=item
|itemtags=minecraft:chest_boat
|translationkey=item.chest_boat.bamboo.name
|foot=1}}
{{ID table
|edition=bedrock
|firstcolumnname=Form
|shownumericids=y
|generatetranslationkeys=y
|displayname=Entity
|spritetype=entity
|spritename=boat-with-chest
|nameid=chest_boat
|id=218
|foot=1}}

=== Entity data ===
Boat with chests have entity data associated with them that contain various properties of the entity.

{{el|java}}:
{{main|Entity format}}
{{/ED}}

{{el|bedrock}}:
: See [[Bedrock Edition level format/Entity format]].

== History ==
{{History||September 23, 2019|link={{ytl|Anv-lZc0pIM}}|The [[swamp]] was announced as a contender for the Biome Vote at [[MINECON Live 2019]]. Frogs, boats with chests, and mangrove trees were announced.}}
{{History||September 28, 2019|link={{ytl|UHoz0Q-LwUU}}|The swamp comes in second place in the Biome Vote, setting the release date of new swamp content further than new mountain content.}}
{{History||October 16, 2021|link={{ytl|w6zLprHHZOk|t=7085}}|[[File:Jungle Boat with Chest (pre-release).png|32px]] [[File:Dark Oak Boat with Chest (pre-release).png|32px]] Boats with chests were announced at [[Minecraft Live 2021]]. Only jungle and dark oak variants were shown.}}
{{History|java}}
{{History||1.19|snap=22w12a|[[File:Oak Boat with Chest JE1.png|32px]] [[File:Spruce Boat with Chest JE1.png|32px]] [[File:Birch Boat with Chest JE1.png|32px]] [[File:Jungle Boat with Chest JE1.png|32px]] [[File:Acacia Boat with Chest JE1.png|32px]] [[File:Dark Oak Boat with Chest JE1.png|32px]] [[File:Mangrove Boat with Chest JE1.png|32px]]<br>[[File:Oak Boat with Chest (item) JE1 BE1.png|32px]] [[File:Spruce Boat with Chest (item) JE1.png|32px]] [[File:Birch Boat with Chest (item) JE1 BE1.png|32px]] [[File:Jungle Boat with Chest (item) JE1 BE1.png|32px]] [[File:Acacia Boat with Chest (item) JE1 BE1.png|32px]] [[File:Dark Oak Boat with Chest (item) JE1 BE1.png|32px]] [[File:Mangrove Boat with Chest (item) JE1 BE1.png|32px]] Added boats with chests.
|Knob on chest is placed incorrectly 1 pixel up.}}
{{History|||snap=22w13a|[[File:Oak Boat with Chest JE2 BE1.png|32px]] [[File:Spruce Boat with Chest JE2 BE1.png|32px]] [[File:Birch Boat with Chest JE2 BE1.png|32px]] [[File:Jungle Boat with Chest JE2 BE1.png|32px]] [[File:Acacia Boat with Chest JE2 BE1.png|32px]] [[File:Dark Oak Boat with Chest JE2 BE1.png|32px]] [[File:Mangrove Boat with Chest JE2 BE1.png|32px]] Changed knob on chest position 1 pixel down to match [[Bedrock Edition]].
|Boats with chests can now be placed by [[dispenser]]s.}}
{{History|||snap=22w14a|Due to the addition of the [[mangrove tree]] and [[mangrove swamp]], make mangrove boat with chest obtainable and renewable.}}
{{History|||snap=22w15a|[[File:Oak Boat with Chest (item) JE2.png|32px]] [[File:Spruce Boat with Chest (item) JE2.png|32px]] [[File:Birch Boat with Chest (item) JE2.png|32px]] [[File:Jungle Boat with Chest (item) JE2.png|32px]] [[File:Acacia Boat with Chest (item) JE2.png|32px]] [[File:Dark Oak Boat with Chest (item) JE2.png|32px]] [[File:Mangrove Boat with Chest (item) JE2.png|32px]] Changed all boat with chest item textures.
|Now, the inventory can be accessed by {{control|using}} it directly when there is already a passenger inside of it.}}
{{History||October 15, 2022|link={{ytl|yZRXmHiEh7U&t}}|[[File:Bamboo Raft with Chest JE1 BE1.png|32px]] Bamboo rafts with chests were announced at [[Minecraft Live 2022]].}}
{{History||1.20<br>(Experimental)|link=1.19.3|snap=22w42a|[[File:Bamboo Raft with Chest JE1 BE1.png|32px]] [[File:Bamboo Raft with Chest (item) JE1.png|32px]] Added bamboo rafts with chests behind the [[Java Edition 1.20|Update 1.20 experimental datapack]].}}
{{History|||snap=22w45a|[[File:Bamboo Raft with Chest (item) JE2 BE2.png|32px]] The item texture of the bamboo raft with chest has been changed.}}
{{History||1.20<br>(Experimental)|link=1.19.4|snap=23w07a|[[File:Cherry Boat with Chest JE1.png|32px]] [[File:Cherry Boat with Chest (item) JE1.png|32px]] Added cherry boats with chests behind the [[Java Edition 1.20|Update 1.20 experimental datapack]].}}
{{History|||snap=1.19.4 Pre-release 2|[[File:Cherry Boat with Chest (item) JE2.png|32px]] The item texture of cherry boats with chests has now been changed.}}
{{History||1.20|snap=23w12a|Bamboo rafts with chests and cherry boats with chests are now available without using the "Update 1.20" experimental datapack.}}

{{History|bedrock}}
{{History||Wild Update<br>(Experimental)|link=Bedrock Edition 1.19.0|snap=beta 1.18.30.28|[[File:Oak Boat with Chest JE2 BE1.png|32px]] [[File:Spruce Boat with Chest JE2 BE1.png|32px]] [[File:Birch Boat with Chest JE2 BE1.png|32px]] [[File:Jungle Boat with Chest JE2 BE1.png|32px]] [[File:Acacia Boat with Chest JE2 BE1.png|32px]] [[File:Dark Oak Boat with Chest JE2 BE1.png|32px]]<br>[[File:Oak Boat with Chest (item) JE1 BE1.png|32px]] [[File:Spruce Boat with Chest (item) BE1.png|32px]] [[File:Birch Boat with Chest (item) JE1 BE1.png|32px]] [[File:Jungle Boat with Chest (item) JE1 BE1.png|32px]] [[File:Acacia Boat with Chest (item) JE1 BE1.png|32px]] [[File:Dark Oak Boat with Chest (item) JE1 BE1.png|32px]] Added boats with chests, missing mangrove type.
|Added unused translation keys for mangrove boat with chest.}}
{{History||1.19.0|snap=beta 1.19.0.20|Boats with chests are now available without enabling experimental gameplay.|[[File:Mangrove Boat with Chest JE2 BE1.png|32px]] [[File:Mangrove Boat with Chest (item) JE1 BE1.png|32px]] Added mangrove boats with chests.}}
{{History||1.19.0|snap=beta 1.19.0.26|[[File:Oak Boat with Chest (item) JE2.png|32px]] [[File:Spruce Boat with Chest (item) JE2.png|32px]] [[File:Birch Boat with Chest (item) JE2.png|32px]] [[File:Jungle Boat with Chest (item) JE2.png|32px]] [[File:Acacia Boat with Chest (item) JE2.png|32px]] [[File:Dark Oak Boat with Chest (item) JE2.png|32px]] [[File:Mangrove Boat with Chest (item) JE2.png|32px]] Changed all boat with chest item textures.}}
{{History||Next Major Update<br>(Experimental)|link=Bedrock Edition 1.19.50|snap=beta 1.19.50.21|[[File:Bamboo Raft with Chest JE1 BE1.png|32px]] [[File:Bamboo Raft with Chest (item) BE1.png|32px]] Added bamboo rafts with chests behind the "[[Bedrock Edition 1.20|Next Major Update]]" [[experimental]] toggle.}}
{{History|||snap=beta 1.19.60.20|[[File:Bamboo Raft with Chest (item) JE2 BE2.png|32px]] The item texture of the bamboo raft with chest has been changed to match ''[[Java Edition]]''.}}
{{History||Next Major Update<br>(Experimental)|link=Bedrock Edition 1.19.80|snap=beta 1.19.80.20|[[File:Cherry Boat with Chest JE1.png|32px]] [[File:Cherry Boat with Chest (item) JE2.png|32px]] Added cherry boats with chests behind the "[[Bedrock Edition 1.20|Next Major Update]]" [[experimental]] toggle.}}
{{History||1.20.0|snap=beta 1.20.0.21|Bamboo rafts with chests and cherry boats with chests are now available without using the "Next Major Update" experimental toggle.}}
{{History|foot}}

== Issues ==
{{issue list}}

== Trivia ==
* A [[chest]] is short enough that a boat with chest falls onto it rather than crashes into it.
* The chest texture is 12×12 pixels, rather than the 14×14 pixel texture the block uses. This is not the case with the [[minecart with chest]].
* Despite the minecart with chest using the Christmas texture, the boat with chest still uses the default chest texture during Christmas time.<ref>{{bug|MC-249378}}</ref>

== Gallery ==
=== Renders ===
<gallery>
Oak Boat with Chest.png|Oak Boat with Chest
Spruce Boat with Chest.png|Spruce Boat with Chest
Birch Boat with Chest.png|Birch Boat with Chest
Jungle Boat with Chest.png|Jungle Boat with Chest
Acacia Boat with Chest.png|Acacia Boat with Chest
Dark Oak Boat with Chest.png|Dark Oak Boat with Chest
Mangrove Boat with Chest.png|Mangrove Boat with Chest
Cherry Boat with Chest.png|Cherry Boat with Chest
Bamboo Raft with Chest.png|Bamboo Raft with Chest
Oak Boat with Chest (item) JE2.png|Oak Boat with Chest (item)
Spruce Boat with Chest (item) JE2.png|Spruce Boat with Chest (item)
Birch Boat with Chest (item) JE2.png|Birch Boat with Chest (item)
Jungle Boat with Chest (item) JE2.png|Jungle Boat with Chest (item)
Acacia Boat with Chest (item) JE2.png|Acacia Boat with Chest (item)
Dark Oak Boat with Chest (item) JE2.png|Dark Oak Boat with Chest (item)
Mangrove Boat with Chest (item) JE2.png|Mangrove Boat with Chest (item)
Cherry Boat with Chest (item) JE2.png|Cherry Boat with Chest (item)
Bamboo Raft with Chest (item) JE2 BE2.png|Bamboo Raft with Chest (item)
</gallery>

=== Concept Art ===
<gallery>
Bamboo Raft and Raft with Chest Concept Art.png|Ditto.
</gallery>

== References ==
{{reflist}}

{{Items}}
{{Entities}}


[[de:Boot mit Truhe]]
[[es:Barca con cofre]]
[[ja:チェスト付きのボート]]
[[ru:Лодка с сундуком]]
[[uk:Човен зі скринею]]
[[zh:运输船]]</li></ul>
beta 1.16.210.51Goats now only drop 2 goat horns each.
Goats now drop 1-2 mutton.
Goat (one horn) BE1 Goat (no horn) BE1 Goats now show missing goat horns in the model.
Baby goats now have half knockback when using a ram attack.
Goats no longer attack armor stands.[2]
Goats now attack shulkers.
Goats now only produce one baby goat at a time when breeding.
beta 1.16.210.53Goats now avoid walking onto powder snow while path-finding.
  1. ↑ BE-104156
  2. ↑ MCPE-104159 — "Goat attacks armor stands" — resolved as "Fixed".

Notice how the former shows the features as a part of 1.17.0, while the latter shows it as part of 1.16.200 and 1.16.210. I prefer the former option as the Caves & Cliffs features added in the betas of 1.16.X don't end up in the full release, but instead will be a part of 1.17.0.

– Unavailablehoax (talk) 23:36, 26 January 2021 (UTC)

I  Support to use the first, because the features won't be part of 1.16.x releases, and it's more specific. Thejoaqui777 (talk) 23:54, 26 January 2021 (UTC)
They are part of the 1.16.210 betas, and it should be declared that way. Saying the beta is for 1.17 is false information. Dhranios (talk) (Join the wiki videos project!) 00:16, 27 January 2021 (UTC)
Should say 1.16.210, with "added under experimental gameplay", then 1.17 with "fully implemented".  Nixinova   T   C   00:26, 1 February 2021 (UTC)

Proposal for a Crossovers page, replacing the current Smash page

I talk about this more on Talk:Super Smash Bros. Ultimate, but since that page doesn't get much traffic for obvious reasons, I thought I'd bring it up here.

My argument boils down to it making more sense than adding a new page for every game that references Minecraft, and being more consistent to what Wiki readers might expect and enjoy. Thoughts? -- DigiDuncan (talk) 00:14, 1 February 2021 (UTC)

Request for a new page - but I need your help

I want to create a new page that lists from the longest name for an item to the shortest name, but I don't know how should I create it. I hope you can help me. - Melvintnh327 (talk) 05:04, 7 February 2021 (UTC)

It is unnotable to be given an article. TheGreatSpring (talk) 05:28, 7 February 2021 (UTC)
It is completely trivial information, so it doesn't belong anywhere on this wiki, except perhaps a subpage of your userpage. Fadyblok240 (talk) 05:40, 7 February 2021 (UTC); updated 06:12, 7 February 2021 (UTC)
Okay then...I guess I would not create it - Melvintnh327 (talk) 02:23, 11 February 2021 (UTC)

What happened?

The wiki stopped working for some time. Why? Gameking1happy (talk) 16:40, 11 February 2021 (UTC)

Another glitch with UCP, this is the worst one so far. James Haydon (talk) 16:41, 11 February 2021 (UTC)
Fandom rolled out an update that broke the platform. They quickly rolled it back though.
While they were rolling it back though, Minecraft Wiki played the roles of: 1) London Bird Club Wiki; 2) Wookieepedia; 3) the Pixel Gun Wiki and the Game of Thrones Wiki simultaneously. Oh, and half the platform was the Raft Wiki for a few moments. --AttemptToCallNil (talk) 16:58, 11 February 2021 (UTC)
I don't think there even is a Game of Thrones wiki on Gamepedia because its not a game. So it also is affecting FANDOM wikis as well. James Haydon (talk) 17:01, 11 February 2021 (UTC)
Yes, it affected the entire platform, including all Fandom wikis. --AttemptToCallNil (talk) 17:04, 11 February 2021 (UTC)

Minecraft Story Mode NS

Hi

We already discussed about Minecraft Earth and Minecraft Dungeons namespaces, but i think we still miss "Minecraft: Story Mode" namespace. This namespace was already discussed in "Moving Minecraft Story Mode Wiki to this wiki", but as Minecraft Story Mode Wiki discussion was really not great, and it failed, we were exploring possibility of exporting articles from "Fandom's Minecraft Wiki". But unfortunately, these will also need rewrite. So, articles are created manually, as stubs, which will need to expand.

So, we have to create these articles by ourselves. Unfortunately, we won't be able to beat Minecraft Story Mode Wiki, until we will have own namespace, and own production of articles.

On Google, we ended really far from top, on 5th place. On Bing, we were more successful, reaching 3rd, but on both searches, MC Story Mode Wiki was on top.

So, should we create Minecraft Story Mode NS?--TreeIsLife (talk) 19:05, 13 February 2021 (UTC)

 Support We have pretty bad situation, on Google, even Fandom's MCW has higher ranking, so we are in bad situation --TreeIsLife (talk) 19:05, 13 February 2021 (UTC)
 Temporal oppose, let me explain. It has been some months since the discussion, but I think that we should contact first their admins. I don't want them to think that we try to compete with them, instead to colaborate. Your words look very competitive, which isn't how this wiki wants to get information. We talk with people, and try to get a deal with them to make both parts happy. So, I think that we should wait 2 months more at least to begin talking with them again, because they refused to merge due to bad communication. Thejoaqui777 (talk) 19:21, 13 February 2021 (UTC)
 Comment TreeIsLife, I agree with Thejoaqui777, why are you making this a competition? MC wiki isnt a promotion wiki. Minecraft Story Mode is a WIP and the Minecraft Story Mode in FANDOM is fine, what makes you think that MC wiki is a promotional wiki? I also  Oppose per my comment on the previous discussion. I'm fine with the namespace but not trying to outmanuver fandom, gamepedia is owned by fandom anywaysHumiebee (talk) 19:25, 13 February 2021 (UTC)
This, this, this, this, this, this and this. It's not a competition. This exact behavior is what made the initial merge proposal fail badly. Dhranios (talk) (Join the wiki videos project!) 19:33, 13 February 2021 (UTC)
 Comment to all. This is not about competition. We tried... but... it did not go well. Hummie may not know about that, but there is great server, called Minecraft Wiki Crossover, where we discussed future of MC Wikis (all of them). We had a big dream. 3 big wikis for everything Minecraft - Minecraft Wiki, Minecraft Community Wiki and Minecraft Mods Wiki. And, we wanted to start with merging of all wikis from "Minecraft Wiki Network" into this wiki. Anddddd... I created discussion post, and we had protest on that wiki. I was critized about how i wrote it, and that i wrote it into discussions. Then, i decided i will left server, and do discussion by myself. So great, i had another conflict on another wiki (double problem). Unfortunately, discussion just failed and that's it. And now everybody hates me 😔. That was joke, obviously, I said it was my fault, and we discussed we won't say nothing to community, until we will lock the wiki (meaning only discussing with admins). And now, let's say why i want to do this. Well, they are inactive and only 1 person said something, but his timestamp between answers were 1 week.--TreeIsLife (talk) 19:41, 13 February 2021 (UTC)

Minicraft?

There are 5 Minecraft games: Minecraft, Minecraft Story Mode, Minecraft Earth and Minecraft Dungeons and, Minicraft. They all have page(s) other than Minicraft witch only has 1 reference on the whole wiki. I think Minicraft should have a page, if not may pages for the things in the game (mobs, items, etc). --Gtbot2007 (talk) 22:22, 13 February 2021 (UTC)

 Weak oppose this wiki is about Minecraft. TheGreatSpring (talk) 23:04, 13 February 2021 (UTC)
 Comment Well, 0x10c has its own wiki page, and yet it isn't a minecraft related game, it was developed by mojang, but wasn't really minecraft-like. James Haydon (talk) 23:23, 13 February 2021 (UTC)
 Comment But it was made by Notch, and has a lot of things from Minecraft (such as creepers), even the name is based on Minecraft --Gtbot2007 (talk) 23:53, 13 February 2021 (UTC)
Minicraft already has a page, but it is a redirect. Fadyblok240 (talk) 01:26, 14 February 2021 (UTC)
I guess because it wasn't developed by mojang unlike 0x10c and it wasn't nearly publicized as much. Makes sense why it doesn't have its own page. James Haydon (talk) 01:30, 14 February 2021 (UTC)
Redirects are pages too. Fadyblok240 (talk) 02:58, 14 February 2021 (UTC)
@Fadyblok240: By page I meant articles, no need to correct me about that. James Haydon (talk) 18:41, 14 February 2021 (UTC)
But its a minecraft game unlike 0x10c
 Comment The reason I felt the need to create the 0x10c page is because, unlike other games made by Notch or Mojang, you can't actually play it because it never came out, and so it doesn't have a wiki of its own (not anymore anyway). Now, on the other hand, Minicraft is a game you can play and it does have its own wiki, but, keep in mind, it is technically an official Minecraft spinoff game, and all the other official Minecraft spinoffs get to be on this wiki, so why not that one too? Plus the Minicraft wiki is really messy and incomplete, so I definitely wouldn't be opposed to something better being added to this wiki. AlienAgent124 (talk) 03:08, 14 February 2021 (UTC)
This is what I mean --172.58.228.82 09:27, 14 February 2021 (UTC)

Pocket/Bedrock Edition version pages

As the title, the Chinese Wiki is also disussing the same problem. See here.

Here, the problem is slightly different. It's mainly about {{version nav}}.

The documentation doesn't mention the usage of parameter {{{internal}}}. The number filled in this parameter shouldn't called "Internal version no.", and it should be "Full version no.". The correct "Internal version no." is a long string of numbers in file AndroidManifest.xml or in something else. "Full version no." is also in the file. For example, the Internal version no. of Pocket Edition 1.1.3 is 871010352 and the Full version no. is 1.1.3.52. Some of the pages on the Wiki need to split according to this, because we found that some apk files of very old version that shows the same Full version no. but they have different Internal version numbers.

About the articles, Style guide says that "naming specification is currently under discussion", but it was shelved obviously. Some version pages is different from the naming specification it stated. Also, MCW:SG/V needs to update.

In addition, The Chinese wiki is discussing renaming Bedrock/Pocket Edition version articles, and we are having an argument about if development versions should have "beta" or "alpha" on their names. Some people think that "the version number is for distinction", and they suggest to delete all the parts in the title that are not useful for distinction, include "alpha/beta" and "v" (the abbreviation of word "version"). Articles like "Bedrock Edition 1.16.210.59" or "Pocket Edition 0.10.0.b9" is enough to explain it's a development version, does not need to be like "Bedrock Edition beta 1.16.210.59" or "Pocket Edition v0.10.0 alpha build 9". The articles don't need to be exactly the same as shown in game, just like we don't name the page Java Edition 21w06a "Java Edition Minecraft 21w06a/snapshot".

If we changed the articles, the parameter {{{title}}} and {{{protocol_manual}}} of {{version nav}} also need to be changed. Do you think it's necessary?--SkyE | Talk · Contributions · Logs 08:00, 14 February 2021 (UTC)

Necessary, no, but it is a change I'd support. The only thing is that bedrock's beta builds aren't as distinguishable from the full build, compared to java's snapshots; betas only have 1 additional ".X", unlike snapshots which use a vastly different naming altogether. Dhranios (talk) (Join the wiki videos project!) 08:36, 14 February 2021 (UTC)
Oppose new naming scheme (the example given isn't actually relevant, the "/snapshot" isn't part of the version), and "beta" is useful for disambiguating. "The articles don't need to be exactly the same as shown in game"; they are though. Support parameter rename.  Nixinova   T   C   18:55, 14 February 2021 (UTC)
Although the existence of "alpha/beta" , "v" , parentheses and spaces have certain significance, it's not so significant as to benefit from changing the title. Now the whole title is long and scattered. According to what you said, "it is useful for disambiguating". But most of the time, the correct page cannot be found. In daily communication, few people would say "beta 1.16.210.59", most people would say "1.16.210.59" directly. Personally, I’m used to find pages directly with URLs instead of search functions. If the users who don’t know much about Wiki type an extra space or a wrong letter, and then find that the page does not exist, they won't know what to do (for example, I want to find "Bedrock Edition beta 1.16.210.59" but input "Bedrock Edition v1.16.210.59" or "Bedrock Edition 1.16.210.59"). If you ask "Why not use the search function?", if the title is changed to "Bedrock Edition 1.16.210.59", wouldn't the search function still be useful? Without various prefixes and suffixes, wouldn't the search efficiency be higher?--SkyE |  Talk · Contributions · Logs 13:24, 16 February 2021 (UTC)
 One more problem. Word "alpha" was not shown since 0.14, can we recognize that versions from 0.14 to 0.16 belong the Alpha development stage? --Lxazl5770zh.admin（论 ▪ 功） 14:47, 17 February 2021 (UTC)

Some current issues

Even if there is no need to change the naming specification, some Pocket Edition/Bedrock Edition pages still have problems.

  • Bedrock Edition 1.2.13.60 and Bedrock Edition 1.2.16 are two different versions. They just updated the same things and are in the same changelog on the Minecraft feedback website. The correct process is: First, Mojang changed the version number in the source code to 1.2.13.60 and released a version. This version didn't compile for iOS. Then Mojang changed the version number to 1.2.16.3, and bumped another version. They just used the same protocol version so they were still multiplayer compatible with each other. In order to prove that they are two versions, let me give an example: if I made an add-on, max_engine_version and min_engine_version in the manifest.json are both 1.2.13.60, then the version on iOS (1.2.16) cannot load this add-on.
  • The arcticles of Pocket Edition Alpha Realms build 1, build 2 and build 4 are different from other Pocket Edition Alpha versions. What's the naming specification exactly?
  • Mojang's naming specifications are very messy. Sometimes the version numbers show in different places are different.
    • For example, Bedrock Edition 1.2.6.1 should be "Bedrock Edition 1.2.6.60". In Google Play changelog and Mojira's this page], Mojang said it's 1.2.6.1, but in game it displays 1.2.6. In source code and MCPE-17100 on Mojira it's 1.2.6.60. The full version no. of Bedrock Edition 1.2.6 is 1.2.6.55. We know that if you want to update an app, the version number must be higher than the original installed version. Otherwise, the update will fail. So the correct article is "Bedrock Edition 1.2.6.60". There was an argument about this on the talk page.
    • @Nixinova: Your statement is incorrect. This also shows that the version number displayed in the game is unreliable, and the articles must be named according to the source code.
  • We found some versions that you thought did not exist (e.g. 1.14.1.4). If you want, we can provide the original apk files. We made a table to show this:
Wiki page Version no. displayed in game Internal version no. Recommended version no. (ver1) Recommended version no. (ver2)
0.1.0 0.1 1 0.1 0.1
0.1.0 0.1 2 0.1_Rev2 0.1_Rev2
0.1.0 0.1 4 0.1_Demo 0.1_Demo
0.1.1 0.1.1 1013 0.1.1_j 0.1.1_j
0.1.1 0.1.1 1015 0.1.1 0.1.1
0.1.2 0.1.2 1023 0.1.2_j 0.1.2_j
0.1.2 0.1.2 1025 0.1.2 0.1.2
0.1.3 0.1.3 1033 0.1.3_j 0.1.3_j
0.1.3 0.1.3 1035 0.1.3 0.1.3
None 0.1.3 1036 0.1.3_Rev2 0.1.3_Rev2
0.2.0 0.2.0 2003 0.2.0_j 0.2.0_j
0.2.0 0.2.0 2005 0.2.0 0.2.0
0.2.0 0.2.0 2006 0.2.0_Rev2 0.2.0_Rev2
None 0.2.1 2013 0.2.1_j 0.2.1_j
0.2.1 0.2.1 2015 0.2.1 0.2.1
0.2.1 (2) 0.2.1 2016 0.2.1_Rev2 0.2.1_Rev2
None 0.2.1 2017 0.2.1_Rev3 0.2.1_Rev3
None 0.2.2 2023 0.2.2_j 0.2.2_j
0.2.2 0.2.2 2025 0.2.2 0.2.2
None 0.3.0 3003 0.3.0_j 0.3.0_j
0.3.0 0.3.0 3005 0.3.0 0.3.0
None 0.3.0 3006 0.3.0_Rev2 0.3.0_Rev2
None 0.3.0 3007 0.3.0_Rev3 0.3.0_Rev3
None 0.3.2 3023 0.3.2_j 0.3.2_j
0.3.2 0.3.2 3025 0.3.2 0.3.2
None 0.3.3 3030 0.3.3_j 0.3.3_j
0.3.3 0.3.3 3035 0.3.3 0.3.3
0.4.0 0.4.0 4000 0.4.0_j 0.4.0_j
0.4.0 0.4.0 4005 0.4.0 0.4.0
0.4.0 rev 2 0.4.0_Rev2 0.4.0_Rev2
0.4.0 rev 3 0.4.0_Rev3 0.4.0_Rev3
0.5.0 0.5.0 5000 0.5.0 0.5.0
0.5.0 0.5.0 5005 0.5.0 0.5.0
0.6.0 0.6.0 6006 0.6.0 0.6.0
0.6.1 0.6.1 30006010 0.6.1 0.6.1
0.7.0 0.7.0 30007000 0.7.0 0.7.0
0.7.1 0.7.1 30007010 0.7.1 0.7.1
0.7.2 0.7.2 30007020 0.7.2 0.7.2
0.7.3 0.7.3 40007040 0.7.3 0.7.3
0.7.4 0.7.4 50007040 0.7.4 0.7.4
0.7.5 0.7.5 50007050 0.7.5 0.7.5
0.7.6 0.7.6 50007060 0.7.6 0.7.6
None 0.8.0_test1 300800001 0.8.0.b1 0.8.0.b1
0.8.0 build 2 0.8.0 build 2 300800002 0.8.0.b2 0.8.0.b2
0.8.0 build 3 0.8.0 build 3 300800003 0.8.0.b3 0.8.0.b3
0.8.0 build 4 0.8.0 build 4 300800004 0.8.0.b4 0.8.0.b4
0.8.0 build 5 0.8.0 build 5 300800005 0.8.0.b5 0.8.0.b5
0.8.0 build 6 0.8.0 build 6 300800006 0.8.0.b6 0.8.0.b6
0.8.0 build 7 0.8.0 build 7 300800007 0.8.0.b7 0.8.0.b7
0.8.0 build 8 0.8.0 build 8 300800008 0.8.0.b8 0.8.0.b8
0.8.0 0.8.0 500800010 0.8.0 0.8.0
0.8.1 0.8.1 500801011 0.8.1 0.8.1
0.9.0 build 1 0.9.0 500900000 0.9.0.b1 0.9.0.b1
0.9.0 build 2 0.9.0 500900001 0.9.0.b2 0.9.0.b2
0.9.0 build 3 0.9.0 500900002 0.9.0.b3 0.9.0.b3
0.9.0 build 4 0.9.0 500900003 0.9.0.b4 0.9.0.b4
0.9.0 build 5 0.9.0 500900004 0.9.0.b5 0.9.0.b5
0.9.0 build 6 0.9.0 500900005 0.9.0.b6 0.9.0.b6
0.9.0 build 7 0.9.0 500900006 0.9.0.b7 0.9.0.b7
0.9.0 build 8 0.9.0 500900007 0.9.0.b8 0.9.0.b8
0.9.0 build 9 0.9.0 500900008 0.9.0.b9 0.9.0.b9
0.9.0 build 10 0.9.0 500900009 0.9.0.b10 0.9.0.b10
0.9.0 build 11 0.9.0 500900010 0.9.0.b11 0.9.0.b11
0.9.0 build 12 0.9.0 500900011 0.9.0.b12 0.9.0.b12
0.9.0 0.9.0 500900012 0.9.0 0.9.0
0.9.1 0.9.1 500901000 0.9.1 0.9.1
0.9.2 0.9.2 500902000 0.9.2 0.9.2
0.9.3 0.9.3 500903000 0.9.3 0.9.3
0.9.4 0.9.4 500904000 0.9.4 0.9.4
0.9.5 0.9.5 500905000 0.9.5 0.9.5
None 0.9.5 500905001 0.9.5_Rev2 0.9.5_Rev2
0.10.0 build 1 0.10.0 740100000 0.10.0.b1 0.10.0.b1
0.10.0 build 2 0.10.0 740100001 0.10.0.b2 0.10.0.b2
0.10.0 build 3 0.10.0 740100002 0.10.0.b3 0.10.0.b3
0.10.0 build 4 0.10.0 740100003 0.10.0.b4 0.10.0.b4
0.10.0 build 5 0.10.0 740100004 0.10.0.b5 0.10.0.b5
0.10.0 build 6 0.10.0 740100005 0.10.0.b6 0.10.0.b6
0.10.0 build 7 0.10.0 740100006 0.10.0.b7 0.10.0.b7
0.10.0 build 8 0.10.0 740100007 0.10.0.b8 0.10.0.b8
0.10.0 build 9 0.10.0 740100008 0.10.0.b9 0.10.0.b9
0.10.0 0.10.0 740100009 0.10.0 0.10.0
0.10.1 0.10.1 740100100 0.10.1 0.10.1
0.10.2 0.10.2 740100200 0.10.2 0.10.2
0.10.3 0.10.3 740100300 0.10.3 0.10.3
0.10.4 0.10.4 740100400 0.10.4 0.10.4
0.10.5 0.10.5 740100501 0.10.5 0.10.5
0.11.0 build 1 0.11.0 740110001 0.11.0.b1 0.11.0.b1
0.11.0 build 2 0.11.0 740110002 0.11.0.b2 0.11.0.b2
0.11.0 build 3 0.11.0 740110003 0.11.0.b3 0.11.0.b3
0.11.0 build 4 0.11.0.b4 740110004 0.11.0.b4 0.11.0.b4
0.11.0 build 5 0.11.0.b5 740110005 0.11.0.b5 0.11.0.b5
0.11.0 build 6 0.11.0.b6 740110006 0.11.0.b6 0.11.0.b6
0.11.0 build 7 0.11.0.b7 740110007 0.11.0.b7 0.11.0.b7
0.11.0 build 8 0.11.0.b8 740110008 0.11.0.b8 0.11.0.b8
0.11.0 build 9 0.11.0.b9 740110009 0.11.0.b9 0.11.0.b9
0.11.0 build 10 0.11.0.b10 740110010 0.11.0.b10 0.11.0.b10
0.11.0 build 11 0.11.0.b11 740110011 0.11.0.b11 0.11.0.b11
0.11.0 build 12 0.11.0.b12 740110012 0.11.0.b12 0.11.0.b12
0.11.0 build 13 0.11.0.b13 740110013 0.11.0.b13 0.11.0.b13
0.11.0 build 14 0.11.0.b14 740110014 0.11.0.b14 0.11.0.b14
0.11.0 0.11.0 740110015 0.11.0 0.11.0
0.11.1 0.11.1 740110101 0.11.1 0.11.1
None 0.11.1 740110102 0.11.1_Rev2 0.11.1_Rev2
0.11.2 0.11.2 0.11.2 0.11.2
0.12.0 0.12.0 0.12.0 0.12.0
0.12.0.1 0.12.0.1 0.12.0.1 0.12.0.1
0.12.1 build 1 0.12.1.b1 760120101 0.12.1.b1 0.12.1.b1
0.12.1 build 2 0.12.1.b2 760120102 0.12.1.b2 0.12.1.b2
0.12.1 build 3 0.12.1.b3 760120103 0.12.1.b3 0.12.1.b3
0.12.1 build 4 0.12.1.b4 760120104 0.12.1.b4 0.12.1.b4
0.12.1 build 5 0.12.1.b5 760120105 0.12.1.b5 0.12.1.b5
0.12.1 build 6 0.12.1.b6 760120106 0.12.1.b6 0.12.1.b6
0.12.1 build 7 0.12.1.b7 760120107 0.12.1.b7 0.12.1.b7
0.12.1 build 8 0.12.1.b8 760120108 0.12.1.b8 0.12.1.b8
0.12.1 build 9 0.12.1.b9 760120109 0.12.1.b9 0.12.1.b9
0.12.1 build 10 0.12.1.b10 760120110 0.12.1.b10 0.12.1.b10
0.12.1 build 11 0.12.1.b11 760120111 0.12.1.b11 0.12.1.b11
0.12.1 build 12 0.12.1.b12 760120112 0.12.1.b12 0.12.1.b12
0.12.1 build 13 0.12.1.b13 760120113 0.12.1.b13 0.12.1.b13
0.12.1 0.12.1 760120114 0.12.1 0.12.1
0.12.2 0.12.2 760120200 0.12.2 0.12.2
0.12.3 0.12.3 760120300 0.12.3 0.12.3
0.13.0 build 1 0.13.0.b1 760130001 0.13.0.b1 0.13.0.b1
0.13.0 build 2 0.13.0.b2 760130002 0.13.0.b2 0.13.0.b2
0.13.0 build 3 0.13.0.b3 760130003 0.13.0.b3 0.13.0.b3
0.13.0 build 4 0.13.0.b4 760130004 0.13.0.b4 0.13.0.b4
0.13.0 build 5 0.13.0.b5 760130005 0.13.0.b5 0.13.0.b5
0.13.0 0.13.0 760130000 0.13.0 0.13.0
0.13.1 0.13.1 760130100 0.13.1 0.13.1
0.13.2 0.13.2 760130200 0.13.2 0.13.2
None 0.13.2 760130201 0.13.2_Rev2 0.13.2_Rev2
None 0.13.2 760130202 0.13.2_Rev3 0.13.2_Rev3
0.14.0 build 1 0.14.0.b1 760140001 0.14.0.b1 0.14.0.b1
0.14.0 build 2 0.14.0.b2 760140002 0.14.0.b2 0.14.0.b2
0.14.0 build 3 0.14.0.b3 760140003 0.14.0.b3 0.14.0.b3
0.14.0 build 4 0.14.0.b4 760140004 0.14.0.b4 0.14.0.b4
0.14.0 build 5 0.14.0.b5 760140005 0.14.0.b5 0.14.0.b5
0.14.0 build 6 0.14.0.b6 760140006 0.14.0.b6 0.14.0.b6
0.14.0 build 7 0.14.0.b7 760140007 0.14.0.b7 0.14.0.b7
0.14.0 0.14.0 760140009 0.14.0 0.14.0
0.14.1 0.14.1 760140100 0.14.1 0.14.1
0.14.2 0.14.2 760140200 0.14.2 0.14.2
0.14.3 0.14.3 760140300 0.14.3 0.14.3
None 0.14.3 760140301 0.14.3_Rev2 0.14.3_Rev2
Realms build 1 0.15.0.a2 781150002 0.15.0.a2 0.15.0.a2
Realms build 2 0.15.0.a3 781150003 0.15.0.a3 0.15.0.a3
Realms build 4 0.15.0.a4 781150004 0.15.0.a4 0.15.0.a4
0.15.0 build 1 0.14.99.0 870149900 0.14.99.0 0.14.99.0
0.15.0 build 2 0.14.99.2 870149902 0.14.99.2 0.14.99.2
0.15.0 build 3 0.14.99.3 870149903 0.14.99.3 0.14.99.3
0.15.0 0.15.0.1 870150001 0.15.0 0.15.0.1
0.15.1 build 1 0.15.0.50 870150050 0.15.0.50 0.15.0.50
0.15.1 0.15.1.2 870150102 0.15.1 0.15.1.2
0.15.2 0.15.2.1 870150201 0.15.2 0.15.2.1
0.15.3 0.15.3.2 870150302 0.15.3 0.15.3.2
0.15.4 0.15.4.0 870150400 0.15.4 0.15.4.0
0.15.6 0.15.6.0 870150600 0.15.6 0.15.6.0
0.15.7 0.15.7.2 870150702 0.15.7 0.15.7.2
0.15.8 0.15.8.0 870150800 0.15.8 0.15.8.0
None 0.15.8.1 870150801 0.15.8.1 0.15.8.1
0.15.9 0.15.9.0 870150900 0.15.9 0.15.9.0
0.15.10 0.15.10.0 870151000 0.15.10 0.15.10.0
0.16.0 build 1 0.15.90.0 870159000 0.15.90.0 0.15.90.0
0.16.0 build 2 0.15.90.1 870159001 0.15.90.1 0.15.90.1
0.16.0 build 3 0.15.90.2 870159002 0.15.90.2 0.15.90.2
0.16.0 build 4 0.15.90.7 870159007 0.15.90.7 0.15.90.7
0.16.0 build 5 0.15.90.8 870159008 0.15.90.8 0.15.90.8
0.16.0 0.16.0.5 870160005 0.16.0 0.16.0.5
0.16.1 0.16.1.0 870160100 0.16.1 0.16.1.0
0.16.2 0.16.2.2 970160202 0.16.2 0.16.2.2
alpha 0.17.0.1 0.17.0.1 870170001 0.17.0.1 0.17.0.1
alpha 0.17.0.2 0.17.0.2 870170002 0.17.0.2 0.17.0.2
alpha 1.0.0.0 1.0.0.0 871000000 1.0.0.0 1.0.0.0
alpha 1.0.0.1 1.0.0.1 871000001 1.0.0.1 1.0.0.1
alpha 1.0.0.2 1.0.0.2 871000002 1.0.0.2 1.0.0.2
alpha 1.0.0.7 1.0.0.7 871000007 1.0.0.7 1.0.0.7
1.0.0 1.0.0.16 871000016 1.0.0 1.0.0.16
1.0.1 1.0.1 1.0.1
1.0.2 1.0.2.1 871000201 1.0.2 1.0.2.1
alpha 1.0.3.0 1.0.3.0 871000300 1.0.3.0 1.0.3.0
1.0.3 1.0.3.12 871000312 1.0.3 1.0.3.12
alpha 1.0.4.0 1.0.4.0 871000400 1.0.4.0 1.0.4.0
alpha 1.0.4.1 1.0.4.1 871000401 1.0.4.1 1.0.4.1
1.0.4 1.0.4.11 871000411 1.0.4 1.0.4.11
alpha 1.0.5.0 1.0.5.0 871000500 1.0.5.0 1.0.5.0
alpha 1.0.5.3 1.0.5.3 871000503 1.0.5.3 1.0.5.3
alpha 1.0.5.11 1.0.5.11 871000511 1.0.5.11 1.0.5.11
alpha 1.0.5.11 1.0.5.13 871000513 1.0.5.13 1.0.5.13
1.0.5 1.0.5.54 871000554 1.0.5 1.0.5.54
alpha 1.0.6.0 1.0.6.0 871000600 1.0.6.0 1.0.6.0
1.0.6 1.0.6.52 871000652 1.0.6 1.0.6.52
1.0.7 1.0.7.0 871000700 1.0.7 1.0.7.0
1.0.8 1.0.8.1 871000801 1.0.8 1.0.8.1
1.0.9 1.0.9.1 871000901 1.0.9 1.0.9.1
alpha 1.1.0.0 1.1.0.0 871010000 1.1.0.0 1.1.0.0
alpha 1.1.0.1 1.1.0.1 871010001 1.1.0.1 1.1.0.1
alpha 1.1.0.3 1.1.0.3 871010003 1.1.0.3 1.1.0.3
alpha 1.1.0.4 1.1.0.4 871010004 1.1.0.4 1.1.0.4
alpha 1.1.0.5 1.1.0.5 871010005 1.1.0.5 1.1.0.5
alpha 1.1.0.8 1.1.0.8 871010008 1.1.0.8 1.1.0.8
alpha 1.1.0.9 1.1.0.9 871010009 1.1.0.9 1.1.0.9
1.1.0 1.1.0.55 871010055 1.1.0 1.1.0.55
alpha 1.1.1.0 1.1.1.0 871010100 1.1.1.0 1.1.1.0
alpha 1.1.1.1 1.1.1.1 871010101 1.1.1.1 1.1.1.1
1.1.1 1.1.1.51 871010151 1.1.1 1.1.1.51
1.1.2 1.1.2.50 871010250 1.1.2 1.1.2.50
alpha 1.1.3.0 1.1.3.0 871010300 1.1.3.0 1.1.3.0
alpha 1.1.3.1 1.1.3.1 871010301 1.1.3.1 1.1.3.1
1.1.3 1.1.3.52 871010352 1.1.3 1.1.3.52
1.1.4 1.1.4.51 871010451 1.1.4 1.1.4.51
1.1.5 1.1.5.1 871010501 1.1.5 1.1.5.1
1.1.7 1.1.7 1.1.7
beta 1.2.0.2 1.2.0.2 871020002 1.2.0.2 1.2.0.2
beta 1.2.0.7 1.2.0.7 871020007 1.2.0.7 1.2.0.7
beta 1.2.0.9 1.2.0.9 871020009 1.2.0.9 1.2.0.9
beta 1.2.0.11 1.2.0.11 871020011 1.2.0.11 1.2.0.11
beta 1.2.0.15 1.2.0.15 871020015 1.2.0.15 1.2.0.15
beta 1.2.0.18 1.2.0.18 871020018 1.2.0.18 1.2.0.18
beta 1.2.0.22 1.2.0.22 871020022 1.2.0.22 1.2.0.22
beta 1.2.0.25 1.2.0.25 871020025 1.2.0.25 1.2.0.25
beta 1.2.0.31 1.2.0.31 871020031 1.2.0.31 1.2.0.31
1.2.0 1.2.0.81 871020081 1.2.0 1.2.0.81
1.2.1 1.2.1.1 871020101 1.2.1 1.2.1.1
1.2.2 1.2.2.3 871020203 1.2.2 1.2.2.3
beta 1.2.3.3 1.2.3.3 871020303 1.2.3.3 1.2.3.3
1.2.3 1.2.3.6 871020306 1.2.3 1.2.3.6
beta 1.2.5.0 1.2.5.0 871020500 1.2.5.0 1.2.5.0
beta 1.2.5.12 1.2.5.12 871020512 1.2.5.12 1.2.5.12
beta 1.2.5.15 1.2.5.15 871020515 1.2.5.15 1.2.5.15
1.2.5 1.2.5.52 871020552 1.2.5 1.2.5.52
beta 1.2.6.2 1.2.6.2 871020602 1.2.6.2 1.2.6.2
1.2.6 1.2.6.55 871020655 1.2.6 1.2.6.55
1.2.6.1 1.2.6.60 871020660 1.2.6.60 1.2.6.60
1.2.7 1.2.7.2 841020702 1.2.7 1.2.7.2
1.2.8 1.2.8.0 871020800 1.2.8 1.2.8.0
1.2.9 1.2.9.1 871020901 1.2.9 1.2.9.1
beta 1.2.10.1 1.2.10.1 871021001 1.2.10.1 1.2.10.1
1.2.10 1.2.10.2 871021002 1.2.10 1.2.10.2
1.2.11 1.2.11.4 871021104 1.2.11 1.2.11.4
beta 1.2.13.5 1.2.13.5 871021305 1.2.13.5 1.2.13.5
beta 1.2.13.6 1.2.13.6 871021306 1.2.13.6 1.2.13.6
beta 1.2.13.8 1.2.13.8 871021308 1.2.13.8 1.2.13.8
beta 1.2.13.10 1.2.13.10 871021310 1.2.13.10 1.2.13.10
beta 1.2.13.11 1.2.13.11 871021311 1.2.13.11 1.2.13.11
beta 1.2.13.12 1.2.13.12 871021312 1.2.13.12 1.2.13.12
1.2.13 1.2.13.54 871021354 1.2.13 1.2.13.54
1.2.13.60 1.2.13.60 871021360 1.2.13.60 1.2.13.60
beta 1.2.14.2 1.2.14.2 871021402 1.2.14.2 1.2.14.2
beta 1.2.14.3 1.2.14.3 871021403 1.2.14.3 1.2.14.3
1.2.14 1.2.14 1.2.14
1.2.15 1.2.15.01 1.2.15 1.2.15.01
1.2.13.60 1.2.16.3 1.2.16 1.2.16.3
beta 1.2.20.1 1.2.20.1 871022001 1.2.20.1 1.2.20.1
beta 1.2.20.2 1.2.20.2 871022002 1.2.20.2 1.2.20.2
1.4.0 1.4.0.5 871040005 1.4.0 1.4.0.5
1.4.1 1.4.1.0 871040100 1.4.1 1.4.1.0
1.4.2 1.4.2.0 871040200 1.4.2 1.4.2.0
1.4.3 1.4.3.0 1.4.3 1.4.3.0
1.4.4 1.4.4.0 871040400 1.4.4 1.4.4.0
beta 1.5.0.0 1.5.0.0 871050000 1.5.0.0 1.5.0.0
beta 1.5.0.1 1.5.0.1 871050001 1.5.0.1 1.5.0.1
beta 1.5.0.4 1.5.0.4 871050004 1.5.0.4 1.5.0.4
beta 1.5.0.7 1.5.0.7 871050007 1.5.0.7 1.5.0.7
beta 1.5.0.10 1.5.0.10 871050010 1.5.0.10 1.5.0.10
1.5.0 1.5.0.14 871050014 1.5.0 1.5.0.14
1.5.1 1.5.1.2 871050102 1.5.1 1.5.1.2
1.5.2 1.5.2.1 871050201 1.5.2 1.5.2.1
1.5.3 1.5.3.0 871050300 1.5.3 1.5.3.0
beta 1.6.0.1 1.6.0.1 871060001 1.6.0.1 1.6.0.1
beta 1.6.0.5 1.6.0.5 871060005 1.6.0.5 1.6.0.5
beta 1.6.0.6 1.6.0.6 871060006 1.6.0.6 1.6.0.6
beta 1.6.0.8 1.6.0.8 871060008 1.6.0.8 1.6.0.8
1.6.0 1.6.0.14 871060014 1.6.0 1.6.0.14
beta 1.6.0.30 1.6.0.30 871060030 1.6.0.30 1.6.0.30
1.6.1 1.6.1.0 871060100 1.6.1 1.6.1.0
1.6.2 1.6.2 1.6.2
beta 1.7.0.2 1.7.0.2 871070002 1.7.0.2 1.7.0.2
beta 1.7.0.3 1.7.0.3 871070003 1.7.0.3 1.7.0.3
beta 1.7.0.5 1.7.0.5 871070005 1.7.0.5 1.7.0.5
beta 1.7.0.7 1.7.0.7 871070007 1.7.0.7 1.7.0.7
beta 1.7.0.9 1.7.0.9 871070009 1.7.0.9 1.7.0.9
1.7.0 1.7.0.13 871070013 1.7.0 1.7.0.13
1.7.1 1.7.1 1.7.1
1.7.3 1.7.3 1.7.3
None 1.7.9.0 871070900 1.7.9 1.7.9.0
beta 1.8.0.8 1.8.0.8 871080008 1.8.0.8 1.8.0.8
beta 1.8.0.10 1.8.0.10 871080010 1.8.0.10 1.8.0.10
beta 1.8.0.11 1.8.0.11 871080011 1.8.0.11 1.8.0.11
beta 1.8.0.13 1.8.0.13 871080013 1.8.0.13 1.8.0.13
beta 1.8.0.14 1.8.0.14 871080014 1.8.0.14 1.8.0.14
1.8.0 1.8.0.24 871080024 1.8.0 1.8.0.24
1.8.1 1.8.1.2 871080102 1.8.1 1.8.1.2
None 1.8.9.25 871080925 1.8.9 1.8.9.25
beta 1.9.0.0 1.9.0.0 871090000 1.9.0.0 1.9.0.0
beta 1.9.0.2 1.9.0.2 871090002 1.9.0.2 1.9.0.2
beta 1.9.0.3 1.9.0.3 871090003 1.9.0.3 1.9.0.3
beta 1.9.0.5 1.9.0.5 871090005 1.9.0.5 1.9.0.5
1.9.0 1.9.0.15 871090015 1.9.0 1.9.0.15
1.9.1 1.9.1 1.9.1
1.9.3 1.9.3 1.9.3
beta 1.10.0.3 1.10.0.3 871100003 1.10.0.3 1.10.0.3
beta 1.10.0.4 1.10.0.4 871100004 1.10.0.4 1.10.0.4
1.10.0 1.10.0.7 871100007 1.10.0 1.10.0.7
1.10.1 1.10.1 1.10.1
beta 1.11.0.1 1.11.0.1 871110001 1.11.0.1 1.11.0.1
beta 1.11.0.3 1.11.0.3 871110003 1.11.0.3 1.11.0.3
beta 1.11.0.4 1.11.0.4 871110004 1.11.0.4 1.11.0.4
beta 1.11.0.5 1.11.0.5 871110005 1.11.0.5 1.11.0.5
beta 1.11.0.7 1.11.0.7 871110007 1.11.0.7 1.11.0.7
beta 1.11.0.8 1.11.0.8 871110008 1.11.0.8 1.11.0.8
beta 1.11.0.9 1.11.0.9 871110009 1.11.0.9 1.11.0.9
beta 1.11.0.10 1.11.0.10 871110010 1.11.0.10 1.11.0.10
1.11.0 1.11.0.23 871110023 1.11.0 1.11.0.23
1.11.1 1.11.1.2 871110102 1.11.1 1.11.1.2
1.11.2 1.11.2.1 1.11.2 1.11.2.1
1.11.3 1.11.3.1 871110301 1.11.3 1.11.3.1
1.11.4 1.11.4.2 871110402 1.11.4 1.11.4.2
beta 1.12.0.2 1.12.0.2 871120002 1.12.0.2 1.12.0.2
beta 1.12.0.3 1.12.0.3 871120003 1.12.0.3 1.12.0.3
beta 1.12.0.4 1.12.0.4 871120004 1.12.0.4 1.12.0.4
beta 1.12.0.6 1.12.0.6 871120006 1.12.0.6 1.12.0.6
beta 1.12.0.9 1.12.0.9 871120009 1.12.0.9 1.12.0.9
beta 1.12.0.10 1.12.0.10 871120010 1.12.0.10 1.12.0.10
beta 1.12.0.11 1.12.0.11 871120011 1.12.0.11 1.12.0.11
beta 1.12.0.12 1.12.0.12 871120012 1.12.0.12 1.12.0.12
beta 1.12.0.13 1.12.0.13 871120013 1.12.0.13 1.12.0.13
beta 1.12.0.14 1.12.0.14 871120014 1.12.0.14 1.12.0.14
1.12.0 1.12.0.28 871120028 1.12.0 1.12.0.28
1.12.1 1.12.1.1 871120101 1.12.1 1.12.1.1
1.12.3 1.12.3 1.12.3
1.12.5 1.12.5 1.12.5
1.12.60 1.12.60 1.12.60
beta 1.13.0.1 1.13.0.1 871130001 1.13.0.1 1.13.0.1
beta 1.13.0.2 1.13.0.2 871130002 1.13.0.2 1.13.0.2
beta 1.13.0.4 1.13.0.4 871130004 1.13.0.4 1.13.0.4
beta 1.13.0.5 1.13.0.5 871130005 1.13.0.5 1.13.0.5
beta 1.13.0.6 1.13.0.6 871130006 1.13.0.6 1.13.0.6
beta 1.13.0.13 1.13.0.13 871130013 1.13.0.13 1.13.0.13
beta 1.13.0.15 1.13.0.15 871130015 1.13.0.15 1.13.0.15
beta 1.13.0.16 1.13.0.16 1.13.0.16 1.13.0.16
beta 1.13.0.17 1.13.0.17 1.13.0.17 1.13.0.17
beta 1.13.0.18 1.13.0.18 941130018 1.13.0.18 1.13.0.18
1.13.0 1.13.0.34 941130034 1.13.0 1.13.0.34
1.13.1 1.13.1.5 941130105 1.13.1 1.13.1.5
beta 1.14.0.1 1.14.0.1 941140001 1.14.0.1 1.14.0.1
beta 1.14.0.2 1.14.0.2 941140002 1.14.0.2 1.14.0.2
beta 1.14.0.3 1.14.0.3 941140003 1.14.0.3 1.14.0.3
beta 1.14.0.4 1.14.0.4 941140004 1.14.0.4 1.14.0.4
beta 1.14.0.6 1.14.0.6 941140006 1.14.0.6 1.14.0.6
1.14.0 1.14.0.9 941140009 1.14.0 1.14.0.9
beta 1.14.0.50 1.14.0.50 941140050 1.14.0.50 1.14.0.50
beta 1.14.0.51 1.14.0.51 941140051 1.14.0.51 1.14.0.51
beta 1.14.0.52 1.14.0.52 941140052 1.14.0.52 1.14.0.52
beta 1.14.1.2 1.14.1.2 941140102 1.14.1.2 1.14.1.2
beta 1.14.1.3 1.14.1.3 941140103 1.14.1.3 1.14.1.3
None 1.14.1.4 941140104 1.14.1 1.14.1.4
1.14.1 1.14.1.5 941140105 1.14.1.5 1.14.1.5
beta 1.14.2.50 1.14.2.50 941140250 1.14.2.50 1.14.2.50
beta 1.14.2.51 1.14.2.51 941140251 1.14.2.51 1.14.2.51
1.14.20 1.14.20.1 941142001 1.14.20 1.14.20.1
beta 1.14.25.1 1.14.25.1 941142501 1.14.25.1 1.14.25.1
1.14.30 1.14.30.2 941143002 1.14.30 1.14.30.2
1.14.30 1.14.30.06 283143006 1.14.30.06 1.14.30.06
beta 1.14.30.51 1.14.30.51 941143051 1.14.30.51 1.14.30.51
1.14.31 1.14.31.0 283143100 1.14.31 1.14.31.0
1.14.32 1.14.32.0 283143200 1.14.32 1.14.32.0
1.14.41 1.14.41 1.14.41
1.14.50 1.14.50.0 283145000 1.14.50 1.14.50.0
1.14.60 1.14.60.5 1.14.60 1.14.60.5
beta 1.15.0.8 1.15.0.8 1.15.0.8 1.15.0.8
beta 1.15.0.9 1.15.0.9 1.15.0.9 1.15.0.9
beta 1.15.0.11 1.15.0.11 1.15.0.11 1.15.0.11
beta 1.15.0.51 1.15.0.51 1.15.0.51 1.15.0.51
beta 1.15.0.53 1.15.0.53 1.15.0.53 1.15.0.53
beta 1.15.0.54 1.15.0.54 1.15.0.54 1.15.0.54
beta 1.15.0.55 1.15.0.55 1.15.0.55 1.15.0.55
beta 1.15.0.56 1.15.0.56 1.15.0.56 1.15.0.56
1.16.0 1.16.0.2 1.16.0 1.16.0.2
beta 1.16.0.51 1.16.0.51 1.16.0.51 1.16.0.51
beta 1.16.0.53 1.16.0.53 1.16.0.53 1.16.0.53
beta 1.16.0.55 1.16.0.55 1.16.0.55 1.16.0.55
beta 1.16.0.57 1.16.0.57 1.16.0.57 1.16.0.57
beta 1.16.0.58 1.16.0.58 1.16.0.58 1.16.0.58
beta 1.16.0.59 1.16.0.59 1.16.0.59 1.16.0.59
beta 1.16.0.60 1.16.0.60 1.16.0.60 1.16.0.60
beta 1.16.0.61 1.16.0.61 1.16.0.61 1.16.0.61
beta 1.16.0.63 1.16.0.63 1.16.0.63 1.16.0.63
beta 1.16.0.64 1.16.0.64 1.16.0.64 1.16.0.64
beta 1.16.0.66 1.16.0.66 1.16.0.66 1.16.0.66
beta 1.16.0.67 1.16.0.67 1.16.0.67 1.16.0.67
beta 1.16.0.68 1.16.0.68 1.16.0.68 1.16.0.68
1.16.1 1.16.1.02 1.16.1 1.16.1.02
1.16.1.03 1.16.1.03 1.16.1.03 1.16.1.03
1.16.1.04 1.16.1.04 1.16.1.04 1.16.1.04
1.16.10 1.16.10.02 1.16.10 1.16.10.02
beta 1.16.20.50 1.16.20.50 943162050 1.16.20.50 1.16.20.50
beta 1.16.20.52 1.16.20.52 943162052 1.16.20.52 1.16.20.52
beta 1.16.20.53 1.16.20.53 943162053 1.16.20.53 1.16.20.53
beta 1.16.20.54 1.16.20.54 943162054 1.16.20.54 1.16.20.54
1.16.21 1.16.21.01 1.16.21 1.16.21.01
beta 1.16.30.52 1.16.30.52 1.16.30.52 1.16.30.52
beta 1.16.30.53 1.16.30.53 1.16.30.53 1.16.30.53
beta 1.16.30.56 1.16.30.56 1.16.30.56 1.16.30.56
beta 1.16.30.57 1.16.30.57 1.16.30.57 1.16.30.57
1.16.40 1.16.40.02 1.16.40 1.16.40.02
1.16.42 1.16.42 1.16.42
1.16.50 1.16.50 1.16.50
1.16.60 1.16.60 1.16.60
1.16.61 1.16.61 1.16.61
1.16.100 1.16.100.04 1.16.100 1.16.100.04
beta 1.16.100.50 1.16.100.50 953610050 1.16.100.50 1.16.100.50
beta 1.16.100.51 1.16.100.51 953610051 1.16.100.51 1.16.100.51
beta 1.16.100.52 1.16.100.52 953610052 1.16.100.52 1.16.100.52
beta 1.16.100.53 1.16.100.53 953610053 1.16.100.53 1.16.100.53
beta 1.16.100.54 1.16.100.54 953610054 1.16.100.54 1.16.100.54
beta 1.16.100.55 1.16.100.55 953610055 1.16.100.55 1.16.100.55
beta 1.16.100.56 1.16.100.56 1.16.100.56 1.16.100.56
beta 1.16.100.57 1.16.100.57 953610057 1.16.100.57 1.16.100.57
beta 1.16.100.58 1.16.100.58 953610058 1.16.100.58 1.16.100.58
beta 1.16.100.59 1.16.100.59 953610059 1.16.100.59 1.16.100.59
beta 1.16.100.60 1.16.100.60 953610060 1.16.100.60 1.16.100.60
1.16.101 1.16.101.01 1.16.101 1.16.101.01
1.16.200 1.16.200.02 1.16.200 1.16.200.02
beta 1.16.200.51 1.16.200.51 971620051 1.16.200.51 1.16.200.51
beta 1.16.200.52 1.16.200.52 971620052 1.16.200.52 1.16.200.52
beta 1.16.200.53 1.16.200.53 971620053 1.16.200.53 1.16.200.53
beta 1.16.200.55 1.16.200.55 971620055 1.16.200.55 1.16.200.55
beta 1.16.200.56 1.16.200.56 971620056 1.16.200.56 1.16.200.56
beta 1.16.200.57 1.16.200.57 971620057 1.16.200.57 1.16.200.57
1.16.201 1.16.201.01 1.16.201 1.16.201.01
1.16.201 1.16.201.02 1.16.201.02 1.16.201.02
1.16.201 1.16.201.03 1.16.201.03 1.16.201.03
beta 1.16.210.50 1.16.210.50 971621050 1.16.210.50 1.16.210.50
beta 1.16.210.51 1.16.210.51 971621051 1.16.210.51 1.16.210.51
beta 1.16.210.53 1.16.210.53 971621053 1.16.210.53 1.16.210.53
beta 1.16.210.54 1.16.210.54 971621054 1.16.210.54 1.16.210.54
beta 1.16.210.55 1.16.210.55 971621055 1.16.210.55 1.16.210.55
beta 1.16.210.56 1.16.210.56 1.16.210.56 1.16.210.56
beta 1.16.210.57 1.16.210.57 1.16.210.57 1.16.210.57
beta 1.16.210.58 1.16.210.58 1.16.210.58 1.16.210.58
beta 1.16.210.59 1.16.210.59 1.16.210.59 1.16.210.59

--SkyE | Talk · Contributions · Logs 06:51, 17 February 2021 (UTC)

Minecraft Dungeons

Dungeons
This section has been created to separate Dungeons wiki related topics and proposals from the sea of other topics in this portal, mainly for my own convenience. If this is of issue then please notify me of such so that I am aware to not do so in future. 🍍 Raybeano99 (Talk) 09:45, 16 February 2021 (UTC)

Extension to Style Guide

Related discussion in Wiki Discord (2021-02-14)

As the dungeons wiki continues to expand there has become a desire and a need for a Style Guide that caters specificity to aspects that likely are not evident in general MCW pages or MC and MCE wikis. WIth MCD:Flames of the Nether and a large free update rapidly approaching bring a large quantity of new content, I believe it would be beneficial if we had something to guide Dungeons editors, including myself, to ensure consistency, convenience, and quality of pages and files.

This specific style guide can touch upon image naming schemes for dungeons equipment images (See: User:Raybeano99/MCD_EquipStyle), common page layouts for general articles, equipment articles, mission articles ect., inform about commonly used templates and appropriate scale values for using them, and probably much ,much more that I, myself, have not even thought about.
Preferably, this is to be viewed as an extension with tweaks upon the existing MCW:STYLE rather than a transcluded/duplicated page with some modifications. I have a few ideas on how this could be implemented:

Style 1 - Append onto existing MCW:STYLE page.

  • A new section could be created and enveloped within a distinctive #f4efe6 coloured box and text to ensure viewers recognise that the contained information is specific for the Dungeons WIki. Alternately, dungeons specific information are appended onto existing sections and subsections.
  • Clear that the information is an extension rather than a replacement or equivalent.
  • Centralised - Come one, come all, all ye need lies within a single page of wonderful info.
  • Most exposure to all editors of the wiki - More feedback, critique, and viewpoints from editors to ensure that the style guide is constructed up to a high standard. Also more users are likely to view it.
  • Flow, bit of a double edge - Centralised page would allow the whole MCW:STYLE to be read without trying to find other places for info. However, this may flow too well. Users may not recognise the section as dungeons specific, even with crystal clear visual elements and text, and apply the information onto non-dungeons pages, or miss/disregard the information altogether.
  • Expansion concerns - The existing style guide may become formidably long over time as the dungeons specific section expands and adds detail.

Style 2 - A subpage of MCW:STYLE.

  • A page to contain the dungeons specific information. linked by a visually-distinct hatnote on the MCW:STYLE.
  • Still clear that the information is an extension rather than a replacement or equivalent.
  • Expansion concerns are no longer a concern.
  • Flow concerns mitigated - Information not all in one place thus the distinction that the information is for dungeons specifically is more clear.
  • Moderate exposure to all editors of the wiki - Likely less exposure than style 1.
  • There must certainly be a clear negative somewhere but I am unable to think of one.
  • MCW:Style Guide/Dungeons, MCW:Style Guide/MCD perhaps?

Style 3 - A page within the Minecraft Dungeons namespace.

  • A page to contain the dungeons specific information close to home in the dungeons. linked by a visually-distinct hatnote on the MCW:STYLE.
  • Style - All the visual glory of the dungeons is applied onto the page.
  • Expansion concerns are no longer a concern.
  • Flow concerns mitigated - Information not all in one place thus the distinction that the information is for dungeons specifically is undoubtedly clear, especially with the dungeons namespace.
  • Least exposure to all editors of the wiki - Probably less exposure than style 1 or style 2.
  • Probably another negative exists but I am unable to think of one.
  • MCD:Style Guide perhaps?

I have personal preference for the dungeons style guide extension to become its own page in some form that style 2 and style 3 provides.

  • 🤔 Would this lead to further specificity for other MCW pages such as the portal, tasks and projects? Would that be a concern? Could further pages make things more cumbersome and difficult?

🍍 Raybeano99 (Talk) 09:45, 16 February 2021 (UTC)

Style 1
I don't fully agree with this approach. Pertaining to keeping different kind of information simultaneously can be difficult to navigate and may lead to some confusion. A similar problem to this is the difference of information between Java and Bedrock. So as to resolve, the community decided to use {{in}}/{{only}} whenever the provided information contain disparities. This solution should not be used in terms of information that are fundamental to the wiki, like style guides. Another solution such as adding a background color or new section wouldn't help as much. Furthermore, similar styling to background color has already been defined and it requires new knowledge for people to realize the distinction.
Style 2
I totally agree in separating the page from the main style guide. By separating the page, there will be more freedom for expansion whilst not polluting the current page with MCD guides. Regarding misdirections, they are enough to be resolved by using a hat note or message box. For page name, I would say that Minecraft_Wiki:Style_guide/Minecraft_Dungeons is good enough.
Before talking about extensions to the style guide, maybe the editors of Minecraft Dungeons articles could work harder to follow the basic style guidelines that already exist, such as not using title case in headings, not capitalizing things in text that aren't proper nouns, refraining from filling articles with indiscriminate lists of trivia (which I have worked hard to clean up), and so on. The last thing we need is new guidance that conflicts with or creates exceptions to guidelines we already have. Amatulic (talk) 02:38, 1 June 2021 (UTC)
Style 3
It would be more appropriate to put meta information in the Minecraft Wiki namespace. As for MCD:Style, I guess it can be used as a redirect to the MCW namespace for shortcut. Also I wouldn't personally be bothered with the design aspect of the page.
In addition, I feel like the sidebar could have the style guide to link specifically when you are in the MCD namespace. Thus resolving the concern of exposure of the page, especially to MCD editors. Other maintenance/community pages like community portal, projects, etc. shouldn't be a concern, at least for now. – ItsPlantseed ⟨₰|₢⟩ 11:20, 16 February 2021 (UTC)
Having a dynamic sidebar that alters to suit the namespace the user is in would be a brilliant implementation and not just for the style guide exposure. I do recall a discussion in the discord where an issue that prevents namespace dependent sidebars from functioning was mentioned. I suppose until that is resolved, we can’t poke the sidebar in a dynamic fashion. Could have Dungeons Style Guide be under Style Guide until that fix arrives.
Style 1 could certainly end up becoming messy and unclear for all members involved, I agree with your views.
Style 2 & 3 design aspect is agreeably low priority and appropriate location should have possess weight. Some design aspects can be determined by the page through the source so things can be solved on that front.
Minecraft_Wiki:Style_guide/Minecraft_Dungeons with MCD:Style and MCW:Style Dungeons as redirects perhaps? Maybe only the one redirect shortcut is required. 🍍 Raybeano99 (Talk) 14:55, 16 February 2021 (UTC)

Centralised Datapage

Related discussion in Wiki Discord (2021-02-04)

In the Dungeons namespace, there are multiple pages that duplicate the same information that must be kept updated, consistently styled, and worded correctly. For instance:

Some of these pages present the information in different styles to match the context of these pages.

To make numerous edits across multiple pages is tiring, time-consuming, introduces error, and new editors may be unaware of the different information location. A centralised place to edit this frequently used information will be immensely helpful. One edit to induce into many edits.
I am unaware on how to construct such a thing and implement it in a way that is accessible to locate, trivial to edit, future-proof, and easy to implement into pages.

Please share your thoughts on this and how such a thing could be constructed. A dedicated Sandbox page with subpages could be created for testing purposes.
🍍 Raybeano99 (Talk) 09:45, 16 February 2021 (UTC)

UPDATE: Consideration for the use of Cargo. Discussed at Wiki Discord 2021-03-2021

Wiki channel in the Official Dungeons Discord

This is a thought that has been swimming around in my mind for some time. The Dungeons wiki does not have a huge quantity of editors that are immensely experienced with the game and its internals. There is also, unfortunately, a partial community consensus that any dungeons wikis are untrustworthy and information from them is to be treated with caution. This is something we need to resolve and gain the trust in the community.
The Official Dungeons Discord hosts a large quantity (but not overwhelmingly large!) of experienced players that educate, advise, and guide others but are unfamiliar with wiki editing. I believe there to be a fiction when learning how to edit the wiki with there being a few places to learn such with huge exposure. This wiki, MediaWiki Wiki, Help Wiki and the MCW:Discord (side note: I am very glad the wiki hosts a Discord Server.) are all brilliant places to start learning how to wiki edit however, they are not frequently seen or you need to ask around and explore to find them.

As a moderator of the dungeons discord, I have been able to internally propose the idea of a wiki dedicated channel - a place for dungeons folk to comfortably discuss wiki pages and information without worrying about unintentionally misinforming other players or being disruptive to existing channels. Information and links directing to wiki rules, help wikis, frequently used templates, and some wiki editing tools (ie: the generate spreadsheet on User:Raybeano99 userpage) will be made available as a pinned message. Speculation and general chat will not be permitted in the channel and will be held to a high standard. Specialised roles have not been discussed and will be handled internally.
The internal proposition was to gain feedback and thoughts from the rest of the admins and the moderators before establishing further communications. Unfortunately, the response turnout has been unexpectedly low however, none have made an explicit deny to the channel implementation. Hence me making communications here to gain your thoughts whether ye be a passer-by, an editor, admin or above to ignite the idea again.
I am in belief that implementation would not immediately yield desired output... could be slow, could be nothing, maybe something worth the attempt. Can always be removed quicker than the time taken to make the channel. Reverting and backtracking is not a concern

  • Exposure - More people experienced with the game will be informed of the wiki's existence and can contribute! This could also increase the frequency of disruptive, defacing edits.
  • New place to learn - Another place for editors to gain assistance from other editors.
  • Communication fragmentation - This, personally, is a huge concern. Could be mitigated by instructing users to provide the discord message link of the first substantial message in a conversation in the talk page of the page in discussion.
  • 🤔 What about Wiki Discord's #dungeons-wiki channel? - Something to be considered is if the implementation of a wiki channel on the official discord would have any impact on the existing Wiki Discord.

🍍 Raybeano99 (Talk) 09:45, 16 February 2021 (UTC)

Neutral to weak oppose. Agree with the three points (except I'd say the first point is more positive than negative, rather than positive/negative to an approximately equal degree). I'd also like to add a fourth point (which is a rather major one for me). As I understand, the Dungeons server is run by Mojang, who may have a conflict of interest against the community in a number of aspects. As such, I'm not very positive about game developers controlling communities. Mojang in specific isn't a company I trust given some historical actions and additional information. --AttemptToCallNil (talk) 18:23, 8 April 2021 (UTC)

Tabbed Mob pages

Alt title: Merge “base” and “variant” mobs into a singular page.

Mobs in Minecraft Dungeons have different tiers (a term used by 1.8.0.0 patch notes referring to apocalypse plus changes) that exhibit the same behaviour but with, generally, increased statistics. For example. Zombie is tier I, the dagger variant of Armored Zombie is tier II, and the sword variant of Armored Zombie is tier III.

Rather than visually appending the information upon the “base” mob (as it would encumber the page), or, what is currently the case, separate pages for Tier I and Tier II&III, a single page could implement a tabbed experience that would allow viewers to select which tier of mob they wish the page, section, or specific component to display.

Perhaps something similar to the infobox used at Terraria's Blue Slime but fashioned so it that would influence the information on the page. This could be under the page title, attached to each section, or applicable components such as tables.

Unsure on whether tabbed consolidation should include Jungle and Frozen variants of Zombie, Skeleton, and Creeper…these are tier I mobs but with additional and/or modified attacks. Could that be considered significantly altered behaviour?
Also are charged creepers considered a higher tier of creeper? Also husks and drowned? Ancients?

  • Reduction of duplicated or fragmented applicable information.
  • Makes explicit that the mobs are related
  • 🟡 Less pages for near identical mobs and thus less entries on Mob. Could possibly be beneficial?
  • Potential to decrease accessibility.
  • Likely to increase complexity of page source and hinder visual editors.

🍍 Raybeano99 (Talk) 17:34, 2 April 2021 (UTC)

Oppose, I don't think this is a useful way of using tabs. Tabs tend to cause accessibility and technical problems as you said (I'd also add that links to anchors in non-default tabs may not work). Fandom staff keep telling editors that research has shown tabs are not an effective way of conveying information as tabs other than the first will be ignored by a large portion of readers. I'm not sure about your third point, I'd say this isn't a factor at all. About the second point, is "fun related" a typo for "unrelated"? I'm not sure what "fun related" means. --AttemptToCallNil (talk) 18:29, 8 April 2021 (UTC)
Typo… not sure how fun got in there. Has been corrected.
Yeah I could envision folk not recognising the tabs as clickable and missing the information enclosed within them thinking about it more. Wondering if there are other ways that the merge could be achieved… or perhaps the standard information suffixing might not be as encumbering as initially imagined. Would love any different ideas. 🍍 Raybeano99 (Talk) 18:54, 8 April 2021 (UTC)
Community content is available under CC BY-NC-SA unless otherwise noted.
More Fandoms