Talk: Community portal

Minecraft Wiki Community portal discussion page

This is the community's main discussion page.

Shortcuts

Talk about anything wiki-related here!
Sign your posts with ~~~~, add new posts below others, and click "Add topic" above for new topics.
Note that this page is NOT for suggesting new ideas about the game. That belongs on the feedback site.
This page is for community discussion; generally, wiki issue reports should go on the Admin's noticeboard and discussions about a single page do not belong here.

Proposal: remove images from history and put them into separate gallery subpages

This is distracting with how many animations there are. This is annoying to read and translate with how many images there are. This disrupts the flow of text because the images are large.

I propose to not put historical images into history lists directly, but instead maintain a history gallery subpage with the images. Notably, that would be a subpage and not a section, as I don't believe most readers would need those images, and so they're an invariable bandwidth/performance strain. --AttemptToCallNil (report bug, view backtrace) 09:26, 21 August 2020 (UTC)

Support, and while doing that for revisions, maybe it's also an idea to do it for the block states sections like with redstone wire? Currently, some block states are hard to understand with the explanation they have. Images for visual block state differences would help. FVbico (talk) 09:37, 21 August 2020 (UTC)

Support, it took a lot of time to update these spawn egg images on Chinese Wiki (from sprites to images), and barely does nothing. It might be a bit useful when there are a little images along with historical texts, but only a little.--

Lakejason0 (Talk • Contribs) 10:07, 21 August 2020 (UTC)

Support, they are just an eyesore at this point. I had this idea beforehand but not encouraged enough to make a remark. For now, I would only think that separating them is the best decision. – ItsPlantseed ⟨₰|₢⟩ 10:30, 21 August 2020 (UTC)

I'd say this is more of an issue with the History template itself than its contents, and we can all agree that said template is way overdue for a revamping. - User-12316399 (talk) 12:00, 21 August 2020 (UTC)

Agree with you, also Neutral about this topic---Humiebee^{Discuss anything with me Look at my edits} 12:56, 21 August 2020 (UTC)

Support, sheep kinda does this already. -PancakeIdentity (talk) 03:32, 23 August 2020 (UTC)

Support. — Thomanski | t | c | 13:15, 23 August 2020 (UTC)

Proposal

I have created a potential mock-up on User:Thomanski/Sandbox/Gallery for Log. Any feedback appreciated. — Thomanski | t | c | 13:15, 23 August 2020 (UTC)

Support. -DEJVOSS (talk) 13:47, 26 August 2020 (UTC)

Changed to Support---Humiebee^{Discuss anything with me Look at my edits} 17:29, 4 September 2020 (UTC)

Support || Remember this thing? File:Nether Reactor Core Revision 1.png Because I do. --Ninji2701 14:17, 27 December 2020 (UTC)

The problem with subpages

I think subpages are overused on this wiki. Wikipedia has disabled subpages in the main namespace and some others. Subpages cannot be accessed by clicking on the "Random page" link and only support one hierarchy while they may be more. I'm not saying to get rid of all subpages in the content namespaces, but to discourage some uses. Here's what I think when subpages should and should not be used:
Acceptable uses:

Anything that Wikipedia accepts as subpages—User subpages, template documentation, etc. It is laughable to even think about removing these subpages from the Minecraft wiki.
Mod pages (until all mod pages are moved to FTB)—The Minecraft Wiki only concerns the vanilla game. Although some of these pages are full articles, we don't want readers to end up on pages about specific mods.

Disallowed uses:

Writing about a feature of the same name for a different edition—These pages are articles and there are better ways to disambiguate the name than making it look like one article forms part of another when it does not.
Category subpages—Categories were created to replace mainspace subpages on Wikipedia. Using subpages for categories is pointless and sometimes the names get ridiculously long.
Mechanics pages—These pages are also articles, and in the past there was a dispute on whether these pages should be named "Mechanics/X" or "X/Mechanics".
Tutorials subpages—These pages are less like encyclopedia articles, but they still contain helpful instructional material so they should be moved to a new namespace.
File subpages—I don't know whether there are such pages or even if the subpage feature is enabled, but it should be disabled because some filenames create accidental subpages and hierarchy among files is bad.

Unsure:

Previous versions of features—These articles are useful to a historical perspective, but completely irrelevant in the latest version of the game.
Command subpages—These pages are legitimate articles, but pages starting with "/" cause technical problems.
Schematic pages—They are merely pseudo-images that are transcluded, but sometimes they may be used on more than one page so maybe they should be converted to templates.

There are more uses of subpages on this wiki but I am still unsure about whether they are acceptable. Fadyblok240 (talk) 21:23, 23 August 2020 (UTC)

My opinion. I'm going to list my strongest support on top and strongest oppose on the bottom (of what subpages should be allowed)

User subpages Definitely should be allowed.
Minecraft Wiki namespace subpages Definitely should be allowed.
Archive subpages Definitely should be allowed.
Documentation Definitely should be allowed (template)
Guides, Commands and Official subpages Should be allowed.
Previous versions of features Should be allowed.
Development versions subpages Should be allowed (ex:Java Edition 1.0.0/Development versions)
Subpages that make sense but are too technical to be in a main article (Ex:/DV, /Structure, Category Data Pages, or others).
Mod subpages Should be allowed (as they still haven't been completely exported yet)
Writing about a feature of the same name for a different edition Should maybe be allowed as it makes sense but the argument also makes sense so i'm sorta split?
Mechanics pages should be Moved to another subpage/possible tutorial namespace
Tutorials subpage should be Moved to another namespace
Category subpages should be Should not be allowed like theres such thing as subcategories (Ex Objects requiring isometric renders/Re-render)

1 more thing, what do you mean by previous versions of features? are you talking about Java Edition 1.13/Flattening? ---Humiebee^{Discuss anything with me Look at my edits} 22:59, 23 August 2020 (UTC)

Kinda, I meant pages like "X/Before <version>". which in my opinion I am still not sure about. Fadyblok240 (talk) 17:21, 24 August 2020 (UTC)

I support keeping those as let's take the Far lands, old farlands sounds so wrong and also, merging the Far Lands/Java Edition and Far Lands will create a lot of confusion, thats why it was split---Humiebee^{Discuss anything with me Look at my edits} 17:46, 24 August 2020 (UTC)

What does this (Writing about a feature of the same name for a different edition) mean? like I don't know any example and I'm pretty sure there's no subpage, can you give an example?---Humiebee^{Discuss anything with me Look at my edits} 17:48, 24 August 2020 (UTC)

A page like Achievements/Java Edition. I prefer moving pages like these to "<edition> X" (i.e. Java Edition Achievements and Java Edition Far Lands). I also support moving the current Far Lands page and moving it to Bedrock Edition Far Lands and leaving a disambiguation page behind. –Preceding unsigned comment was added by Fadyblok240 (talk • contribs) at 17:58, 24 August 2020 (UTC). Please sign your posts with ~~~~

I don't think moving "X/Edition" to "Edition X" is a good idea; the former provides a semantic relation that is more visible to search engines. I'm not sure what "category subpages" are or whether they are used on MCW. As for mechanics, "X/Mechanics" has the same consideration of semantic relation as with editions. --AttemptToCallNil (report bug, view backtrace) 18:01, 24 August 2020 (UTC)

There are already articles using the "Edition X" format, e.g. Java Edition mentioned features. Also, there is such a thing as category subpages on this wiki. I have reworked Template:Needs render to avoid category subpages, but Template:Render uses dozens of category subpages (e.g. Category:Objects requiring isometric renders/Historical features/Stems/Invalid states) which is too much for me to handle. Fadyblok240 (talk) 18:36, 24 August 2020 (UTC)

Above is 1 such example---Humiebee^{Discuss anything with me Look at my edits} 18:40, 24 August 2020 (UTC)

Oh, those? Yeah, I agree, they're not the best idea. --AttemptToCallNil (report bug, view backtrace) 18:43, 24 August 2020 (UTC)

Mixed opinion on this. Subpages automatically link back to their parent pages at the top and allows easy access to them; this is especially useful on mobile where neither categories nor navbox templates show up. With that in mind, I think it makes sense to keep at least the following as subpages (and probably other scenarios that I missed):

Subpages of Commands, Java Edition guides, and Official pages, where having the subpage format makes the page topic and allows quick access to the root article
Historical/outdated versions of articles
Subpages that are intended to be accessed directly, but don't make sense without the parent article (such as Enchanting/Levels, "/Structure" subpages, or the proposed gallery subpages)
Pages in Category:Data pages. Though transcluded like templates and not accessed directly, they describe article content.

However, I would support template-like subpages (such as Renewable resource/row) to the template namespace, as well as cleaning up category subpages. I would also support moving "Mechanics/Redstone" to "Redstone mechanics" since the mechanics page itself is a redirect to a different page. Regarding some of the suggestions by Humiebee, I am neutral on moving Tutorials pages to a separate namespace (assuming that it's searchable like the MCD and MCE namespaces), but disagree with making a namespace for "X/Mechanics" pages as they are similar to regular articles, just more technical. –Sonicwave ^talk 20:08, 24 August 2020 (UTC)

Ok, I agree on pretty much your whole statement above including the gallery subpage idea but but I think the Mechanics should possibly go into Tutorials:Mechanics/whatever.---Humiebee^{Discuss anything with me Look at my edits} 20:15, 24 August 2020 (UTC)

I dont know, if mechanics are (not) tutorials, but I have no problem with that. So I am Supporting this idea.–Preceding unsigned comment was added by TreeIsLife (talk • contribs) at 20:50, 24 August 2020 (UTC). Please sign your posts with ~~~~

I mean it is teaching you the mechanics of whatever so that Would make sense.---Humiebee^{Discuss anything with me Look at my edits} 22:47, 24 August 2020 (UTC)

I don't think you make strong enough case for not using subpages, especially so for mechanics and tutorials pages. For example, you brought up the past dispute regarding the names of mechanics pages, but the fact that the dispute was had and solved, and the community arrived at a solution, is an argument in favour of keeping the current page hierarchy, if anything. I'm fine with the other suggestions but mechanics and tutorials subpages work fine without issues. Blue Banana whotookthisname (talk) 07:16, 25 August 2020 (UTC)

Many of the Tutorials subpages are ignored by the Minecraft Wiki's most active editors. ~~Special:Random~~ The "Random page" link never links to subpages. If the tutorials were moved to a new content namespace, they wouldn't be subpages and therefore be accessible from the Random page link and more likely for editors to notice. Fadyblok240 (talk) 02:09, 27 August 2020 (UTC)

Fadyblok240 Special:Random does not link to anything besides mainspace so that's.......---Humiebee^{Discuss anything with me Look at my edits} 02:24, 27 August 2020 (UTC)

The "Random page" link does link to other namespaces, namely Minecraft Earth and Minecraft Dungeons. If a Tutorials namespace were created, the wiki manager could classify it as a content namespace. Ironically, Special:Random also links to subpages, although the "Random page" link does not. I tested this after the migration to UCP and I still couldn't get to a subpage by using the "Random page" link on the sidebar. Fadyblok240 (talk) 02:40, 27 August 2020 (UTC)

This is because the Random page link in the sidebar uses Special:RandomRootpage instead. – Unavailablehoax (talk) 21:55, 15 October 2020 (UTC)

It was probably configured like that to bypass non-article pages that are subpages of articles, but there are also legitimate articles that are subpages. Maybe we should move article subpages to root pages or allow the random page link to access subpages and move non-article subpages of articles to other namespaces. Fadyblok240 (talk) 20:20, 7 November 2020 (UTC)

Ditto Sonicwave and Humiebee for the most part, don't have a whole lot to add. I'd also add history-esque subpages to the list of "acceptable" subpages, there's not really a better place for most of these and it keeps them tied to their parent pages really nicely. While yes the current version of a main article body should always reflect the current version (and only the current version), the wiki should still hold all the information on old versions of features. Usually a good history section can get the job done, but oftentimes the changes are too vast and/or complicated to be fully represented there (for example, loot table reworks, old villagers, etc). -PancakeIdentity (talk) 17:41, 27 August 2020 (UTC)

See Minecraft Wiki talk:Community portal/Archive 26#Should we move all Tutorials pages to a own namespace? for further info about moving tutorials to a new namespace. Fadyblok240 (talk) 00:22, 18 September 2020 (UTC)

Should you open up a new discussion about this? I would like a new tutorials namespace, supporing Psl85 and User-12316399 ideas.---Humiebee^{Discuss anything with me Look at my edits} 01:19, 18 September 2020 (UTC)

Here is a quote

“	If we move the pages to a new namespace, we could make in the LocalSettings.php so these could show up by default in the search bar.	„
	— User:Psl85

---Humiebee^{Discuss anything with me Look at my edits} 01:25, 18 September 2020 (UTC)

And Another one

“	The aim of the mainspace is for information on the game (and, by extension, Mojang) to be documented. Tutorials do not fall within the scope of what the mainspace should document, and as such should not be kept in the same namespace. It's also worth noting that other Gamepedia wikis such as the Terraria Wiki already have namespaces dedicated to tutorials.	„
	— User-12316399

All in all, the opposes are not very convincing but the supports are, should I reopej the discussion?---Humiebee^{Discuss anything with me Look at my edits} 01:27, 18 September 2020 (UTC)

Bot noticeboard?

I know this sounds really dumb but I kind of want like a page, similar to the Minecraft Wiki:Admin noticeboard that people can post on that requests something that a bot would do such as fixing links due to UCP. Maybe is should be called something else but idk what. Link????Minecraft Wiki:Bot noticeboard---Humiebee^{Discuss anything with me Look at my edits} 20:29, 26 August 2020 (UTC)

I'm kind of skeptical. The Russian wiki has made one long ago. Now it's unused. Completely. The last 3 edits were in 2016, 2017, and one IP request about a month ago. --AttemptToCallNil (report bug, view backtrace) 20:40, 26 August 2020 (UTC)

Is there a link?---Humiebee^{Discuss anything with me Look at my edits} 20:40, 26 August 2020 (UTC)

ru:MCW:Запросы к ботоводам. --AttemptToCallNil (report bug, view backtrace) 21:07, 26 August 2020 (UTC)

Oh... ever since 2016, it's been unused??---Humiebee^{Discuss anything with me Look at my edits} 21:17, 26 August 2020 (UTC)

It seemed to be pretty active at 2014 but for some reason, it completely died down..---Humiebee^{Discuss anything with me Look at my edits} 21:18, 26 August 2020 (UTC)

Thanks!---Humiebee^{Discuss anything with me Look at my edits} 21:16, 26 August 2020 (UTC)

Weak support Wikipedia has a similar page named Wikipedia:WP:Bot requests but on the Minecraft Wiki there are not that many bots, so maybe the Bot Noticeboard doesn't warrant its own page, but should be a section of subpage of the Admin Noticeboard or linked directly on the sidebar. Fadyblok240 (talk) 20:46, 26 August 2020 (UTC)

I don't think it should be in the sidebar but I do Agree on it to be a subpage/subsection of the admin noticeboard.---Humiebee^{Discuss anything with me Look at my edits} 20:49, 26 August 2020 (UTC)

I would Support a small section dedicated for this. Although I feel like the community portal would a better place for this than the admin noticeboard, as bot edits aren't necessarily for admins. — Thomanski | t | c | 21:55, 26 August 2020 (UTC)

Though bots rights are only given to bots of trusted users so I have some mixed opinions---Humiebee^{Discuss anything with me Look at my edits} 21:56, 26 August 2020 (UTC)

It's not super hard to be considered a trusted user if you're somewhat active and consistently constructive. Also, bots don't really have many different rights than normal user accounts, it's more to do with reducing spam and stuff. -PancakeIdentity (talk) 21:53, 27 August 2020 (UTC)

Weak oppose. Don't really see a need honestly. In my time here, I've only seen a few users ask for a bot to do something for them that they couldn't/didn't want to do themselves. And in these few instances, they were easily fulfilled through discord or this CP. -PancakeIdentity (talk) 17:34, 27 August 2020 (UTC)

Closing and merging projects

Well. Currently, we have many, many, many active Wiki Projects in Minecraft Wiki:Projects. But many of them are duplicate, non-useful and others, which idk, how someone could create it.

So here's complete list of active projects, excluding language ones

Welcome
Screenshot Minecraft Versions
Beginner's Guide Rewrite
Minecraft in schools
Screenshot Fixing
Rewrite for Style
Version cleanup
Tutorials Modernization
Userboxes standardization
Redirect cleanup
Renaming
Cleanup open tags
Capitalization Fixing
Individual Biome Pages
Upload Missing Wiki Sounds
Refactoring edition specific information
Minecraft Earth Wiki
Texture Documentation Cleanup
Gallery organization
Wiki videos
Minecraft: Story Mode Mobs

21 pages, with some of them could be deleted.

So i start with my ideas

Fandom has automatic Messages from some MediaWiki page. Also i don't see anybody adding {{Welcome}} template, so I consider Closing it.
Should be merged with Screenshot fixing
Keep it
Better merging with Minecraft in Education
Should be merged with Screenshot Minecraft Versions
Keep it but, compleate it.
Keep it
Ok, Keep it
Keep it
No activity, it's in dead point from it's creation, consider removing it
It is compleated, we should archive that
Keeping it
Keeping it
Happy to see it will be done (one time), so keep it
It is compleated, so archive
Keeping longer for discuss
Archive
Keep
This is not most useful project, so discussion
Keep that
Keep it, but i notice that's outdated.

--TreeIsLife (talk) 20:54, 26 August 2020 (UTC)

I have some opinions as well.

Somewhat Agree, Madminecrafter12 is the only user to even remotely work on it, completly unused though the template should still remain as the template, not the project is still used.
Agree
Agree
Agree
Agree
Merge, would be better to merge with capitalization fixing.
Agree
Agree
Agree
Disagree, don't bomb it, improve it.
Agree
Agree
Merge with Rewrite for Style
Agree
Agree
Agree
Agree
Agree
Don't really agree/disagree there's still a discussion with like 90% support and so more discussion is not really needed
Agree
Disagree Story mode is discontinued so since less people have it, I don't think it's worth the effort so Bomb it---Humiebee^{Discuss anything with me Look at my edits} 21:15, 26 August 2020 (UTC)

I think Rewrite for Style and Capitalization Fixing should be merged. Fadyblok240 (talk) 16:57, 27 August 2020 (UTC)

Mostly agree with your conclusions. At this point, I'm not sure we need #16 anymore, we only deal with two editions. We're not perfect in how we document them yet but I'm not sure if need a project, especially as it never really had much discussion on what to do. Also, just wanted to check, the Earth Wiki project has no relevance now that it has its own namespace, correct? -PancakeIdentity (talk) 17:32, 27 August 2020 (UTC)

The Minecraft Earth Wiki project is still relevant, as many of the articles in that wiki's namespace are stubs. Fadyblok240 (talk) 09:43, 31 August 2020 (UTC)

Also, we should reclassify some projects as semi-active, as the Minecraft Wiki is never complete. I have added a handy template called {{project status}} that categorizes projects by activity. The cleanup open tags project has turned into a white elephant project. Fadyblok240 (talk) 02:16, 19 September 2020 (UTC)

Documentation template revamp

Can somebody add links to "/sandbox" and "/testcases" subpages of templates to the Template:Documentation template? Fadyblok240 (talk) 19:08, 28 August 2020 (UTC)

Why? --TreeIsLife (talk) 22:39, 9 September 2020 (UTC)

I (along with Humiebee) have created several template sandboxes, but the documentation template does not recognize that they are template sandboxes and shows that they have no documentation; they appear in Category:Templates with no documentation instead of Category:Template sandboxes. Fadyblok240 (talk) 22:32, 26 September 2020 (UTC)

I don't see the need for those pages, they'd just become outdated and useless quickly. Just use the Template:Sandbox or your own user subpage instead. Nixinova T C 02:10, 27 September 2020 (UTC)

Template sandbox subpages would be useful for implementing major changes to high-risk templates with complex code or many parameters, where the "show preview" button alone would not guarantee whether the template is free of errors. Fadyblok240 (talk) 03:31, 5 October 2020 (UTC)

Okay, and what stops you from doing that on your own page or as a subpage on the sandbox, instead of creating additional maintenance for all templates? Very few templates are both high traffic enough that a major change is wiki breaking and get enough changes to warrant a permanent sandbox page. Likewise, {{BatchTest}} can handle doing test cases by comparing actual uses of the template to a sandboxed version.

I get that other wikis like Wikipedia do this, we don't have nearly the editing traffic they do so we don't have to adopt such complicated systems to make templates easy to maintain.–KnightMiner · (t) 04:02, 5 October 2020 (UTC)

Move the Greek and Turkish Wiki back into translation projects

Why? Well for starters, Grid Files, the vast majority of them are used exclusively by the turkish wiki, also for both wiki, they have inactive admins. Another thing is that the amount of contributions to the wiki is miniscule. All I see is User:Fusion thermonucleaire, who is technically a bot, who puts interwiki links, User:Thomanski, who uploads files and thats pretty much it, for the Greek Wiki, it's main page is not even 100% translated and again, completely inactive.

A Summary

Both have no active admin (Greek admin edits once a year, turkish admin hasn't edited since 2017)
Both have no active real contributers (Greek wiki is slightly more active then Turkish, still, 80% of edits are by Fusion thermonucleaire)
The Greek Wiki does not even have a 100% translated main page
The Turkish wiki uses grid files and would ease the hassle of removing them.
Those are my reasons
---Humiebee^{Discuss anything with me Look at my edits} 17:39, 4 September 2020 (UTC)

Comment, the reason why I upload files to those interwikis is to remove their dependency of the English wiki so we can finally remove the grid files here. I honestly don't know what to do with these wikis though. I don't think straight up deleting them is a good idea (for people that don't understand English), but on the other hand, these interwikis are REALLY outdated and inaccurate information is never a good thing for a wiki. — Thomanski | t | c | 21:45, 4 September 2020 (UTC)

Yeah, but like putting it into a translation project isn't harmful.---Humiebee^{Discuss anything with me Look at my edits} 22:01, 4 September 2020 (UTC)

Hate to say it, but, Strong support moving back to translation projects, as their state is actually harmfull to the readers (false/outdated info everywhere, and only partially translated) and only hinders changes on the english wiki due to the dependency. FVbico (talk) 22:04, 4 September 2020 (UTC)

~~I think it has to do with the Cyprus dispute~~ Fadyblok240 (talk) 00:36, 5 September 2020 (UTC)

What does this have anything to do with the discussion?---Humiebee^{Discuss anything with me Look at my edits} 00:42, 5 September 2020 (UTC)

Weak oppose - why can't we just delete the untranslated pages instead, and add dedicated "this info is disgustingly outdated" templates to it instead? I wouldn't be against just getting rid of the wikis entirely either given the lack of interest. - User-12316399 (talk) 00:40, 5 September 2020 (UTC)

Comment Yes, because whats the point about having a wiki page translated in multiple languages and the translated pages not even be finished and be forgotten about. I would consider it wiki clutter. So unless someone takes the time out of their day to rework all these translated pages, i think it's best to just axe em'. James Haydon (talk) 04:05, 5 September 2020 (UTC)

Strong support doing something about these translations, the Greek wiki is just a complete import of the English one, issues pages and all (this should never be how translations are done), so everything is 3+ years outdated and clutters maintenance on this wiki. Add to that the fact that, since the wiki is in English, its a target for spammers who won't be reverted like they are here. E.g.: el:Alpha 1.2.4: there's no'one other than English wiki users to revert them. I can barely find many pages that have actually been translated apart from like a disambig, though there is el:Κρύσταλλος_του_Ender, el:Βιβλίο και Πένα, el:Κύβοι Διαμαντιού‏‎, el:Μπλοκ‏‎, but that's it. I'll just import all of the translated pages back here so they're safe if we feel like nuking that wiki. Nixinova T C 20:20, 5 September 2020 (UTC)

There: Special:Prefixindex/MCW:Projects/Greek translation/ – that's literally all the translated Greek pages. The wiki can be safely nuked now if that's decided. Nixinova T C 20:34, 5 September 2020 (UTC)

What about the turkish wiki?---Humiebee^{Discuss anything with me Look at my edits} 22:53, 5 September 2020 (UTC)

Strong support for the Greek wiki, mainly because so many pages are untranslated (which kinda defeats the purpose of a traduction). Weak support for the Turkish wiki, mainly because of the inactivity. Sagessylu (discuss | edits) 17:37, 6 September 2020 (UTC)

Sagessylu, the Greek wiki is already translated.---Humiebee^{Discuss anything with me Look at my edits} 20:55, 6 September 2020 (UTC)

Done by Nixinova Greek wiki only---Humiebee^{Discuss anything with me Look at my edits} 20:55, 6 September 2020 (UTC)

Well, not really, I've just moved a couple to this wiki, el: still exists. Nixinova T C 01:33, 7 September 2020 (UTC)

okay ill wait and see if someone will actually finish them now that there back in the works. James Haydon (talk) 00:50, 7 September 2020 (UTC)

I'm worried about the Ukrainian wiki potentially suffering from the same fate. It's also on the brink of dying out. There is one local user who appears to have edited in the last few days, but aside from that, there are predominantly edits by users from other wikis, notably Mak_and_Iv (a Russian admin) who is also an admin on the Ukrainian wiki. — Babylon AS *Happy Camper* 12:20, 30 September 2020 (UTC)

The thai wiki also only has like 1 contributer who keeps it alive and from anarchy as well but aside from that, it could die as well. – Preceding unsigned comment was added by Humiebee (talk • contribs) at 21:22, 3 November 2020 (UTC). Please sign your posts with ~~~~

Replace /ED, etc, subpages with DPL section transclusion

TIL that DPL can be used for labelled section transclusion: {{#dpl:title=Furnace|include=#Block entity}}. This can replace having /ED, /BE, etc subpages. Nixinova T C 22:47, 5 September 2020 (UTC)

Changing it might break some nbt inherit templates though. FVbico (talk) 20:58, 6 September 2020 (UTC)

What about change it to only certain templates where it won't break?---Humiebee^{Discuss anything with me Look at my edits} 20:59, 6 September 2020 (UTC)

Oh, LST finally works now? I believe there could be a workaround for NBT pages, but if it can be easily done with non-NBT data, then I am all for it. — Babylon AS *Happy Camper* 07:23, 24 September 2020 (UTC)

Converting .ogg files to .mp3 and .wav

Given that .ogg files aren't supported on mobile, maybe we should convert all .ogg files into .mp3 (Music samples) and .wav (sounds) files with software like Audacity. One user at Terraria wiki did this to Terraria: Otherworld tracks, wich were .ogg files. --Superwill771 (talk) 15:55, 8 September 2020 (UTC)

Oppose There will be much much work. Only if you want to do converting and uploads, then, i am Neutral --TreeIsLife (talk) 16:04, 8 September 2020 (UTC)

Umm... for me, the sounds on skeleton#Sounds, which are ogg sounds, work fine on mobile. FVbico (talk) 16:12, 8 September 2020 (UTC)

Probably (as I understood from discussion) meant on mobiles with mobile view. But even there, it is working. --TreeIsLife (talk) 16:24, 8 September 2020 (UTC)

I use Duckduckgo on an ipad with desktop view and they don't work.--Superwill771 (talk) 16:36, 8 September 2020 (UTC)

Well, it can be problem with iPads/iPhones. Duckduckgo is search engine. --TreeIsLife (talk) 16:40, 8 September 2020 (UTC)

Ogg sounds are not supported in Safari browsers. --AttemptToCallNil (report bug, view backtrace) 17:49, 8 September 2020 (UTC)

Duckduckgo is also a browser app on iOS/Android. I don't know if they meant that. — Thomanski | t | c | 19:38, 8 September 2020 (UTC)

Half-Support. For the above reasons that some devices don't support these ogg files, I support. However, looking at User:TreeIsLife,'s argument it is a lot of work, I say go ahead and do that, I don't see it as a bad thing. Good luck on that. Blockofnetherite ^{Talk Contributions} 18:05, 8 September 2020 (UTC)

Changed to full support for below reasons. Blockofnetherite ^{Talk Contributions} 21:22, 9 September 2020 (UTC)

Support, this wiki is about work, I use safari and it fails completely, the terraia wiki example is good.---Humiebee^{Discuss anything with me Look at my edits} 19:26, 8 September 2020 (UTC)

Weak support for conversion to MP3, definitely not WAV. See my explanation on Terraria Wiki. --AttemptToCallNil (report bug, view backtrace) 19:38, 8 September 2020 (UTC)

So your saying we could use FLAC?---Humiebee^{Discuss anything with me Look at my edits} 19:41, 8 September 2020 (UTC)

It looks possible, but I don't think this was actually done on the wiki before. --AttemptToCallNil (report bug, view backtrace) 20:05, 8 September 2020 (UTC)

Support, but I'm not gonna do it. — Thomanski | t | c | 19:39, 8 September 2020 (UTC)

Strong oppose. Just because ogg isn't supported on some mobile devices now, doesn't mean it won't be later, given that it's a license-free open-source thing. Firefox and Chrome already support ogg. I note that the VLC player supports ogg on all mobile devices. And I believe the Opera browser does also, which is also available on any mobile device. ~ Amatulic (talk) 16:28, 9 September 2020 (UTC)

why strong oppose TheGreatSpring (talk) 07:56, 22 September 2020 (UTC)

As a matter of principle, I strongly oppose creating unnecessary time-wasting busy-work, which is basically what is being proposed. Ogg is playable on all desktop browsers and on all mobile devices using VLC. By the time all the work has been done to convert ogg to mp3, mobile browsers will likely be supporting it anyway. ~ Amatulic (talk) 21:13, 22 September 2020 (UTC)

Weak support as a temporary measure until the majority of affected devices end up supporting playback. - User-12316399 (talk) 17:11, 9 September 2020 (UTC)

Neutral. I definitely don't like mp3 because it's not lossless, and I think this wiki supposedly being a source of information should present that information without losses. I see the issues with wav and ogg as well, though. What other possibilities are there? Blue Banana whotookthisname (talk) 07:39, 21 September 2020 (UTC)

Well, the sounds and music are stored in Minecraft as Ogg files in the first place, so if data integrity is a concern, they should be used and uploaded directly, which was already done. (For music files, it’s possible to cut the file to 30 seconds without re-encoding it — FFmpeg does allow that, not so sure about Audacity.) — Babylon AS *Happy Camper* 15:09, 24 September 2020 (UTC)

~~Weak support~~ TheGreatSpring (talk) 07:56, 22 September 2020 (UTC)

Oppose — Transcoding Ogg Vorbis (one lossy format) to MP3 (another lossy format, with worse quality by the way) isn't good practice in general, and using WAV will lead to much larger files. Safari not supporting Ogg is Apple's fault, and VLC is also available (if I recall correctly™) on iOS/macOS as well. As for royalty free, this advantage of Ogg is no longer relevant now, as all patents on MP3 have already expired, however Ogg Vorbis is still superior quality-wise (as in, Ogg file will sound better than an MP3 of identical size). It doesn't seem to be worth the effort. — Babylon AS *Happy Camper* 07:19, 24 September 2020 (UTC)

I now Oppose the idea TheGreatSpring (talk) 12:56, 24 September 2020 (UTC)

Weak Oppose. I don't really have any original arguments, just see the opposing arguments above. I especially wouldn't like MP3 if it is indeed more lossy than Ogg. It seems like a lot of work and I know how long it can take us to do these sorts of tasks. -PancakeIdentity (talk) 19:13, 24 September 2020 (UTC)

Changed to Weak support for above reasons, still think it should be done. I am Weak oppose for mp3, Support for wav and Weak oppose due to the amount of time and effort it woult cause.---Humiebee^{Discuss anything with me Look at my edits} 16:08, 17 October 2020 (UTC)

Comment - Doesn't Wikipedia have a web player or something? I'm able to play Ogg Vorbis sounds in Wikipedia while using Safari. – Unavailablehoax (talk) 16:30, 17 October 2020 (UTC)

I'm pretty sure that is .ogv, not .ogg and it's basically adding up .gif and .(a music file that is available in all search engines as well as not being lossy)---Humiebee^{Discuss anything with me Look at my edits} 21:42, 28 October 2020 (UTC)

What makes you think it's a video? Here an example sound file from Wikipedia, which is in Ogg Vorbis and can be played in Safari. – Unavailablehoax (talk) 22:12, 28 October 2020 (UTC)

.ogv is just an extension, the base format is still the same (well, then you’d usually have Theora video together with Vorbis audio). As far as I know Wikipedia uses a different extension for media playback, which might in fact handle audio files somewhat differently. — Babylon AS 10:36, 29 October 2020 (UTC)

The Skeleton Horseman problem, and how should we fix it?

Recently, Skeleton Horseman has had its link changed from Skeleton Horse#Skeleton trap to MCD:Skeleton Horseman. Two major problems emerged from doing so:

Many "Skeleton Horseman" links of the Minecraft jockey-like mob suddenly redirected into a Minecraft Dungeons mob. This created problems for the Minecraft topic section of the Skeleton (disambiguation) page.
At least two templates, Template:EntitySprite and Template:EntityLink's id is "skeleton-horseman", not "skeleton-trap".

Is it called a skeleton trap, a skeleton jockey, or a skeleton horseman? This change of redirect of the [[Skeleton Horseman]] page has caused some confusion for me.
Blockofnetherite ^{Talk Contributions} 20:33, 8 September 2020 (UTC)

Ok, try do to your best and fix it, i have no other argument, so I am Supporting. --TreeIsLife (talk) 20:40, 8 September 2020 (UTC)

Comment Thanks for the support, but I currently don't want to fix it yet, as I still don't exactly know how to fix it, nor do I know how to change those two templates which use the id "skeleton-horseman". @Humiebee very recently undid @Fadyblok240 's edit, but it's not over. Blockofnetherite ^{Talk Contributions} 20:44, 8 September 2020 (UTC)

To avoid confusion, I added the {{redirect}} template.---Humiebee^{Discuss anything with me Look at my edits} 20:46, 8 September 2020 (UTC)

It should be redirected back to skeleton trap with a hatnote ({{for}}) added to the top of the section. Vanilla should always take priority. Nixinova T C 20:41, 8 September 2020 (UTC)

Comment What about the templates? Blockofnetherite ^{Talk Contributions} 20:47, 8 September 2020 (UTC)

Done, but with {{redirect}} instead---Humiebee^{Discuss anything with me Look at my edits} 20:43, 8 September 2020 (UTC)

Now that this issue is fixed, there are still questions remaining.

It seems that "skeleton trap" and "skeleton horseman" have been used interchangeably. In the Skeleton Horse page, where skeleton traps/horsemen are described, they call them skeleton traps. However, the {{EntitySprite}} and {{EntityLink}} templates use the id: "skeleton-horseman". So what are they, skeleton traps, skeleton horsemen, or skeleton/skeleton horse jockeys? What should we do, keep them as interchangeable terms, or merge into one?
Blockofnetherite ^{Talk Contributions} 16:15, 9 September 2020 (UTC)

Add shorthand Namespaces for certain things

Now there are shortened namespaces such as MCD:Zombie or MCE:Muddy Pig but others such as Templates don't have one. All namespaces except for main (obviously) should have an abbreviation.
Already Existing

MCW (Minecraft Wiki)
MCT (Minecraft Wiki talk)
MCE (Minecraft Earth)
MCD (Minecraft Dungeons)

Not Sure if exists

Minecraft Dungeons talk or Minecraft Earth talk
My proposals would be MDT and MET respectively

Does not exist, definitely want

TP for Template
TPT for Template talk
~~MW for MediaWiki~~ - Automaticly redirects to mediawiki.org, so that's impossible to add.
New Proposal for MediaWiki. MDW for MediaWiki.
MWT for MediaWiki talk
CAT for Category
CTT for Category talk
M or MOD for Module
MT or MDT for Module talk

If this gets implemented, want for consistancy

T for talk
U for User
UT for User talk
F for File
FT for File talk
H for Help
HT for Help talk
W for Widget (didn't even know this existed)
WT for Widget talk
S or SP for Special Page
UP for UserProfile

Ones that I really just don't want or need but it would br nice for consistancy

G(T) or GAD(T) for Gadget (talk)
GD(T) for Gadget definition (talk)

---Humiebee^{Discuss anything with me Look at my edits} 20:09, 11 September 2020 (UTC)

Not sure these should all be created, but I can definitely make a template that does this. Nixinova T C 20:10, 11 September 2020 (UTC)

I think, their existence wouldn't harm the wiki. FVbico (talk) 20:18, 11 September 2020 (UTC)

How do tou create a template for namespaces?---Humiebee^{Discuss anything with me Look at my edits} 20:21, 11 September 2020 (UTC)

Not for the namespaces themselves, but for linking to them. That wouldn't affect searching, however, but I could also make a script that does this for individuals. Nixinova T C 20:29, 11 September 2020 (UTC)

I would love the script as I search for templates a lot and it's annoying when I misspell it as trmplate (r is on the way from t to e so yeah), where would the script go, common.js?---Humiebee^{Discuss anything with me Look at my edits} 20:32, 11 September 2020 (UTC)

Yes, common.js, try adding mw.loader.load('/index.php?title=User:Nixinova/namespace-shortcuts.js&action=raw&ctype=text/javascript'); to yours to test my new script. Nixinova T C 20:49, 11 September 2020 (UTC)

Oh, ok, thank you, can you delete the test page I made and it's documentation?---Humiebee^{Discuss anything with me Look at my edits} 20:51, 11 September 2020 (UTC)

Why does it go to like the search then the desired page, nothing of a big deal though, is it a limitation or is it diffucult to change that?---Humiebee^{Discuss anything with me Look at my edits} 21:29, 11 September 2020 (UTC)

Fixed. Nixinova T C 21:45, 11 September 2020 (UTC)

I think it broke again.... I searched UT:Nixinova and it didn't work..., thanks for everything!---Humiebee^{Discuss anything with me Look at my edits} 21:55, 11 September 2020 (UTC)

Fixed as well. Take further reports to User talk:Nixinova/namespace-shortcuts.js. Nixinova T C 22:07, 11 September 2020 (UTC)

(edit conflict) I think they could be implemented into shortcut redirects, but implementing them as aliases would require modifying the wiki software. Also, I prefer CAT: over C: for categories. Fadyblok240 (talk) 20:34, 11 September 2020 (UTC)

Changed---Humiebee^{Discuss anything with me Look at my edits} 20:39, 11 September 2020 (UTC)

I don't see the point of most of these, they would add confusion since most other wikis don't have these abbreviations. The only ones that I support are Minecraft Dungeons/Earth talk since these are more of a handful to type out, and are more likely to be linked to (as opposed to the MediaWiki namespaces, for example). –Sonicwave ^talk 22:14, 11 September 2020 (UTC)

I agree with you, especially about the talk pages of non-article pages except for the Minecraft Wiki: namespace. Even Wikipedia doesn't have alias for most types of talk pages. Fadyblok240 (talk) 22:52, 11 September 2020 (UTC)

Oppose changing, except MDT and MET. Sry, but shortcuts are SHORT-CUTS. So it is for shorter things, and for things, which won't get confused. This means, it is for project talks or ns with more then 8 characters. And MediaWiki, NO! I don't know, how it will work, but MediaWiki shouldn't be shortcutted in any way! I don't want, that users will easily get to MediaWiki ns. Also, special pages,... No! --TreeIsLife (talk) 17:43, 12 September 2020 (UTC)

Why oppose special pages and templates? You gave no reason for special pages and templates have more than 8 characters and I use them as search terms a lot---Humiebee^{Discuss anything with me Look at my edits} 22:12, 12 September 2020 (UTC)

Done with {{sl}} and example U:Nixinova/namespace-shortcuts.js of course by Nixinova. ~~The only issue is that it shows in S:WantedPages~~---Humiebee^{Discuss anything with me Look at my edits} 20:10, 12 September 2020 (UTC)

I'll fix the wanted pages thing, however these still don't go towards making universal namespace shortcuts. Nixinova T C 20:12, 12 September 2020 (UTC)

Wait actually you just have to do {{sl}}, does it still come up in S:WantedPages?---Humiebee^{Discuss anything with me Look at my edits} 20:29, 12 September 2020 (UTC)

Well, with {{sl}}, i'm not oppose, i only was scared, if many users, which want to browse wiki content will see MediaWiki:Hydra.css by just MDW or other things, which are not wiki content.--TreeIsLife (talk) 19:51, 13 September 2020 (UTC)

Why would they type media wiki in the first place? You would type the shortcut if you knew the destanation and as for {{sl}}, if they saw the link and pressed it, they would just press the back button (an example of this "back button" sense is TP:Disambiguation.---Humiebee^{Discuss anything with me Look at my edits} 20:47, 13 September 2020 (UTC)

This is already partially implemented with {{sl}}, however, for this to be 100% implemented, U:Nixinova/namespace-shortcuts.js would have to be implemented to MediaWiki:common.js, however, tjis will need a consensus. There still has not been a clear answer but it seems like User:Nixinova is support and User:TreeIsLife is Oppose. Any thoughts or clear opinions?---Humiebee^{Discuss anything with me Look at my edits} 20:52, 13 September 2020 (UTC)

Oppose for most talk namespaces and site-wide automatic implementation. Even Wikipedia doesn't use shortcuts for most namespaces. We should use shortcuts on a page-by-page basis, meaning we can abbreviate the page name, not just the namespace. Fadyblok240 (talk) 22:45, 13 September 2020 (UTC)

Comment Putting shortcuts on pages? There are so much more pages then shortcuts, I don't get why your proposing this and your only reason for opposition was

“	Even Wikipedia doesn't use shortcuts for most namespaces.	„
	— U:Fadyblok240

do you have any more opposition reasons? I mean the shortcut for searching substitutes it, not like normal Ex:If i'm searching MCT:CP, MCT doesn't turn into Minecraft Wiki talk:whatever page, it keeps it but this commons.js thing does this, T:Golden Apple->Talk:Golden Apple. Again, it's helpful and I don't see anything wrong, it's nice and convenient, also you have to put T: (colon) so it won't affect normal searching---Humiebee^{Discuss anything with me Look at my edits} 00:19, 14 September 2020 (UTC)

Support as this is a quality of life change that assists editors and viewers. I really don't see any real problems, and no technical issues as of what I know. Blockofnetherite ^{Talk Contributions} 00:14, 15 September 2020 (UTC)

I am still Oppose about this idea. This is bad idea with auto redirect. Yes, even Wikipedia has no "shortcut ns". What you see like WP:R is basicly an article with redirect. Sry, but not everything is good. --TreeIsLife (talk) 18:04, 15 September 2020 (UTC)

Support per above reasons. TheGreatSpring (talk) 10:32, 18 September 2020 (UTC)

Oppose most shortcuts. A single letter namespace name is hard to read and can be confusing for new users, all for the gain of you typing 5 less letters. I don't see much point to that. For long namespaces such as Minecraft Wiki or Minecraft Dungeons (and cooresponding talk pages) I agree, but for short ones like Talk or Template, you are gaining a ton of confusion in favor of typing 6 less letters. (is T:Minecraft a talk page, or a template?). Plus, many of these rarely get links, such as widgets, MediaWiki, and Help. Template is also rarely linked directly, the template syntax automatically handles it. KnightMiner ^(t/c) 17:27, 10 November 2020 (UTC)

New proposal

It looks like the most support is headed towards implement for only MET and MDT and the others are not really nessicary, so would you support just

Only MDT and MET
MD, ME, MDT, MET
Everything on my definitely list (+ MD and ME)
Everything except Gadget, Widget, and their talk and definition variants.
Everything

I feel like MD and ME could also be helpful (so that is why I added it to the list)---Humiebee^{Discuss anything with me Look at my edits} 22:37, 19 September 2020 (UTC)

Option 1 and CAT: for Category:, H: for Help:, and T: for Template: instead of Talk: Fadyblok240 (talk) 23:37, 19 September 2020 (UTC)

Option 1 and that's it! This is not Project NS or talks, so there is no need to do other shortcuts. --TreeIsLife (talk) 11:41, 24 September 2020 (UTC)

Certainly Option 1 at least. I dislike the idea of CAT shortening (suggested by Fadyblok) because no category uses short names like Minecraft Wiki pages or even some templates do. Help shortening does seem to be helpful, the same may apply for templates, and if both these get shortcuts, then their talk pages should probably have them as well (HT and TT). But implementing shortcuts for all namespaces just for the sake of it is certainly not worth the effort.

As I said before, I don't support most namespace aliases (including CAT:); I only support them as pseudo-namespace redirects for some pages. Also, I would rather have W: point to Wikipedia pages than to Widget pages. Fadyblok240 (talk) 01:12, 22 November 2020 (UTC)

On a side note, why exactly MDT and MET? The respective article namespaces are abbreviated MCD and MCE. Unless such shortenings are limited to three letters for some reason, I’d suggest using MCDT and MCET respectively for the sake of consistency (though, we already have MCT for Minecraft Wiki talk...). — Babylon AS *Happy Camper* 06:27, 25 September 2020 (UTC)

For consistancy that is (all namespaces has 3 letter) and yes, it would be consistant with MCT (it's not MCWT))---Humiebee^{Discuss anything with me Look at my edits} 14:11, 26 September 2020 (UTC)

Option 1 TheGreatSpring (talk) 06:58, 25 September 2020 (UTC)

Still staying with Everything per my above reason. Just don't see anything wrong with this addition, saving characters is useful. Blockofnetherite ^{Talk Contributions} 19:31, 1 October 2020 (UTC)

Keep in mind that some of the proposed namespace shortcuts conflict with potential interlanguage links, such as ga: for Gadget and Irish (which doesn't make any sense since pages in the Gadget namespace, if any, cannot be accessed directly from the search bar) and tl: for Talk and Tagalog (which somewhat offends me since I am an ethnic Filipino). Another reason to Oppose. Fadyblok240 (talk) 23:43, 23 October 2020 (UTC)

Okay, I don't think we need Gadget, Widget, or MediaWiki, because we shouldn't make it easier to see MediaWiki pages, as they contain information (like blocked words/website links on the inappropriate filter). Gadget and Widget are not so necessary. Talk is proposed to be short for T and not Tl. Still Supporting MDT, MET, TP, TPT, CAT, CTT, MOD, MDT, T, U, UT, F, FT, H, HT, S and SP, and UP. Blockofnetherite ^{Talk Contributions} 18:10, 6 November 2020 (UTC)

See WP:Perennial_proposals#Create shortcut namespace aliases for various namespaces for why this was rejected in Wikipedia and probably the Minecraft Wiki. Fadyblok240 (talk) 04:05, 10 November 2020 (UTC)

I Oppose the addition of a "T:" namespace, as "T" could stand for either "talk" or "template", and because of this, such a namespace would be more confusing than helpful. I Oppose the "M:" namespace for the same reason, as "M" could stand for either "module" or "MediaWiki". I also Oppose the "GA:" namespace as it would conflict with interwiki links. I Support "MDT:" and "MET:", as the main Dungeons and Earth namespaces already have shortcuts, so the addition of shortcuts to their talk namespaces would create consistency. I'm Neutral about the rest, as whilst I can't see much harm in adding them, I'm unsure whether they would be particularly helpful, either. GrogTheGreatEvilGoblinWarlord (talk) 06:00, 11 November 2020 (UTC)

Add sort keys for version exclusive articles (including articles about versions themselves)

I think it would benefit to add sort keys to remove prefixes from version exclusive articles. (e.g. the sort key for Java Edition level format would be Level format) It would provide a better ordering of lists of pages in version exclusive categories. Fadyblok240 (talk) 21:10, 12 September 2020 (UTC)

Go ahead, this should be an uncontroversial change. Nixinova T C 22:10, 12 September 2020 (UTC)

It may take a long time to add all the sort keys for the version articles. Maybe consider modifying or creating templates (see Template:Version nav/sandbox) to automatically create the sort key? Meanwhile, I will add sort keys for articles that are not about versions. Fadyblok240 (talk) 22:21, 12 September 2020 (UTC)

Change the main discussion from MCT:CP to MCW:Centralized discussion

This is a very big change proposal but I have some reasons to back it up.

This page should be used for discussing the Community Portal itself
The ftb wiki does this as well
It could be linked on the sidebar (as centralized discussion)
How did this name start anyways?
There is not any page to describe this main community discussion, now that it is in MCW namespace instead of MCT namespace, it could have a proper talk page.
This would be an enourmus change and could break a lot of links.
1. However, I will try to fix the links
However, it fits more nicely

---Humiebee^{Discuss anything with me Look at my edits} 22:14, 28 September 2020 (UTC)

The community portal page itself needs almost no discussion as most of it is requesting pages or linking other discussions, I don't see a need for a dedicated talk page. This page is the portal to community, including community discussion, so the name seems clear enough to me. Plus, centralized discussion can lead to confusion, such as that the page is the only place we discuss wiki topics. Additionally, as you said, this is a huge change which will break basically any reference to the portal; none of the benefits you listed outweigh breaking all links from former discussions. –KnightMiner · (t) 16:08, 29 September 2020 (UTC)

Looking at the What links here tool, 214 pages link here, and since at least like 50 of them are like redirects and duplicates (yes if it shows a redirect, it shows it indented below the redirect AND as normal) so it shouldn't be such a hard task. Since this page would not be used as much, it's redirects could just change without worry of the actual page, and like you said, if there is no discussion, it could temporaraly become a redirect while the links try to be fixed.---Humiebee^{Discuss anything with me Look at my edits} 22:24, 30 September 2020 (UTC)

In my opinion, the community portal can very well be discussed about on the community portal, "wiki name"/Community portal is default and thus very widely used in other Gamepedia wikis, ftb is completely unrelated to this wiki, apart for the remaining mod pages, and, as you said yourself, this would be a enormous disruptive change. Oppose. Sagessylu (discuss | edits) 17:19, 1 October 2020 (UTC)

Massive Oppose - Seriously? Ok, Wikipedia works this way, but this is ultra massive change, which won't end up being useful. You could name this section - Proposal, which will never get any support. Idk, why, but your ideas are sometimes really outside of reality. This will be so much work, that idk, how will be doing this. A bot? Admins? You? No, this is outside reality change this page, as ut is so active, that it will be bad. Also, even we will end up doing this, it won't be MCW:Centralized discussion, but some MCW:Village pump (just like Wikipedia has it) --TreeIsLife (talk) 12:03, 3 October 2020 (UTC)

Oppose. I don't really see the point in fixing something that isn't really broken. ~ Amatulic (talk) 17:28, 3 October 2020 (UTC)

Weak support Well, I guess I'm the only one who supports this at all. Fadyblok240 (talk) 15:26, 20 October 2020 (UTC)

Massively oppose, there's absolutely nothing to gain from this change, and it would break so much. Every wiki does things slightly differently, consistency with other wikis really isn't a reason to do something. Not only pages on the wiki link to the community portal, links outside of the wiki (such as on discord) will all break too, and you cannot fix those. Do consider all of these in your proposals, because, as stated by others, this idea is way outside of the scope of reality. Nothing to gain, everytging to break. Dhranios (talk) 16:06, 20 October 2020 (UTC)

UCP considerations

suppressredirect permission, UCP, and autopatrolled users

On UCP, regular users won't have the permission to move pages without leaving a redirect. This permission will become admin-only. Since there are valid use cases for non-admins using this permission, but concerns with all users having it, I propose to grant autopatrolled users and patrollers this right. Non-English Minecraft Wikis may have other custom groups that they feel should not lose this right and aren't going to cause much damage with it; if so, I encourage the users of these wikis to list these groups here. See also the Wikipedia group that inspired this proposal. --AttemptToCallNil (report bug, view backtrace) 12:40, 2 October 2020 (UTC)

Is moving without redirect vandalism (or in general bad edits) really common though? because if not, I see no reason to take that permission from anyone who may not have autopatroller rights. Dhranios (talk) 13:10, 2 October 2020 (UTC)

I couldn't get a conclusive answer on whether a configuration with suppressredirect for all registered users will be approved (there's no guarantee it will be, and from what I've heard, staff don't know either). I can't give a conclusive answer on whether such vandalism is common either, but I'd say we should expect disruptive users with accounts to be more common than before given that now having an account is much easier (no more Twitch requirement). --AttemptToCallNil (report bug, view backtrace) 13:26, 2 October 2020 (UTC)

If the privilege gets taken away from regular users, I'd definitely support allowing autopatrol and patrollers to retain it, for the reasons you described. I might actually support it otherwise as well, as currently any user who logs in essentially has the ability to delete a page (because that's literately what moving without a redirect does). If someone has the autopatrol or patroller right, they're presumably trusted enough to make constructive edits/moves, so imo they can be trusted to move without leaving a redirect.--Madminecrafter12 ^{(Talk to me | View what I've done)} 13:17, 2 October 2020 (UTC)

Done I added the suppressredirect permission to the following groups:

--

MarkusRost (talk) 22:50, 2 October 2020 (UTC)

Comparison of Lua-based templates and non-Lua counterparts

According to Template:SimpleNavbox/doc, Lua-based templates seem to be slower than their non-Lua counterparts, contrary to the situation on Wikipedia. This might change when the Minecraft Wiki is transferred to the UCP. I want someone to prove or disprove the statement that Lua runs slower than parser functions, before and after migration to the UCP. Fadyblok240 (talk) 02:26, 3 October 2020 (UTC)

That template is not a useful general judgement for Lua vs. wikitext. In fact, in many cases Lua-based templates are going to be faster. In addition, with UCP we are expected to eventually get LuaSandbox, an extension that makes Lua even faster. --AttemptToCallNil (report bug, view backtrace) 04:33, 3 October 2020 (UTC)

List of broken items

~~Protection icons~~
Some text that was centered is now left-aligned

Fadyblok240 (talk) 20:00, 5 October 2020 (UTC)

Revert war

Today, there was Minecon. That means many edits from IPs and vandals. But today, there is problem with diffrent thing - Planned Fixes and Planned changes.

There are 2 camps now for these 2 topics. First is that, which wants to have Planned fixes on page and Planned additions on Update page.

Second (in which i am) wants to have Planned additions on page and don't have Planned fixes on page.

So to solve this problem, we can vote, because Camp 1 is now (if i am correct) violating style guide. So we could change it and don't be scared, that we will have edit wars after Update annouced.

Here are options for Planned Additions

Have Planned Additions on Caves & Cliffs page
Have Planned Additions on Java Edition 1.17

Options for Planned Fixes

Have it on update page
Have it seperate page
Don't have it

--TreeIsLife (talk) 19:16, 3 October 2020 (UTC)

With Planned additions, i Support Option 2, and with Planned Fixes also Supporting Option 2. --TreeIsLife (talk) 19:16, 3 October 2020 (UTC)

Planned additions go on the Caves & Cliffs page for now, and is transcluded on JE & BE 1.17, but fixes are edition-specific and should go on their respective pages. Nixinova T C 19:45, 3 October 2020 (UTC)

@Nixinova: Maximally, we could make subpage for entire update content, like Legacy Console Edition has. –Preceding unsigned comment was added by TreeIsLife (talk • contribs) at 19:51, 3 October 2020 (UTC). Please sign your posts with ~~~~

Well, LCE versions are pretty much exactly the same, running on the same codebase etc. Java/Bedrock are very much not that. Nixinova T C 03:41, 5 October 2020 (UTC)

Smash content

Hi hi. I'm not a regular editor of the Minecraft Wiki, but rather a visitor from SmashWiki, which—as you can imagine—has been busy with the reveal of Steve and company in SSBU. I was curious as to how you all are going to handle the Minecraft content in Smash. We're already linking to you on a few pages, and I've proposed making a formal partnership between wikis to higher-ups on SmashWiki, but it's still in discussion right now. I suppose right now I just want to ask and gauge interest, since there doesn't seem to be much about Smash on this wiki right now. Is Smash content something you would like to further elaborate on for the wiki, and if so, would partnership (being able to reference and cross-link us where necessary) be of any interest? DryKirby64 (talk) 00:50, 5 October 2020 (UTC)

There's some discussing over at Talk:Super Smash Bros., and personally I think we should indeed document it here. Not sure where exactly, though. Nixinova T C 00:53, 5 October 2020 (UTC)

Minecon Live!!

Mega-massive-ultra news for MCD!!!!

Okay that was too dramatic

1. A very important announcement was made for Minecraft: Dungeons at Minecon Live. First of all, we need renders for all of the new mobs in Howling Peaks. Second of all, we need names for the new DLC skins, we need to find out more about the new Armor, Weapons, and the Artifact.

2. They announced a Nether DLC in a Basalt Deltas Biome, Crimson Forest Biome, and more. Piglins, Blazes, and Wither Skeletons were all seen. Is there any more info?

3. They also announced an Ocean DLC. It contains tons of new mobs, but what about the special rolling mechanics? What about the other underwater features? How can the player breathe underwater? Will the Glow Squid be there?

4. End DLC. In the video, for an extremely short nano-time, I saw Archie, back in his Arch-Illager form, and still with the Orb once again, summoning mobs. Did the Ender Dragon secretly have power over the orb this whole time or something? Why is Archie evil again?

5. Obsidian Monstrosity. End or Nether DLC? If it's even going to be a mob....

So that's about it. Please answer my questions one at a time if you have answers, because my eyesight is poor. Howling Peaks (talk) 12:19, 5 October 2020 (UTC)

This notice would be better suited for the Dungeons wiki. Also, we probably don't need these renders until the DLC is actually released. -PancakeIdentity (talk) 23:58, 5 October 2020 (UTC)

Yea but i still cant wait. Also i would love it if they actually put the Obsidian Monstrosity as a boss, that would be dope. James Haydon (talk) 01:07, 6 October 2020 (UTC)

Standardizing NBT documentation tag order

Currently, NBT documentation is added in a rather arbitrary order in the tree, I'd suggest standardizing the order as much as possible.

My suggestions, either:

Sort alphabetically, ignoring NBT type
Sort by NBT type and then alphabetically

Opinions? Dhranios (talk) 10:13, 6 October 2020 (UTC)

Support for suggestion #1. Seems cleaner to sort alphabetically as sometimes tags may be related in name and what they are used for in-game while having different NBT types. Suggestion #2 seems impractical. -- SizableShrimp🦐 (talk · contribs) 16:43, 7 October 2020 (UTC)

Support for suggestion #1, SizableShrimp pretty much explained everything. Sagessylu (discuss | edits) 19:09, 15 October 2020 (UTC)

#1 makes the most sense. Nixinova T C 22:08, 15 October 2020 (UTC)

Minecraft dungeons on Xbox series x

Yesterday I went to JB Hi-Fi to get minecraft dungeons on Xbox one and on the cover of the disc holder is said compatibility for Xbox One|Xbox Series X. Can someone put the series X logo on the wiki so it can go on the dungeons page and main page. --Minecraft loot (talk) 22:04, 6 October 2020 (UTC)

Sounds Page

Should a sounds page be added, i realize all sounds are being added to pages they are caused from, but should a page with all the sounds from all versions of the game be made, as to have them all in one place, as well as on each page?-Robonate135 _{(T C)} 17:25, 8 October 2020 (UTC)

In my opinion, no. The sound section is only marginally useful, it's just more data to expand the page. It's sufficient for each space (vanilla, Earth, Dungeons) to have their own sound files for things that may be common to all versions. Amatulic (talk) 06:09, 17 October 2020 (UTC)

I don't think this would be super useful and I'd worry about performance and load times with that many files on a single page. I'm not completely opposed to it if anyone has a good reason for it. -PancakeIdentity (talk) 18:16, 22 October 2020 (UTC)

Agreed, sound files take up a lot of space on pages and there is many of them on the wiki for mobs and blocks. I think having these on one page might be useful but it could be hundreds of thousands of bytes in size and could cause severe performance issues or could not load entirely. It would be useful somewhat but it would be too large and too laggy so we shouldn't. James Haydon (talk) 18:22, 22 October 2020 (UTC)

Neutral, mainly what NineTreyBlud said but instead of creating 1 single page, we could split it into a few pages. 1 for subtitles, and 1 for other sounds.---Humiebee^{Discuss anything with me Look at my edits} 20:11, 22 October 2020 (UTC)

It could be made the same way Block states is done, put the sounds to a subpage (e.g Block of Quartz/Sounds) and all the sound subpages would be transcluded to a page like Sounds. – Unavailablehoax (talk) 20:22, 22 October 2020 (UTC)

Ill agree on that one though, just make sure they are in separate tables. James Haydon (talk) 20:31, 22 October 2020 (UTC)

add certain rights to certain user groups

Can you add the autopatrol right to Directors and Patrollers?---Humiebee^{Discuss anything with me Look at my edits} 17:29, 12 October 2020 (UTC)

Shouldn't they already have it by default? James Haydon (talk) 19:15, 11 November 2020 (UTC)

They don't for some odd reason, just go to Special:UserGroupRightsHumiebee^{talk contribs} 03:06, 25 November 2020 (UTC)

WTF happened to advanced search?

Advanced search has become useless. It used to show me search results up to 500 per page. Now it's this short paginated thing that doesn't even include all results, and the pagination links don't even work.

For example, try an advanced search for all articles containing the word "epic". Scroll down and go to page 2. You can't. It goes to the rarity article.

Try a search main space for the word "now". 90 results? Just about every article on the game has history sections that include the word "now". That's hundreds of articles, not 90.

Is there a user setting somewhere that gives me back the original search? The only "improvement" here is the ability to search other wikis, which isn't relevant to me. Amatulic (talk) 02:50, 13 October 2020 (UTC)

I think it has to do with the fact that UCP search doesn't use CirrusSearch, which legacy Gamepedia and Wikimedia had been using. The most advanced thing you can do is filter by namespace, which means we miss out on truly advanced search parameters like insource: and regular expressions. Also, the new search only considers articles by default. Fadyblok240 (talk) 02:55, 13 October 2020 (UTC)

And as I mentioned, it's broken. All search results are not shown, and pagination doesn't work.

Bring back the original Wikimedia search! Amatulic (talk) 22:36, 14 October 2020 (UTC)

I don't think they're switching away from the current search (apparently they believe the original search isn't scalable or performant). Some issues with the search are known and are likely to eventually end up fixed. --AttemptToCallNil (talk) 23:04, 14 October 2020 (UTC)

I don't understand how the Wikimedia search, used on the busiest website on the planet, is considered non-scalable and non-performant. This new mess is not an improvement. Amatulic (talk) 05:44, 15 October 2020 (UTC)

I'm not sure either, nor did I read any extensive explanation for why this change happened. It's possible that Fandom running some hundreds of thousands of wikis and having different hardware constraints are important factors, but I, of course, can't have any data on that either. --AttemptToCallNil (talk) 09:31, 15 October 2020 (UTC)

I agree, you can't even create pages using search function, it's horrible.---Humiebee^{Discuss anything with me Look at my edits} 20:36, 15 October 2020 (UTC)

Yes how do you create pages now? It probably harder. James Haydon (talk) 21:15, 15 October 2020 (UTC)

You have to CREATE A REDLINK????? on a page such as MCW:Sandbox. This is torture.---Humiebee^{Discuss anything with me Look at my edits} 21:20, 15 October 2020 (UTC)

Its easy to create a redlink if you use visual editor, i just go on a small page, add a link that doesnt exist yet, open it in a new tab, and discard my edit and create the page. It may also work with source editor but you have to use the page preview button. James Haydon (talk) 21:22, 15 October 2020 (UTC)

minecraft.gamepedia.com/<page name> – Unavailablehoax (talk) 21:24, 15 October 2020 (UTC)

Yes is suppose but that is the way i am used to creating them. James Haydon (talk) 21:26, 15 October 2020 (UTC)

I never use visual editor as it is ick, Unavailablehoax's idea is fine and easy though.---Humiebee^{Discuss anything with me Look at my edits} 02:26, 16 October 2020 (UTC)

Another thing is that it doesn't suggest the redirect when typing in the search bar, but instead the target page of the redirect.

For example, typing 'Warden' doesn't suggest the redirect Warden, but instead Caves & Cliffs. This means a user trying to find information about the Warden would have to scroll to the Caves & Cliffs § Warden section, while the Warden redirect would have gone to that section automatically. – Unavailablehoax (talk) 21:47, 15 October 2020 (UTC)

Comment Yes that is really not a good thing, it makes redirects useless unless it goes to an actual page instead of a section. James Haydon (talk) 21:50, 15 October 2020 (UTC)

A fix at least for the no new page link is expected to come. Other fixes are definitely considered. If you have specific feedback, please send it to Zendesk (like that redirect thing) so that staff take a look. But chances are, a lot of the issues you raise here are already known. (It's useful to tell us anyway even if they just answer, "This is known". Part of the reason I wrote that list on the Help Wiki is to present the community with a centralized, if unofficial, source of issue information in the absence of a public issue system.) --AttemptToCallNil (talk) 23:33, 15 October 2020 (UTC)

The redirect problem has been fixed, still waiting for the page creation issue, typing Caves and Cliffs worked.---Humiebee^{Discuss anything with me Look at my edits} 22:54, 16 October 2020 (UTC)

The pagination bug I mentioned at the top of this thread is fixed too. Advanced search for "epic" and the page links at the bottom no longer take you to the rarity article. However, erroneous search results appear, like pickaxe and sea pickle, neither of which includes the word "epic" anywhere in the article. Amatulic (talk) 06:06, 17 October 2020 (UTC)

The redirect bug and the create new page bug has been fixed, however there are still many other bugs such as what Amatulic said, incorrect search results as well as a lack of results. Wikimedia search is not going to come back in a LONG time (most likely never)---Humiebee^{Discuss anything with me Look at my edits} 01:15, 21 October 2020 (UTC)

Did they also stop advertising unrelated wikis in the corner, because that is annoying too. James Haydon (talk) 01:17, 21 October 2020 (UTC)

They did, it's still comepletly broken as when i search welcomee, it does not even show results for welcome, it just shows some random story mode episode page like ???????---Humiebee^{Discuss anything with me Look at my edits} 01:22, 21 October 2020 (UTC)

I think it looks for those words in other pages and then recommends them above the actual pages. James Haydon (talk) 01:24, 21 October 2020 (UTC)

Update, there is another bug with search. When you search a page that does not exist, it shows as a blue link but when you click on it, it says Creating Page <page name>.Humiebee (talk) 17:19, 16 February 2021 (UTC)

Spooky Fall

Make pages with content from the MCD:Spooky Fall MCD:Seasonal Trials. Minecraft Dungeons Howling Peaks (talk) 15:58, 16 October 2020 (UTC)

Okay i already have an image related to that on my computer. James Haydon (talk) 15:59, 16 October 2020 (UTC)

Like Pages for MCD:Hungry Horror and MCD:Haunted Bow. Minecraft Dungeons Howling Peaks (talk) 18:49, 16 October 2020 (UTC)

Yes, if those are the names i will create them. James Haydon (talk) 18:51, 16 October 2020 (UTC)

They are now created, give me any more items/mobs that will appear in these seasonal trials. James Haydon (talk) 18:55, 16 October 2020 (UTC)

Go to twitter.com/dungeonsgame and check daily for any new Spooky Fall-related Dungeons items or mobs, I need to catch up on online schoolwork so I won't be available to do so. I'm getting backlogged. Minecraft Dungeons Howling Peaks (talk) 14:26, 17 October 2020 (UTC)

Never received confirmation email

I keep getting a message at the top of most pages that my email address has not been confirmed. I've clicked the link to send me another email many times, but still have never received an email of any kind.

Can someone verify that the email sending process actually works?

(Yes, I checked my junk filters and other tabs of mail.)

Jim SirDaddicus (talk) 21:32, 17 October 2020 (UTC)

Same for me, but I signed up using twitch, so I somehow eventually got it in my twitch email, not my gamepedia account email. Blockofnetherite ^{Talk Contributions} 02:59, 18 October 2020 (UTC)

When i did it i had to wait many hours for it to come in, i even thought something was wrong with my email and i changed it. The UCP migration has kind of ruined gamepedia in some ways. James Haydon (talk) 18:51, 18 October 2020 (UTC)

Remove section on Mob page

There's a low-quality section "mobs to be added" on the Mob page, which also violated a comment on the page that explains to not add any mobs until they appear in a development version. I was simply going to delete this section, but was disallowed.

SweptThrone (talk) 01:01, 23 October 2020 (UTC)

I fixed some of the grammar and capitalization, but i am still disputing if it should be there. James Haydon (talk) 02:47, 23 October 2020 (UTC)

I commented out the section as a violation of MCW:FUTURE. Nixinova T C 04:37, 23 October 2020 (UTC)

Okay, i wasnt keen on keeping it, as it has been removed before for the same reason. James Haydon (talk) 12:43, 23 October 2020 (UTC)

bedrock or java?

i feel that the java and bedrock info is a bit outdated and me, a bedrock editon player have items, mobs, and blocks that you mark "java only" i think you shoud work on that--67.189.86.56 18:34, 5 November 2020 (UTC)

Which pages do you mean? – Unavailablehoax (talk) 18:57, 5 November 2020 (UTC)

Moving Minecraft Story Mode Wiki to this wiki

The following discussion of a proposed Pausing merger, because MCSM Wiki editors are oppose for now. Till admins won't discuss with editors and readers, it has no sense to keep it open --TreeIsLife (talk) 13:44, 27 November 2020 (UTC) is closed. Please do not modify it. Subsequent comments should be made in a new section.

merger with Minecraft Story Mode Wiki

Hi guys. I have an idea, which we partially discussed on Minecraft Wiki Crossover Discord. So, idea is creating Namespace for Minecraft Story Mode and moving there content from https://minecraftstorymode.fandom.com. Yes, it is an active wiki, with many content, which may help this wiki.

This is in a plan of entire crossosover of wikis.

We discussed, that there should be 3 big wikis - Minecraft Wiki (with all non-community content releated to MC), FTB Wiki (for mods) and Minecraft Community Wiki (Creepypastas, Servers, buildings, etc.)

So, what do you think about migrating Story Mode Wiki? --TreeIsLife (talk) 14:23, 11 November 2020 (UTC)

Having it be kept under a namespace is basically the only thing I'm bothered about. Otherwise, go ahead. - User-12316399 (talk) 14:25, 11 November 2020 (UTC)

Well, unfortunatly, it is not so easy as you think. So, there is need for both sides to agree. And as the Wiki has users, who are still contributing, i cannot just force users. I know that, because i already merged 1 community and it took 1 month, to just start it. And it compleated 1.5 months later, with wiki being locked.

And wiki is somewhat active. --TreeIsLife (talk) 15:52, 11 November 2020 (UTC)

So, when comparing to this number of content + users, it may take 2 or 3 months. But, if not using Discord, maybe just few weeks.--TreeIsLife (talk) 14:36, 11 November 2020 (UTC)

Weak oppose, mainly for the reason that story mode is discontinued and it would take a lot of work, and I also Strong oppose adding a separate namespace. Also, the pages themselves will probably gain no traction for readers and editors anyways.Humiebee (talk) 15:45, 11 November 2020 (UTC)

It is just merging for better SEO results, because all Gamepedia wikis will migrate to fandom.com domain early 2021. And this is reason, why i am making a subpage with project crossover. --TreeIsLife (talk) 15:50, 11 November 2020 (UTC)

Changed to Weak support and Neutral per below.Humiebee^{talk contribs} 21:28, 13 November 2020 (UTC)

Comment There is already a project about adding minecraft story mode content i believe, but i dont think there is enough to constitute for its own namespace and sub wiki. I think it should have it content put on the main wiki marked with minecraft story mode in the title. James Haydon (talk) 19:03, 11 November 2020 (UTC)

(I think we are getting from the main path - theme). So, i am talking about Wiki, not sub-wiki, which is on Fandom! There are over 300 pages, which makes it big enough to have its own namespace. Next time, use pls term Main page, as main wiki is Minecraft Wiki, as a name, and you probably meant main page. Yes, now, we have like 3 articles, but with this, we can boost wiki with many content. --TreeIsLife (talk) 19:11, 11 November 2020 (UTC)

Okay so if we are going to make a namespace it should be MSM, the acronym for Minecraft Story Mode. James Haydon (talk) 19:13, 11 November 2020 (UTC)

No, we don't use shortcuts as namespaces, only aliases. It would be "Minecraft Story Mode" or "Story Mode" with alias MCSM or SM respectively, to match dungeons and earth (MCD MCE, not MD ME). Dhranios (talk) 19:35, 11 November 2020 (UTC)

I personally Support, the reason being that it's a Minecraft game and should be on the Minecraft wiki. I don't know how many other people would want to contribute. Maybe if we contacted the people in the Fandom Wiki they would be up to helping. There is currently a request move on my user page for a Story Mode exclusive features for an official page. If nothing else, we could at least have that. https://minecraft.gamepedia.com/User:Yekulten/Story_mode_exclusive_features Yekulten (talk) 12:35, 12 November 2020 (UTC)

Support moving Story Mode content to this wiki. This would improve the main Minecraft wiki by making it more comprehensive, and could even bring in new readers and editors. The move would also improve consistency, as all other official Minecraft games are already documented in this wiki. GrogTheGreatEvilGoblinWarlord (talk) 14:07, 12 November 2020 (UTC)

Strong support — Thomanski | t | c | 08:11, 13 November 2020 (UTC)

Strong support. More editors, more pages, more relevance on Google and everything on its own namespace, which means nothing will change in vanilla documenting. --Dr03ramos (talk) 12:17, 13 November 2020 (UTC)

Strong support The Great Spring (talk) 12:18, 13 November 2020 (UTC)

Strong support DEJVOSS (talk) 12:45, 13 November 2020 (UTC)

Supporting for above reasons Blockofnetherite ^{Talk Contributions} 16:59, 13 November 2020 (UTC)

Strong support okay lets make it happen. James Haydon (talk) 18:18, 13 November 2020 (UTC)

Strong support Just because story mode is discontinued doesn't mean we shoud treat it differently from Minecraft Earth and Dungeons. it should be given pages for the episodes and mobs, its own mainspace, and more contributors on the story mode wiki project --Minecraft loot (talk) 03:13, 15 November 2020 (UTC)

Process

So, i see great support, and first admin respond, and he has no concerns 🙂, except User groups changes. So, our questions are:

User groups

On MCW Crossover, it has been already discussed, and there was result of re-vote. That will mean, we will start vote about them.

Bot

We can use any bot

When?

Well, best will be as soon, as possible

Content

All it should in Minecraft Story Mode namespace. Its alias should be MCSM?

What do you think? And if there is something to add, add it!

--TreeIsLife (talk) 14:35, 16 November 2020 (UTC)

So basically, what are we doing? Is there a project page? If so, we should have one. Then what do we do? Basically copy paste the content from the fandom? I agree with the namespaces Minecraft Story Mode: and Minecraft Story Mode Talk: , but I am currently undecided on its alias. I personally believe MCSM and MCST are good, although they are 4 characters, but that shouldn't be a major problem at all. Can someone answer these questions, now that this proposal got massive amount of support? Blockofnetherite ^{Talk Contributions} 18:02, 17 November 2020 (UTC)

We will not copy paste, that'd lose edit history and alike, instead the pages will need to be exported. Also, IIRC, there's already a project for documenting story mode. Dhranios (talk) 20:23, 17 November 2020 (UTC)

About the user right thing. You said that we'll vote, so let's do it here then. I'd say to create a custom user right that gives content-moderator (read more here) but limited to the MCSM namespace. However, i'm not sure if we should do that. --Dr03ramos (talk) 10:54, 18 November 2020 (UTC)

We said we won't do user groups limited to one namespace, because it will be techically difficult. --TreeIsLife (talk) 12:37, 18 November 2020 (UTC)

Herobrine page

Hi guys. After suggestion from discussion on Discord about crossover, we ran to problem with a page Herobrine. As Herobrine is community made, but really noticed by Mojang Staff, it makes us thinking, if we should keep this page or not?

What do you think? Do you support deletion, or not? --TreeIsLife (talk) 19:38, 13 November 2020 (UTC)

Support we already moved most of the mod related pages on this wiki to FTB, so making a wiki for fancontent and community content is a good ides. But it should be for more than just moving already existing pages. James Haydon (talk) 19:42, 13 November 2020 (UTC)

Neutral, I do not have an opinion on this yet, however, could you supply a link to the discord message on the mcw server? Blockofnetherite ^{Talk Contributions} 18:04, 17 November 2020 (UTC)

Strikethroughed because I am no longer neutral and I have also seen the original discord converstationBlockofnetherite ^{Talk Contributions} 16:09, 19 November 2020 (UTC)

Switched to Oppose, at least for now or any time soon, as a Herobrine page is actually useful as Mojang references it, and even references it in the code (no, I am not talking about implementing it), like "4J studios may have removed Herobrine" or things like that. Also opposing for below discussion. Blockofnetherite ^{Talk Contributions} 23:39, 18 November 2020 (UTC)

Oppose for now. If we're making that three main wikis thing I've proposed on MC crossover Discord, we should first have the fan content wiki estabilished and only then move the Herobrine page. --Dr03ramos (talk) 10:57, 18 November 2020 (UTC)

Finally, you remember, that you proposed 3 wikis! --TreeIsLife (talk) 13:34, 18 November 2020 (UTC)

Oppose deletion. Herobrine is a notable part of Minecraft's history and regularily mentioned in changelogs by Mojang. It shouldn't be removed from the wiki just because it's community-made. Violine1101 (talk) 16:31, 18 November 2020 (UTC)

Oppose deleting the Herobrine page. The Great Spring (talk) 23:41, 18 November 2020 (UTC)

Seems like a lot of people are against this now. James Haydon (talk) 02:26, 19 November 2020 (UTC)

Yes, but it was not my idea. --TreeIsLife (talk) 06:56, 19 November 2020 (UTC)

Okay based on everyone's reaction i think we might have to re-discuss this over. James Haydon (talk) 05:13, 21 November 2020 (UTC)

Create List of entity textures?

List of block textures already exist, need to create List of entity textures.-- Duowan channel（T&C） 23:29, 13 November 2020 (UTC)

An observation: "Random Page" is quite unlikely to get anything useful

Out of 10 tries, I observed exactly one that was about gameplay (Netherite Scrap), one about about a rule (Minecraft Dungeons:rarity), and one about a data file (level.dat) The remainder consisted of two short summaries of not-very-notable employees and FIVE short summaries of specific platform edition numbers. This suggests that there's a lot of room to clean up or combine near-useless pages so the average random page is likely to teach something interesting or spark an interesting session of following links; the cleanup of, especially, the specific platform versions ought to be accessible to a simple script to combine them all, depending on what tech underlies the wiki. --Realweregamer (talk) 03:57, 14 November 2020 (UTC)

I suggested it to be Special:Random, not SP:RandomRootPage, though it has mostly the same issues, probably ending in a /DV or some other technical page, possibly remove it?Humiebee^{talk contribs} 23:30, 16 November 2020 (UTC)

Yes, Special:Random does give version articles a lot, but that's not a bad thing, because there are a lot of version numbers. They shouldn't be combined because each version article can contain a lot of content. Special:Random isn't meant to be "useful", and there are index pages for them like Version history. Nixinova T C 23:45, 16 November 2020 (UTC)

The link uses Special:RandomRootPage which excludes subpages. Some of these subpages are considered to be articles e.g. Java Edition version history/Development versions but others are like templates (e.g.Dirt/BS) We should move all article subpages to root pages or move all non-article subpages into template namespace and reconfigure the link so that it could link to subpages. This won't fix the problem entirely, but it could help. Also, why is it called "Random page" instead of "Random article"? Fadyblok240 (talk) 00:56, 21 November 2020 (UTC)

Make some templates more reader-friendly

Some templates such as {{more images}} and {{infobox}} without an an image parameter cause unnecessary clutter for readers. Since only registered users can upload files, readers cannot address the problems presented by these templates. To provide a cleaner look for some articles, I propose moving templates like {{more images}} to talk pages or hiding them from readers by using a CSS class. For infoboxes, removing the placeholder image at least for readers would reduce whitespace. Also, the {{delete}} template has a "delete" link that only administrators can use, so I am considering hiding it from non-admins, which also requires a CSS class. Fadyblok240 (talk) 00:26, 22 November 2020 (UTC)

Hiding content with CSS is generally not a good idea and preferably avoided. For one, Google finds it anyway, and this might incur SEO penalties. While most readers never become editors, and it's unlikely such templates get a lot of readers make their first uploads, I feel it's not the best idea in terms of "wiki way" to hide content from unregistered users. In addition, I'm not sure there are easy CSS classes to do things based on group preferences, so that might need to be spread across multiple CSS files (MediaWiki:Group-sysop.css). (Note also delete links are useful for SOAP and maybe even WMs/staff, who also might need to act on deletion templates, but aren't necessarily local admins. This means the link would need to be hidden based on user rights, not group membership, which I'm not sure can be done easily.)

In other terms, Oppose the presented solution, doesn't seem like a substantial problem, but incurs other problems and seems to require a rather complicated solution.

As an additional idea, maybe move editor-facing message boxes like {{more images}} to the bottom of pages? --AttemptToCallNil (talk) 01:25, 22 November 2020 (UTC)

Oppose moving notice templates to the bottom of pages becuase then editors would not even see the notice template at all. If possible, notcie templates can be hidden from ip's as readers would probably not register an account without editing. What is the "wiki way" anyways? As for the orginal proposal, I am Weak oppose per AttemptToCallNilHumiebee^{talk contribs} 02:36, 25 November 2020 (UTC)

By "wiki way" here I meant the idea that editing should be open to unregistered users, and they should be treated as potential editors instead of just readers. --AttemptToCallNil (talk) 02:57, 25 November 2020 (UTC)

True, though a possible solution is to do it based on edits. 1 edit means ips AND users are able to see notice templates. This shows that they are an editor.Humiebee^{talk contribs} 03:03, 25 November 2020 (UTC)

Convert some disambiguation pages into broad concept articles (again)

This got archved but I don't really feel like closing it. To continue, ai Support doing this AND I have revamp the netherite article. Fadyblok240, you Should start turning the pages into broad concept articles.Humiebee^{talk contribs} 01:59, 25 November 2020 (UTC)

Cleanup of the docs of Bedrock Edition add-ons articles: Request 1

I want to contribute by fixing up all the scripting and layouting of articles related to add-ons and the Bedrock Edition add-on/resource pack/behavior pack documentation. My first request is a page split of the Bedrock Edition scripting documentation as there is a lot of information there. I said the following on the talk page of that article:

I am suggesting that we split these into separate pages under the Bedrock Edition scripting documentation umbrella. This is because programming documentation has a lot of headings, subheadings and such, this page is really diving deep. So I suggest the following:

Scripting system will remain on the landing page: Bedrock Edition scripting documentation
Script API objects will be in Bedrock Edition scripting documentation/Script API objects
Script bindings will be in Bedrock Edition scripting documentation/Script bindings
Script components and User-Defined Components will be in Bedrock Edition scripting documentation/Script components
Script events will be in Bedrock Edition scripting documentation/Script events

Feel free to share any thoughts on this.

Or maybe some other way to fix that particular article, as there is no style guide that is related to programming, let alone JavaScript documentation (according to my knowledge). YivanGamer (talk) 06:41, 3 December 2020 (UTC)

Readd Pi Edition history to pages

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

Originally this was removed due to Pi Edition being discontinued. However, Console and 3DS editions have also been discontinued, yet history information for these is kept on pages, so should Pi Edition info make a return to pages it applies to? - User-12316399 (talk) 01:32, 4 December 2020 (UTC)

Strong support yeah this makes no sense Oreli (talk) 01:40, 4 December 2020 (UTC)

I Oppose because Pi Edition was just one, unlike Console and 3DS which had many more. All the info for Pi Edition can be seen on its main article, so this would be pointless. Thejoaqui777 (talk) 02:14, 4 December 2020 (UTC)

Agree with joaqui Nixinova T C 05:19, 4 December 2020 (UTC)

Pi edition was literally just an adapted version of pocket edition alpha 6.1.0, so its not really even its own edition. James Haydon (talk) 05:24, 4 December 2020 (UTC)

Oppose per Thejoaqui777. The Great Spring (talk | contribs) 05:28, 4 December 2020 (UTC)

Weak Oppose for above reasons. I have Pi edition and know that there is barely anything there. Blockofnetherite ^{Talk Contributions} 17:22, 4 December 2020 (UTC)

Stongest oppose that i have ever opposed

It never got updated
It would be extremely inconvenient
All the info is on pi edition page

Just noHumiebee^{talk contribs} 17:28, 6 December 2020 (UTC)

Ray Tracing

Shouldn't we have a article on ray tracing.
It is a feature of more light and smooth light and all that sort of stuff.
For more information go to Minecraft.net and look at articles that have RTX or ray tracing in them.
to get started here is one. https://www.minecraft.net/en-us/updates/ray-tracing
from --73.89.66.98 18:12, 10 December 2020 (UTC)

Redirect capitalization

Currently, we are allowed to make lowercase redirects that point to their uppercase articles. However, it is unclear whether we should create uppercase redirects to articles with lowercase titles. Is it okay to create such uppercase redirects, since when someone tries to go to an uppercase form of the same article, they go to the search page instead of directly to the lowercase article. Blockofnetherite ^{Talk Contributions} 19:01, 8 December 2020 (UTC)

Per the style guide, alternate capitalization redirects are allowed. Dhranios (talk) (Join the wiki videos project!) 19:04, 8 December 2020 (UTC)

Okay thanks, but was there a time before UCP where "uppercase is redundant to lowercase," where uppercase was not needed because the system already redirected? I feel like that has changed since UCP. Blockofnetherite ^{Talk Contributions} 19:10, 8 December 2020 (UTC)

Inventory Template in Snapshot and releases Pages

I wanted to add to the snapshot pages some Images of all the things added in that snapshot, using the Inventory template, I already done that to a lot of pages, and it looks pretty good aesthetically, in the case I don't get the permission here to do that I will undo that, Am I allowed to do that? RondiMarco (talk) 18:13, 13 December 2020 (UTC)

~~Per this discussion, Neutral.~~ The Great Spring (talk | contribs) (Tagalog translation) 13:18, 14 December 2020 (UTC)

Seeing the discussion there the concensus wasn't reached, so it is worth to discuss this again. However that discussion used the same format of what we are doing currently at "Planned additions" on the Caves & Cliffs article, and what RondiMarco did is add just the inventory template. I Support this because it's a little summary of additions with another format, so I don't find a problem there, because it's just visual, and for development versions the things there were just adittions, not changed ones. Thejoaqui777 (talk) 18:03, 15 December 2020 (UTC).
Edit: Also with visual is that they don't make the page look cluttered and are an easy link to the blocks and items articles. Thejoaqui777 (talk) 18:07, 15 December 2020 (UTC)

Changed to Support. TheGreatSpring (talk) 03:21, 27 December 2020 (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)

Moving the remaining orientable block renders to use the current naming system

Currently just about all blocks which can connect (e.g. iron bars, redstone wire) or be oriented (e.g. furnaces, pistons) directionally share a consistent naming system. However, a notable exception is blocks with log orientation, which still use an Axis orientation. I've marked all of these for moving but have been instructed to ask about this here.

Advantages of moving:

More consistent with other block files with directional placement
Considerably easier to memorise as a result (with few exceptions, all block renders have north-west as the upwards direction, meaning up-left is west and up-right is north; with the Axis naming you'd need to also consider which axis corresponds to which direction, which wastes time and also changed throughout the game's history)
Has allowed some remaining files which didn't follow the remaining parts of the naming scheme to be identified and fixed

Disadvantages of moving:

Not consistent with the block's actual block state naming (probably not relevant as if we were to keep to being completely consistent with block states, rails for example would have to be moved to names such as "Rail Shape North South JEx BEy")

Other things to note:

Some blocks had an "Axis None" orientation and their new file names after this unification may be unclear. However, this exact same thing affects some files which already use the intended new naming scheme File:Hexahedral Piston.png File:Hexahedral Sticky Piston.png , so this is likely worth a separate, smaller discussion.
Whether this move is or isn't worth the time/effort is effectively irrelevant, as the move templates will need to be deleted from several talk pages anyway, which would take roughly the same amount of time and both outcomes will likely be performed by a bot/other form of automation anyway

Are there any good enough reasons this move shouldn't go ahead? - User-12316399 (talk) 13:27, 30 December 2020 (UTC)

I personally think we should follow the block states. Writing them out fully is not needed (EG drop the "Axis" from the current files), but we should not change the naming completely. What bothers me right now, for example, is the cauldrons "Cauldron (moderately filled with water)" (instead of "Water Cauldron Level 2" (level can be dropped per previous sentence)), which is absolutely nothing like the actual state of the block. Your rail example (Rail Shape North South) could be simplified to Rail NS, that would still follow the block states, just using a shorter variation.

This "and also changed throughout the game's history" has never actually happened, it was correcting where the sun came from, the axis themselves weren't changed, and never will.

Keep in mind that being aligned to the north-south axis is not the same as facing north or south. Dhranios (talk) (Join the wiki videos project!) 19:38, 30 December 2020 (UTC)

Just got an issue with the naming system that you're trying to apply. For rails, is Ns ascending north, or ascending south? Changing the rail file links from Ns nS Ew and eW to A<letter> for "Ascending <direction>" it is a lot more clear which is which. Dhranios (talk) (Join the wiki videos project!) 21:41, 30 December 2020 (UTC)

Lowercase is the ascending direction - the same logic applies here for redstone dust. - User-12316399 (talk) 14:18, 31 December 2020 (UTC)

It's also logical to think "uppercase is where it does up". Dhranios (talk) (Join the wiki videos project!) 20:21, 31 December 2020 (UTC)

Wouldn't that still be the same thing? – Unavailablehoax (talk) 20:26, 31 December 2020 (UTC)

No, see the redstone dust, which he compared it to, uppercase is not up directions File:Active Redstone Wire (EW).png File:Active Redstone Wire (ew).png. Dhranios (talk) (Join the wiki videos project!) 20:28, 31 December 2020 (UTC)

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.Humiebee^{talk 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)

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.Humiebee^{talk 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.Humiebee^{talk 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?Humiebee^{talk contribs} 21:45, 30 December 2020 (UTC) 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 .Humiebee^{talk contribs} 21:45, 30 December 2020 (UTC) 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)

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)

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>[[Ender Pearl|Ender Pearl]]<br/>{{Update|[[game rule]] <code>enderPearlsVanishOnDeath</code>}}
{{ItemEntity
|image=Ender Pearl.png
|renewable=Yes
|stackable=Yes (16)
|size=Height: 0.25 Blocks<br>Width: 0.25 Blocks
}}
An '''ender pearl''' is an [[item]] that can be thrown to [[teleport]] to where it lands, or used to craft [[eye of ender|eyes of ender]] which are required to access [[the End]].

== Obtaining ==
=== Mob loot ===
An [[enderman]] has a 50% chance to drop 1 ender pearl when killed. The drop is increased by 1 per level of [[Looting]], with a maximum of 4 with Looting III.

=== Chest loot ===
{{LootChestItem|ender-pearl}}

A [[trapped chest]] always containing 2 ender pearls can be found in the "fake end portal" room of [[woodland mansion]]s.

=== Trading ===
{{IN|java}}, expert-level [[Trading#Cleric|cleric villagers]] have a {{frac|2|3}} chance to sell an ender pearl for 5 [[emerald]]s.

{{IN|bedrock}}, expert-level cleric villagers sell one ender pearl for 5 emeralds.

=== Bartering ===
[[Piglin]]s have a {{frac|10|459}} (2.18%) chance to [[barter]] 2–4 ender pearls when given a [[gold ingot]].

== Usage ==
Ender pearls can be thrown by pressing {{control|use}}. After it is thrown, the ender pearl is consumed, and the player teleports to where it lands, taking {{hp|5}} [[fall damage]]. Wearing armor enchanted with [[Protection]] and/or [[Feather Falling]] reduces the damage taken from the ender pearl. 

Ender pearls have a small cone of travel; they do not all follow the same path when thrown in the same direction. The direction and velocity of ender pearl throws is slightly randomized. They can travel about 30 blocks{{Only|java}}/45 blocks{{Only|bedrock}} when thrown straight up, and up to 54 blocks forward when thrown at an optimum launch angle of ~35° (on even ground).

The thrower's vertical velocity influences the throw. Hence timing a throw with a jump can increase the throwing range to 42 blocks when thrown straight up and 64 blocks forward at a 35° angle. Throwing while falling significantly decreases the range. Ender pearls collide with all [[minecart]] types, [[boat]]s, [[end crystal]]s and [[nether portal]]s, and travel through [[end portal]]s. Ender pearls that fall into the [[void]] disappear, and do not trigger the player to teleport. However, ender pearl entities (instead of dropped items) are ''not'' destroyed by lava and will teleport the player to the bottom of lava pools/lava oceans.

Ender pearls have a cooldown of one second before they can be used again. The cooldown is shown in the hotbar by a white overlay on the ender pearl that shrinks and must disappear before the player can use it again. If there are other inventory or hotbar slots containing ender pearls, they are covered with the white overlay as well.<ref>{{bug|MC-88236|||WAI}}</ref> 

Ender pearls can be thrown into [[end gateway]]s to reach the outer islands of the End. They can also be thrown into the [[exit portal]] to reach the player's spawn point.

Ender pearl teleportation makes no sound ''itself''{{only|java}}, but does emit a "small fall" sound at the destination when applying teleportation damage to the player.

=== Stasis chamber ===
Ender pearls are affected by [[bubble column]]s. An ender pearl can remain afloat on top of an upward bubble column, allowing it to be stored indefinitely. A mechanism can then be triggered to make the ender pearl hit a solid surface (e.g. by closing a [[trapdoor]]), teleporting the thrower back to the setup wherever they are.

=== Spawning endermites ===
An ender pearl has a 5% chance to spawn an [[endermite]] when it lands. This is the only way through which endermites can spawn, without using cheats. The endermite spawns at ''the player's position'' when the pearl lands{{only|je}}, or at the pearl's landing site{{only|be}}.

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

== Sounds ==
{{edition|java}}:<br>
Thrown ender pearls use the Friendly Creatures sound category for entity-dependent sound events.
{{Sound table
|sound=Bow shoot.ogg
|subtitle=Ender Pearl flies
|source=neutral
|description=When an ender pearl is thrown
|id=entity.ender_pearl.throw
|translationkey=subtitles.entity.ender_pearl.throw
|volume=0.5
|pitch={{frac|1|3}}-0.5
|distance=16
|foot=1}}

{{Edition|Bedrock}}:
{{Sound table
|type=bedrock
|sound=Bow shoot.ogg
|source=player
|description=When an ender pearl is thrown
|id=random.bow
|volume=0.5
|pitch=0.33-0.5
|foot=1}}

== Data values ==
=== ID ===
{{edition|java}}:
{{ID table
|edition=java
|firstcolumnname=Item
|showforms=y
|generatetranslationkeys=y
|displayname=Ender Pearl
|spritetype=item
|nameid=ender_pearl
|form=item
|foot=1}}
{{ID table
|edition=java
|firstcolumnname=Entity
|generatetranslationkeys=y
|displayname=Thrown Ender Pearl
|spritetype=entity
|spritename=Ender Pearl
|nameid=ender_pearl
|foot=1}}

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|firstcolumnname=Item
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Ender Pearl
|spritetype=item
|nameid=ender_pearl
|id=422
|form=item
|foot=1}} 
{{ID table
|edition=bedrock
|firstcolumnname=Entity
|shownumericids=y
|generatetranslationkeys=y
|displayname=Ender Pearl
|spritetype=entity
|nameid=ender_pearl
|id=87
|foot=1}}

===Entity Data===
Thrown ender pearls have entity data that define various properties of the entity.

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

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

== Achievements ==
{{Load achievements|Beam Me Up}}

== Advancements ==
{{load advancements|Remote Getaway;Bullseye}}

== History ==
{{History|java beta}}
{{History||1.8|snap=Pre-release|[[File:Ender Pearl JE1.png|32px]] Added ender pearls along with [[endermen]]. 
|Ender pearls have no use, but can stack up to 64.}}
{{History|java}}
{{History||1.0.0|snap=Beta 1.9 Prerelease|Ender pearls are now less commonly found near bodies of [[water]] since [[endermen]] now teleport away when in contact with water. Before this version, endermen didn't attempt to teleport and were [[damage]]d/killed from water much more frequently, causing numerous ender pearls to occur around bodies of water.
|Later, on a suggestion from [[wikipedia:Reddit|Reddit]] user isJesus, [[Notch]] implemented the teleporting feature for ender pearls.<ref>http://www.reddit.com/r/Minecraft/comments/kpsay/eggsnowballender_pearl_suggestiongif/c2mabfj</ref><ref>{{Tweet|notch|118614580539826176}}</ref><ref>http://www.reddit.com/r/Minecraft/comments/kss7n/twitter_ender_pearls_have_a_unique_ability_now/c2mwldd</ref>}}
{{History|||snap=Beta 1.9 Prerelease 2|Added teleporting feature to ender pearls.
|Using an ender pearl to teleport resulted in being kicked from servers for "hacking". This is due to a check triggering that was supposed to prevent modified clients from moving too quickly.
|Ender pearls now only stack up to 16.}}
{{History|||snap=Beta 1.9 Prerelease 3|Ender pearls are now used to craft [[eyes of ender]].
|Ender pearls can now be found in the new [[stronghold]] altar [[chest]]s.}}
{{History||1.3.1|snap=12w24a|[[File:Ender Pearl JE2 BE1.png|32px]] The texture of ender pearls has been changed.}}
{{History||1.8|snap=14w02a|As part of the revamp of the trading system, cleric [[villager]]s now [[trading|buy]] ender pearls.}}
{{History|||snap=14w03a|Villager clerics no longer buy ender pearls.}}
{{History|||snap=14w11b|Ender pearls have a 5% chance to spawn [[endermite]]s when used.}}
{{History||1.9|snap=15w31a|Ender pearls can now be thrown in [[Creative]] mode.}}
{{History|||snap=15w34c|Ender pearls now have a cooldown after using them.}}
{{History|||snap=15w41a|[[Villager]] clerics now [[trading|sell]] ender pearls for 4–7 [[emerald]]s, as one of their tier III trades.}}
{{History|||snap=15w49a|Thrown ender pearls now take the user's motion into account. For example, an ender pearl thrown forward will land closer if the player is falling, and land farther if the player is ascending.}}
{{History||1.10|snap=16w21a|Ender pearls can now teleport riders off their mounts.}}
{{History||1.11|snap=16w32a|The entity ID of ender pearls has been changed from <code>ThrownEnderpearl</code> to <code>ender_pearl</code>.}}
{{History|||snap=16w39a|Ender pearls can now be found in [[woodland mansion]]s' fake portal room [[chest]]s.}}
{{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 368.}}
{{History||1.14|snap=18w43a|[[File:Ender Pearl JE3 BE2.png|32px]] The texture of ender pearls has been changed.}}
{{History||1.16|snap=20w07a|Ender pearls have a {{frac|2|109}} (~1.83%) chance of being offered by [[piglin]]s when [[bartering]], in a stack size of 2–4.}}
{{History|||snap=20w09a|Ender pearls now have a {{frac|10|226}} (~4.42%) chance of being offered by piglins when bartering, in a stack size of 1–5.}}
{{History|||snap=20w10a|Ender pearls now have a {{frac|20|411}} (~4.87%) chance of being offered by piglins when bartering, in a stack size of 4–8.}}
{{History|||snap=20w20a|Ender pearls now have a {{frac|20|423}} (~4.73%) chance of being offered by piglins when bartering, in a stack size of 4–8.}}
{{History||1.16.2|snap=20w28a|Ender pearls now have a {{frac|10|459}} (~2.18%) chance of being offered by piglins when bartering, in a stack size of 2–4.}}
{{History|||snap=Pre-Release 1|Ender pearls are now affected by [[bubble column]]s.<ref>{{bug|MC-125758|||Fixed}}</ref>
|Ender pearls no longer get destroyed at contact with non-solid blocks.<ref>{{bug|MC-73884|||Fixed}}</ref>}}

{{History|pocket alpha}}
{{History||v0.14.0|snap=build 1|[[File:Ender Pearl JE2 BE1.png|32px]] Added ender pearls. 
|While fully implemented, ender pearls currently have no assigned ID and are currently unobtainable in-game.}}
{{History|pocket}}
{{History||1.0.0|snap=alpha 0.17.0.1|Ender pearls are now obtainable in-game.
|Ender pearls can now be used to craft [[eyes of ender]].}}
{{History|||snap=alpha 1.0.0.0|Ender pearls now require a 1-second cooldown.}}
{{History|||snap=alpha 1.0.0.1|Ender pearl cooldown now has an animation.}}
{{History||1.0.4|snap=alpha 1.0.4.0|Ender pearls can now be [[trading|bought]] from cleric [[villager]]s for 4-7 [[emerald]]s.}}
{{History||1.1.0|snap=alpha 1.1.0.0|Ender pearls can now be found in [[woodland mansion]]s' [[chest]]s.}}
{{History|bedrock}}
{{History||1.10.0|snap=beta 1.10.0.3|[[File:Ender Pearl JE3 BE2.png|32px]] The texture of ender pearls has been changed.}}
{{History||1.11.0|snap=beta 1.11.0.4|[[Trading]] has been changed, expert-level cleric [[villager]]s now [[trading|sell]] an ender pearl for 5 [[emerald]]s as part of their trade.}}
{{History||1.16.0|snap=beta 1.16.0.57|Ender pearls can now be obtained from [[bartering]] with [[piglin]]s.}}
{{History||1.16.100|snap=beta 1.16.100.54|Ender pearls now have a {{frac|10|459}} (~2.18%) chance of being offered by piglins when bartering, in a stack size of 2–4.}}

{{History|console}}
{{History||xbox=TU5|xbone=CU1|ps=1.0|wiiu=Patch 1|switch=1.0.1|[[File:Ender Pearl JE2 BE1.png|32px]] Added ender pearls.}}
{{History||xbox=TU7|A teleporting feature has been added to ender pearls.}}
{{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Ender Pearl JE3 BE2.png|32px]] The texture of ender pearls has been changed.}}

{{History|new 3ds}}
{{History||1.7.10|[[File:Ender Pearl JE2 BE1.png|32px]] Added ender pearls.}}
{{History|foot}}

== Issues ==
{{issue list}}

== Trivia ==
*Ender pearls can be used to teleport/move through non-[[solid block]]s without suffocation and solid blocks by pressing against the blocks and using the ender pearl at the player's feet until the player goes through.<ref>{{bug|MC-2164}}</ref><ref>{{ytl|KA1UmxraeUg}}</ref>
*In ''Java Edition'', it is possible to spawn a thrown ender pearl using commands, but it does not teleport, unless it is assigned an owner.
*If the player throws an ender pearl and then dies before impact while the pearl is in a loaded chunk, the pearl disappears and the player is not teleported. Pearls in unloaded chunks do not disappear if their owner dies.
*If the player throws an ender pearl in Survival mode and changes to Creative mode before the pearl lands, the player is still teleported.
*The player is still teleported by throwing an ender pearl and entering [[the Nether]] before it lands. The pearl is not lost if an ender pearl is thrown into a [[nether portal]] and the player travels through the portal; the pearl lands and teleports the player as usual.
*If multiple ender pearls are thrown in succession, the player can be hurt only once from fall damage within about a one-second span.
*If a [[player]] dies from ender pearl teleportation, the [[death message]] says: "<player> hit the ground too hard".
*A thrown ender pearl faces toward the player in first-person view, while it appears rotated horizontal in [[third-person view]]. This is the case for all throwable items (ender pearl, [[egg]], [[snowball]], and all throwable [[potion]]s).
*Ender pearls and [[snowball]]s have the exact same range when fired. Therefore, snowballs can be used to predict the trajectory of ender pearls, or simply for practicing ender pearl throwing. This can be very helpful when the player has to throw ender pearls in dangerous environments, such as the Nether or the End.
*Despite the fact that ender pearls deal no damage to anything they're thrown at, provokable mobs (such as iron golems and piglins) will be provoked by the player if one is thrown at them.

== Gallery ==
<gallery>
Ender Pearl Suggestion.gif|The original suggestion image for teleporting with ender pearls.
Enderlake.png|Ender pearls were formerly found in [[water]], however endermen now teleport out to prevent damage.
</gallery>

== References ==
{{reflist}}

== See also ==
*[[The End]]
*[[Ender Dragon]]
*[[End Portal]]
*[[Enderman]]

{{Items}}
{{entities}}

[[cs:Endová perla]]
[[de:Enderperle]]
[[es:Perla de ender]]
[[fr:Perle de l'Ender]]
[[hu:Véggyöngy]]
[[ja:エンダーパール]]
[[ko:엔더 진주]]
[[nl:Enderparel]]
[[pl:Enderperła]]
[[pt:Pérola de ender]]
[[ru:Жемчуг Края]]
[[th:ไข่มุกเอนเดอร์]]
[[tr:Ender İncisi]]
[[uk:Перлина Краю]]
[[zh:末影珍珠]]</li><li>[[Bone Meal|Bone Meal]]<br/>{{Item
| image = Bone Meal.png
| renewable = Yes
| stackable =  Yes (64)
}}
'''Bone meal''' is a material that can be used as a fertilizer for most plants and fungi, as well as a crafting ingredient for [[dye]]s.

== Obtaining ==

=== Crafting ===

{{Crafting
|Bone
|Output=Bone Meal,3
|type=Material
|showname=0
|head=1
}}
{{Crafting
|Bone Block
|Output= Bone Meal,9
|type=Material
|foot=1
}}

=== Mob loot ===

==== Fish ====
All fish mob variants ([[cod]], [[salmon]], [[tropical fish]], and [[pufferfish]]) have a 5% chance to drop 1 bone meal upon death.{{only|java}} In [[Bedrock Edition]], they drop [[bones]] instead.

=== Composters ===

When a [[composter]] is completely filled, a single bone meal drops the next time the composter is {{ctrl|used}}.

=== Trading ===

[[Wandering trader]]s sell 3 bone meal for an [[emerald]].{{only|bedrock}}

== Usage ==

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

{{IN|bedrock}}, bone meal can be also used in [[banner pattern]]s:
{{banner crafting usage}}

=== Loom ingredient === 
{{Banner loom usage|Bone Meal}}

=== Dye ===
{{Dye usage}}

=== Fertilizer ===
Bone meal can also be used on the following [[plants]] to have a chance to increase their growth stage:
{| class="wikitable"
|+
!Plant
!Action
|-
|{{BlockLink|Wheat}}<br>{{BlockLink|Carrots}}<br>{{BlockLink|Potatoes}}
|The plant matures 2–5 growth stages.
|-
|{{BlockLink|Beetroots}}
|The plant has a 75% chance of growing to the next growth stage.
|-
|{{BlockLink|Bamboo}}
|Grows the [[bamboo]] by 1-2 stems.
|-
|{{BlockLink|Melon Stem|link=Melon seeds|text=Melon Seeds}}<br>{{BlockLink|Pumpkin Stem|link=Pumpkin seeds|text=Pumpkin Seeds}}
|The planted stem matures 2–5 growth stages. Bone meal affects only the stem's growth; it does not cause [[melon]]s or [[pumpkin]]s to sprout from a mature stem.
|-
|{{BlockLink|Saplings}}<br>{{BlockLink|Azalea}}<br>{{BlockLink|Flowering Azalea}}<br>{{BlockLink|Mangrove Propagule}} (not hanging)
|The [[sapling]] has a 45% chance of growing to the next growth stage, if possible. Saplings have two growth stages (with no visible difference between them) before growing into trees as the third stage. A tree cannot grow unless the sapling is planted in proper ground and sufficient space is available. Using bone meal on such an obstructed sapling with no chance of growing wastes the bone meal.
|-
|{{BlockLink|Sunflower}}s<br>{{BlockLink|Lilac}}s<br>{{BlockLink|Rose Bush}}es<br>{{BlockLink|Peony|Peonies}}
|The corresponding item form drops, without destroying the original plant.
|-
|{{BlockLink|Grass}}<br>{{BlockLink|Fern}}s<br>{{BlockLink|Seagrass}}
|A one-block-high tall [[grass]], [[fern]], or [[seagrass]] (that is on [[grass block]], [[dirt]], [[coarse dirt]], [[rooted dirt]], [[farmland]], [[podzol]], [[mycelium]], [[moss block]], [[mud]], or [[muddy mangrove roots]] (only exception is seagrass, will need to on a full surface)) grows into a two-block-high tall grass, fern or seagrass.
|-
|{{BlockLink|Mushrooms}}
|Has a 40% chance of growing into a {{EnvLink|huge mushroom}} if on [[grass block]], [[dirt]], [[coarse dirt]], [[rooted dirt]], [[farmland]], [[podzol]], [[mycelium]], [[moss block]], [[mud]], or [[muddy mangrove roots]].
|-
|{{BlockLink|Cocoa}}
|The cocoa plant matures 1 growth stage.
|-
|{{BlockLink|Sweet Berry Bush}}
|Grows every stage.
|-
|{{BlockLink|Sea Pickle}}
|If the [[sea pickle]] is on a [[coral block]] and in [[water]] at least 2 blocks deep, the sea pickle colony grows, and additional sea pickles generate nearby.
|-
|{{BlockLink|Sugar Cane}}{{only|bedrock|short=1}}
|The sugar cane grows to maximum height (three blocks tall).
|-
|{{BlockLink|Kelp}}
|The kelp plant grows by 1 block per bone meal used, up to its maximum height.
|-
|{{BlockLink|Flower|id=poppy}} (excluding wither roses){{only|bedrock|short=1}}
|One-block-high flowers make more flowers of the same type grow in the surrounding area.
|-
|{{BlockLink|Fungus|id=fungi}}
|Grows into [[huge fungi]], but only if on the respective [[nylium]].
|-
|{{BlockLink|Weeping Vines}}
|Grows the [[weeping vine]]s a few blocks downward.
|-
|{{BlockLink|Twisting Vines}}
|Grows the [[twisting vine]]s a few blocks upward.
|-
|{{BlockLink|Cave Vines}}
|Produces [[glow berries]] if the vine did not have any [[glow berries]] on it already.
|-
|{{BlockLink|Glow Lichen}}
|The [[glow lichen]] spreads to a random adjacent block.
|-
|{{BlockLink|Moss Block}}
|The [[moss block]] causes nearby [[stone]], [[cave vine]]s, and [[dirt]] to become moss blocks.
|-
|{{BlockLink|Big Dripleaf}}<br>{{BlockLink|Small Dripleaf}}
|A [[big dripleaf]] grows one block higher, and a [[small dripleaf]] becomes a big dripleaf.
|-
|{{BlockLink|Rooted Dirt}}
|Causes [[hanging roots]] to grow underneath the [[rooted dirt]] if there is space.
|-
|{{BlockLink|Mangrove Leaves}}
|Creates a hanging [[mangrove propagule]] under the [[mangrove leaves]].
|-
|{{BlockLink|Mangrove Propagule}} (hanging)
|The [[mangrove propagule]] matures 1 growth age.
|-
|{{BlockLink|Pink Petals}}
|Produces another pink petal in the block. If there are already four pink petals in the block, it will drop a pink petal as an item.
|-
|{{BlockLink|Torchflower Crop}}<br>{{BlockLink|Pitcher Crop}}
|Grows every stage.
|}

Bone meal does not affect:
* [[Cactus]]
* [[Vines]]
* [[Nether wart]]
* [[Sugar cane]]{{only|JE}}
* [[Chorus plant]]s, or other plants not listed above.

==== Wasting bone meal ====
Bone meal can be used on the following objects in the following situations, consuming it without any real effect:

* On [[grass]], [[fern]]s, and [[seagrass]] that do not have enough space to grow.<ref>{{bug|MC-125642}}</ref>
* On [[seagrass]] that doesn't have [[water]] above.
* On a [[dark oak sapling]] that is not in a group of four.<ref>{{bug|MC-168446}}</ref>
* On a [[mushroom]] that is not on a block that allows it to grow into a huge mushroom.<ref>{{bug|MC-173213}}</ref>
* On a [[sea pickle]] that is already in a group of four and has no valid locations to expand to.<ref>{{bug|MC-127995}}</ref>
* On a [[bamboo]] (not [[bamboo shoot]]) that is blocked in the way.
* On a [[sea pickle]] that is not on a [[coral block]].
* On a [[fungus]] that is not on its respective [[nylium]].
* Any plants that can't grow due to being block by the [[build limit]].

=== Creating new plants ===

If bone meal is {{ctrl|used}} on a [[grass block]]; [[tall grass]], [[grass]], [[flower]]s, and [[pink petals]] form on the targeted block and on random adjacent grass blocks in an 15×5×15{{only|java|short=1}}/7×5×7{{only|bedrock|short=1}} area centered on the targeted block. The flowers/pink petals that appear depend on the biome, meaning that in order to obtain specific flowers, the player must travel to biomes where the flowers are found naturally. See {{slink|Flower|Flower biomes}} for more information.

Using bone meal on a 2-block flower (rose bushes, sunflowers, lilacs or peonies) will cause one of the same type of flower to drop, without breaking the original. This is the only way to reproduce these flowers, since they cannot generate from using bone meal on grass blocks.

Using bone meal on a non-transparent block that is underwater generates [[seagrass]] on that block and surrounding blocks. Sometimes, if in a [[warm ocean]] biome, [[coral]] and [[coral fan]]s may have a chance to generate as well, and in Bedrock Edition, coral (not coral fan) can be generated in any biome. In order for this to work, there must be 2 water blocks above the block the bone meal is being used on, and the lower one must be non-flowing water.

Using bone meal on a [[sea pickle]] on a [[coral block]] creates sea pickles. This generates sea pickles up to 3 [[block]]s (of coral) away, so a 7+ × 7+ block (49+ blocks) of coral may be necessary, to return the most sea pickles per given bone meal attempt (more attempts grows them more numerously, exactly - including the range of it growing, like grass with heights on grass blocks - as coral and coral fans, though those others being non-solid blocks).

Using bone meal on [[netherrack]] adjacent to [[nylium]] converts the netherrack into nylium of the same type. If both crimson and warped nylium are adjacent to the netherrack that was applied with bone meal, there is a 50% chance that either type of nylium is created.

Using bone meal on [[nylium]] causes the corresponding [[roots]] and both types of [[fungi]] to appear on the nylium block and other nylium nearby, with the type of fungi matching the type of nylium being more common. In addition, using bone meal on the side of warped nylium creates [[nether sprouts]] and [[twisting vines]].

=== Farmer villagers ===
[[Villager]]s with the farmer profession can collect bone meal from a full [[composter]], with which they can make their crops grow faster.

== Sounds ==
{{edition|java}}:
{{Sound table
|sound=Bonemeal1.ogg
|sound2=Bonemeal2.ogg
|sound3=Bonemeal3.ogg
|sound4=Bonemeal4.ogg
|sound5=Bonemeal5.ogg
|subtitle=Bone Meal crinkles
|description=When bone meal is successfully used
|source=block
|id=item.bone_meal.use
|translationkey=subtitles.item.bone_meal.use
|volume=1.0
|pitch=1.0
|distance=16
|foot=1}}

{{edition|be}}:
{{Sound table
|type=bedrock
|sound=Bonemeal1.ogg
|sound2=Bonemeal2.ogg
|sound3=Bonemeal3.ogg
|sound4=Bonemeal4.ogg
|sound5=Bonemeal5.ogg
|description=When bone meal is successfully used
|source=block
|id=item.bone_meal.use
|volume=1.0
|pitch=0.9-1.1
|foot=1}}

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

{{edition|bedrock}}:
{{ID table
|edition=bedrock
|showaliasids=y
|shownumericids=y
|showforms=y
|notshowbeitemforms=y
|generatetranslationkeys=y
|displayname=Bone Meal
|spritetype=item
|nameid=bone_meal
|aliasid=dye / 15
|id=411
|form=item
|translationkey=item.dye.white.name
|foot=1}}

== History ==

{{History|java beta}}
{{History||1.2|[[File:Bone Meal JE1 BE1.png|32px]] Added bone meal.
|Bone meal can now only be applied to [[sapling]]s and [[wheat]].}}
{{History||1.6.6|Bone meal can now be applied on [[grass block]]s.}}
{{History||1.8|snap=Pre-release|Bone meal can now be used on [[mushroom]]s to make [[huge mushroom]]s, and the block the mushroom is on changes to [[dirt]].}}
{{History|||snap=Pre-release 2 ;)|Bone meal can now be applied on [[pumpkin seeds|pumpkin]] and [[melon seed]]s.}}
{{History|java}}
{{History||1.3.1|snap=12w19a|Bone meal can now be applied on [[cocoa bean]]s.}}
{{History|||snap=1.3|[[File:Bone Meal JE2 BE2.png|32px]] The texture of bone meal has been changed.}}
{{History||1.4.2|snap=12w34a|Bone meal can now be used to dye [[leather armor]] and [[tamed wolf]]'s collar.}}
{{History||1.4.6|snap=12w49a|Bone meal can now be [[crafted]] with [[gunpowder]] to create a [[firework star]].}}
{{History||1.5|snap=13w04a|Bone meal has been significantly nerfed.<br>
[[Wheat]], [[melon seeds|melon]] and [[pumpkin seed]]s, [[potato]]es and [[carrot]]s: one bone meal is now consumed for all seven stages of growth (melon and pumpkin seeds do not spawn right away).<br>
[[Sapling]]s: one bone meal is now consumed for each of the two growth stages, then it grows into a tree.<br>
[[Cocoa]]s: one bone meal is now consumed for each of the three stages of growth.
|Green [[particle]]s are now displayed when bone meal is used.
|Bone meal can now be used from [[dispenser]]s.}}
{{History|||snap=13w05a|The balancing of bone meal has been adjusted. Growing a plant to its last state now takes on average 2-5 uses of bone meal (results vary from plant to plant).<ref>https://web.archive.org/web/20220921040940/https://imgur.com/a/gOngk</ref>}}
{{History||1.6.1|snap=13w19a|Bone meal can now be used to craft white [[stained clay]].}}
{{History||1.7.2|snap=13w36a|The [[flower]]s generated when using bone meal on grass blocks is now biome dependent.}}
{{History|||snap=13w41a|Bone meal can now be used to craft white [[stained glass]].}}
{{History||1.8|snap=14w30a|Added [[banner]]s, which can be dyed with [[bone meal]].}}
{{History||1.10|snap=16w20a|Bone meal can now be used to craft [[bone block]]s.}}
{{History||1.11|snap=16w39b|Bone meal can now be used to dye [[shulker box]]es.}}
{{History||1.12|snap=17w06a|Bone meal can now be used to craft white [[concrete powder]].}}
{{History||1.13|snap=17w47a|The different data values for the <code>dye</code> ID have been split up into their own IDs.
|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 351.}}
{{History|||snap=18w07a|Bone meal can now be used underwater to create [[seagrass]].}}
{{History|||snap=18w14b|Bone meal can now be used for spreading [[sea pickle]]s.}}
{{History||1.13.1|snap=18w31a|Bone meal used in [[water]] of warm ocean biomes now has a chance of growing [[coral]].
|[[Cod]], [[salmon]], [[tropical fish]], and [[pufferfish]] now have a chance of dropping bone meal upon death.}}
{{History|||snap=18w32a|Bone meal used in [[water]] of warm ocean biomes now has a chance of growing [[coral fan]]s.}}
{{History||1.14|snap=18w43a|Bone meal can now used to craft [[white dye]].
|Bone meal can no longer be used as a [[dye]].
|All of the dye-related functions and crafting recipes of bone meal (except bone blocks) have been transferred to white dye.
|[[File:Bone Meal JE3 BE3.png|32px]] The texture of bone meal has been changed.
|Bone meal can now be used on [[bamboo]] and [[bamboo shoot]].}}
{{History|||snap=19w03a|Bone meal can now be obtained from [[composter]]s.}}
{{History||1.16|snap=20w06a|Bone meal can now be used to grow [[fungi]] into [[huge fungi]].
|Bone meal can now be used to spread [[nylium]] onto netherrack.}}
{{History|||snap=20w09a|Using bone meal to grow fungi now works only on the respective [[nylium]].}}
{{History|||snap=20w11a|Bone meal can now grow [[kelp]], [[weeping vines]], and [[twisting vines]].}}
{{History|||snap=20w12a|Bone meal can now be used to grow [[roots]], [[fungi]], and [[nether sprouts]] on nylium.}}
{{History|||snap=20w13a|Farmers can now use bone meal to grow crops.}}
{{History||1.17|snap=21w03a|Bone meal can now be used to spread [[glow lichen]]s.}}
{{History|||snap=21w05a|Bone meal can now be used on [[moss block]]s, [[small dripleaf]], [[big dripleaf]], and [[cave vines]].}}
{{History|||snap=21w11a|Bone meal can now be used on [[rooted dirt]].}}
{{History|||snap=21w15a|Bone meal now makes a sound when used.}}
{{History|||snap=21w16a|Moss patches obtained from fertilizing moss blocks contain less vegetation and are now smaller and more irregular in shape.
|Bone meal can now be used on [[azalea]] and [[flowering azalea]].}}
{{History||1.19|snap=22w11a|Bone meal can now be used on [[mangrove propagule]]s and [[mangrove leaves]].}}
{{History||1.20<br>(Experimental)|link=1.19.4|snap=23w07a|Bone meal can now be used on [[pink petals]] and [[torchflower crop]]s.|Using bone meal on [[cherry grove]]s now have a chance to generate [[pink petal]]s.}}
{{History||1.20|snap=23w12a|Bone meal can now be used on [[pitcher crop]]s.}}

{{History|pocket alpha}}
{{History||v0.3.0|[[File:Bone Meal JE1 BE1.png|32px]] Added bone meal. It is currently unobtainable and serves no purpose.}}
{{History||v0.3.3|Bone meal can now be crafted from bones.
|Bone meal can now be applied to grass blocks and saplings.}}
{{History||v0.4.0|Added the first [[crop]]s, which bone meal can be applied to.}}
{{History||v0.8.0|snap=build 1|[[File:Bone Meal JE2 BE2.png|32px]] The texture of bone meal has been changed.
|Bone meal no longer instantly grows [[crop]]s to full size.
|Bone meal can now be used to craft white [[wool]].}}
{{History|||snap=build 5|[[Pumpkin]] and [[melon]] stems now grow by only one stage when bone meal is used.
|Some [[flower]]s now spawn certain other flowers when bone meal is used on them.
|Bone meal can now grow [[fern]]s and [[tall grass]] in [[survival]] and [[creative]].
|Bone meal can now grow [[sugar cane]]s to maximum height.}}
{{History||v0.9.0|snap=build 11|Bone meal can now be used to dye tamed [[wolf]] collars.}}
{{History||v0.14.0|snap=build 1|Bone meal can now be used from [[dispenser]]s.
|Bone meal can now be used to dye [[water]] in [[cauldron]]s.}}
{{History|pocket}}
{{History||1.0.0|snap=alpha 0.17.0.1|Bone meal can now be used to dye [[shulker]]s.}}
{{History||1.1.0|snap=alpha 1.1.0.0|Bone meal can now be used to craft white [[concrete powder]], white [[bed]]s and white [[shulker box]]es.}}
{{History||1.1.3|snap=alpha 1.1.3.0|Bone meal can now be used to craft [[bone block]]s.}}
{{History|bedrock}}
{{History||1.2.0|snap=beta 1.2.0.2|Bone meal can now be used to craft white [[stained glass]].
|Bone meal can now be used to craft [[firework star]]s.
|Bone meal can now be used to create [[banner]] patterns.}}
{{History||1.4.0|snap=beta 1.2.14.2|Bone meal can now be used underwater for growing [[seagrass]] and [[coral]].}}
{{History|||snap=beta 1.2.20.1|Bone meal can now be used for spreading [[sea pickle]]s.
|Bone meal can now be used to craft white [[balloon]]s and white [[glow stick]]s.}}
{{History||1.8.0|snap=beta 1.8.0.8|Bone meal can now be used to grow [[bamboo]].}}
{{History|||snap=beta 1.8.0.10|Bone meal can now be used to craft [[white dye]].}}
{{History||1.10.0|snap=beta 1.10.0.3|Bone meal are now sold by [[wandering trader]]s.
|[[File:Bone Meal JE3 BE3.png|32px]] The texture of bone meal has been changed.}}
{{History||1.11.0|snap=beta 1.11.0.1|Bone meal can now be obtained from [[composter]]s.}}
{{History||1.16.0|snap=beta 1.16.0.51|Bone meal can now grow [[fungus|fungi]] into [[huge fungi]].
|Bone meal can now be used to turn [[netherrack]] into [[nylium]].
|Bone meal can now be used to grow [[roots]], [[fungi]], and [[nether sprouts]] on nylium.}}
{{History||1.16.100|snap=beta 1.16.100.56|The ID of bone meal has been changed from <code>dye/15</code> to <code>bone_meal</code>.}}
{{History||1.16.210|snap=beta 1.16.210.51|Bone meal used in [[water]] now has a chance of growing [[coral fan]]s.}}
{{History||1.16.220|snap=beta 1.16.220.52|Bone meal can now be used on [[moss block]]s, [[small dripleaf]], [[big dripleaf]], [[cave vines]] and [[rooted dirt]].}}
{{History||1.17.0|snap=beta 1.16.230.50|Bone meal can now be used to spread [[glow lichen]]s.}}
{{History|||snap=beta 1.16.230.54|Bone meal can be used to grow [[azalea]]s into azalea trees.}}
{{History|||snap=beta 1.17.0.50|Bone meal now makes a sound when used.}}

{{History|console}}
{{History||xbox=TU1|xbone=CU1|ps=1.00|wiiu=Patch 1|switch=1.0.1|[[File:Bone Meal JE1 BE1.png|32px]] Added bone meal.}}
{{History||xbox=TU19|xbone=CU7|ps=1.12|Bone meal no longer instantly grows [[crop]]s to full size.}}
{{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Bone Meal JE3 BE3.png|32px]] The texture of bone meal has been changed.}}

{{History|new 3ds}}
{{History||0.1.0|[[File:Bone Meal JE2 BE2.png|32px]] Added bone meal.}}
{{History|foot}}

== Issues ==

{{issue list}}

== Trivia ==

* Bone meal can be used on the sides or bottom of a [[grass block]], as well as on a grass block with [[plant]]s already on top of it.
* Regardless of if it succeeds in fertilizing, bone meal makes green sparkles. However, like smoke from a [[torch]], the sparkles appear only if the [[player]] has [[particles]] set All or Decreased.
* In real life, [[Wikipedia:bone meal|bone meal]] is used as a fertilizer to provide nitrogen and phosphorus to plants.

==Gallery==

<gallery>
File:Bone Meal On Grass.png|Bone meal used on [[grass block]]s.
</gallery>

== See also ==

* [[Farming]]

== References ==
{{reflist}}

{{Items}}

[[Category:Dyes]]
[[Category:Plants]]
[[Category:Renewable resources]]

[[cs:Kostní moučka]]
[[de:Knochenmehl]]
[[es:Polvo de hueso]]
[[fr:Poudre d'os]]
[[hu:Csontliszt]]
[[ja:骨粉]]
[[ko:뼛가루]]
[[nl:Beendermeel]]
[[pl:Mączka kostna]]
[[pt:Farinha de osso]]
[[ru:Костная мука]]
[[th:ผงกระดูก]]
[[zh:骨粉]]</li></ul>

beta 1.16.210.56

Added pointed dripstone.

However, this is the history section for goats:

Bedrock Edition
1.16.200 {{Extension DPL}}<ul><li>[[Bed\|Bed]]<br/>{{Block \| image = White Bed (N).png \| extratext = View [[#Gallery\|all renders]] \| transparent = Yes \| tntres = 25 \| hardness = 4 \| light = No \| tool = any \| renewable = Yes \| stackable = No \| flammable = No \| lavasusceptible = {{jebe\|Yes\|No}} }} A '''bed''' is a [[Dye\|dyeable]] [[block]] that allows a player to sleep and to reset their [[spawn]] point to within a few blocks of the bed in the [[Overworld]]. If the bed is obstructed or removed, the player spawns at the default world spawning location. == Obtaining == === Natural generation === ;Igloo A red bed naturally generates in each [[igloo]]. ;Village Beds of various colors generate in [[village]] houses, depending on the specific structure and [[biome]]: * [[Desert]] village houses have cyan, green, or lime beds. * [[Plains]] village houses have white or yellow beds. * [[Savanna]] village houses have orange, red, or yellow beds. * [[Snowy taiga]]{{only\|bedrock\|short=1}} and [[taiga]] village houses have blue or purple beds. * [[Snowy tundra]] village houses have blue, red, or white beds. === Breaking === Beds can be mined with any [[tool]], or without a tool.<ref>{{bug\|MC-192722\|\|Beds have no assigned tool}}</ref> {{breaking row\|horizontal=1\|Bed\|sprite=red-bed\|any}} A bed also drops itself as an item when pushed by a [[piston]]. === Crafting === {{Crafting \|head=1 \|showname=0 \|showdescription=1 \|A2=Matching Wool \|B2=Matching Wool \|C2=Matching Wool \|A3=Any Planks \|B3=Any Planks \|C3=Any Planks \|Output= Matching Bed \|type=Decoration block \|description=The wool color must match. The planks can be different. }} <!--recipe removed {{Crafting \|showdescription=1 \|White Bed \|Matching Colored Dye \|Output= Matching Dyed Bed \|type=Decoration block \|description=White beds can be re-dyed using dyes.{{only\|java}}{{until\|JE 1.20}} }}--> {{Crafting \|showdescription=1 \|Any Bed \|Matching Dye \|Output= Matching Bed \|type=Decoration block \|description=A bed of any color can be re-dyed using dyes. }} {{Crafting \|showdescription=1 \|Any Dyed Bed \|Bleach \|Output=White Bed \|type=Decoration block \|description=This removes the color from the bed.{{only\|bedrock\|education}} \|foot=1 }} <div style="display:none"> <!-- This is so the pre-Village & Pillage dyes can have dye-related crafting recipes show on their respective pages. They don't need to be displayed on this page because they already intuitively list "Any Matching Dye". --> {{Crafting \|showdescription=1 \|Any Bed \|Bone Meal; Lapis Lazuli; Cocoa Beans; Ink Sac \|Output=White Bed; Blue Bed; Brown Bed; Black Bed \|type=Decoration block \|description={{only\|bedrock\|education}} }} </div> === Trading === Journeyman-level shepherd villagers sell 1 of 16 beds for 3 [[emerald]]s as part of their trades. == Usage == === Sleeping === [[File:Sleep Animation.gif\|240px\|thumb\|Player falling asleep.]] Beds are used by pressing the {{control\|use item}} button while looking at the bed. A player sleeps by {{control\|using\|using}} a bed during a [[thunderstorm]], or at [[night]] (between 12542 and 23459 ticks in clear weather, when stars appear in the sky, or between 12010 and 23991 ticks in rainy weather). Players can sleep during a thunderstorm even if they are in a biome where it does not rain (i.e. Desert). Attempting to use a bed at any other time results in the message "You can sleep only at night or during thunderstorms"{{only\|java\|short=1}} or "You can only sleep at night".{{only\|bedrock\|short=1}} A player sleeps in a bed for 101 in-game [[tick]]s, or 5.05 seconds before the time skips to the next day. Sleeping in a bed with the {{cmd\|gamerule doDaylightCycle}} set to <code>false</code> results in the player being kicked out of the bed after the 101 ticks, but does not change time of the world to day. Sleeping in a bed is possible only in the [[Overworld]]. Attempting to sleep in a bed in [[the Nether]], [[the End]], and [[custom dimension]]s in which they are disabled causes it to [[explosion\|explode]] and set [[fire]] to surrounding blocks; unless {{cmd\|gamerule respawnBlocksExplode}}{{only\|bedrock}} is set to {{cd\|false}}.<ref>{{bug\|mcpe-28723}} – "Exploding bed in the Nether" resolved as "Works As Intended". This is referenced {{in\|je}} when a player is killed by "Intentional Game Design". </ref> The explosion has power 5, which is stronger than [[TNT]] (4), but not as strong as a charged [[creeper]] or [[End Crystal\|end crystal]] (6). The explosion centers on the head part of the bed. [[Villager]]s can sleep normally in any dimension without the bed being blown up.<ref>{{bug\|MC-146515\|\|\|WAI}}</ref> Upon death from a bed explosion, the [[death messages\|message]] "'''(Player) was killed by [Intentional Game Design]'''" appears. The player must be close to the bed to sleep. If the player is close enough to click on the bed, but not close enough to sleep in it, the message "You may not rest now, the bed is too far away"{{only\|java\|short=1}}/"Bed is too far away"{{only\|bedrock\|short=1}} appears. A player must be within 2 blocks of the bed {{in\|JE}} or 3 blocks {{in\|BE}} to use the bed. If a "monster" is within 8 blocks of the bed horizontally (in the X- and Z-axis), and 5 blocks vertically (in the Y-axis), the message "You may not rest now, there are monsters nearby" appears and the player is prevented from sleeping until the monsters leave or are killed. Most hostile mobs, as well as some neutral mobs prevent players from sleeping, as shown in the table below. {\| class="wikitable mw-collapsible" !Mob !Prevent the player from sleeping \|- \|{{EntityLink\|Blaze}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Chicken Jockey}} \|{{Tc\|partial\|when hostile{{Only\|Java\|short=1}}/Yes{{Only\|Bedrock\|short=1}}}} \|- \|{{EntityLink\|Creeper}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Drowned}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Endermite}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Enderman}} \|{{Tc\|partial\|when hostile}} \|- \|{{EntityLink\|Ender Dragon}} \|{{Tc\|no}} \|- \|{{EntityLink\|Evoker}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Ghast}} \|{{Tc\|no}} \|- \|{{EntityLink\|Giant}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Guardian}}, {{EntityLink\|Elder Guardian}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Hoglin}} \|{{Tc\|no}} \|- \|{{EntityLink\|Illusioner}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Killer Bunny}} \|{{Tc\|no}} \|- \|{{EntityLink\|Magma Cube}} \|{{Tc\|partial\|no{{Only\|Java\|short=1}}/Yes{{Only\|Bedrock\|short=1}}}} \|- \|{{EntityLink\|Piglin}} \|{{Tc\|no}} \|- \|{{EntityLink\|Piglin Brute}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Pillager}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Phantom}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Ravager}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Shulker}} \|{{Tc\|no}} \|- \|{{EntityLink\|Silverfish}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Skeleton}}, {{EntityLink\|Skeleton Horseman}}, {{EntityLink\|Stray}}, {{EntityLink\|Wither Skeleton}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Spider}}, {{EntityLink\|Cave Spider}}, {{EntityLink\|Spider Jockey}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Slime}} \|{{Tc\|partial\|no{{Only\|Java\|short=1}}/Yes{{Only\|Bedrock\|short=1}}}} \|- \|{{EntityLink\|Vex}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Vindicator}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Warden}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Witch}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Wither}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Zoglin}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Zombie}}, {{EntityLink\|Zombie Villager}}, {{EntityLink\|Husk}} \|{{Tc\|yes}} \|- \|{{EntityLink\|Zombified Piglin}} \|{{Tc\|partial\|when hostile{{Only\|Java\|short=1}}/Yes{{Only\|Bedrock\|short=1}}}} \|- \|} {{notelist}} If the player has not entered a bed and didn't die for 3 in-game days, [[phantom]]s can spawn unless {{cmd\|gamerule doInsomnia}} is set to {{cd\|false}}. {{in\|java}}, this can be verified by checking if the "Time Since Last Rest" [[statistic]] is greater than 1.00 h. A hostile mob can wake a player that is sleeping. The player also cannot sleep in a bed occupied by another player, resulting in the message, "This bed is occupied". A player can, however, sleep in a bed being used by a villager. The player may first wake the villager (pressing {{control\|use}} on the villager) and then quickly enter the bed before the villager can lie down again. The villager reclaims the bed after the player wakes. The villager is kicked out of its bed when a player attempts to sleep there. A player also cannot sleep while on fire, while poisoned, or while starving. If all sleeping requirements are met and the player enters a bed, the player is positioned in the bed. The player falls asleep as the screen fades to black. {{IN\|bedrock}}, the sleeping animation slowly lowers the player into bed. Once all players in a world are asleep, after 5 seconds (100 ticks) the time of day changes to sunrise. (time 0) During this time, the chat window is focused, and the player can leave the bed by clicking the {{btn\|Leave Bed}} button. [[Waterlogging\|Waterlogged]] beds{{only\|bedrock}} cannot be slept in unless the player or villager has the {{EffectLink\|Water Breathing}} or {{EffectLink\|Conduit Power}} status effects. Attempting to use a waterlogged bed otherwise does not display any message.<ref>{{bug\|MCPE-35802}}</ref> Beds displaying an error above the hotbar is a feature exclusive to beds; other blocks that cannot be used do not display such a message.<ref>{{bug\|MC-160479}} resolved as "Works As Intended"</ref> If there are two or more blocks of space above the bed, then the player can wake up on the bed. If there is less than two blocks above the bed and there is room on the side, then the player wakes up on the side of the bed. If there is no space on the side of the bed and there is less than two blocks above the bed, then the player still wakes up on top of the bed, but suffocates if it's a solid block. Villagers always wake up on top of the bed, meaning they can suffocate if there isn't enough room above the bed. ====Passing the night==== Sleeping changes the [[daylight cycle\|time of day]] to sunrise and resets the [[weather]] cycle, changing the weather to clear conditions. {{IN\|JE}}, the weather cycle is only reset if it is currently raining or snowing. The player wakes up next to the bed, facing the bed. Sleeping does not accelerate processes that take place over time such as the growth of [[crops]] or [[smelting]]. If {{cmd\|gamerule doDaylightCycle}} is <code>false</code>, the player instead wakes up in the night. To skip the night in multiplayer, all players in the [[Overworld]] must be in bed at the same time. Pressing the {{btn\|Leave Bed}} button is not necessary in this case. The percentage of players that need to sleep to skip the night can be customized with the game rule {{cd\|playersSleepingPercentage}}. Villagers are unable to skip the night by sleeping in beds, unlike players. If the bed is destroyed while the player is in it, due to for example an explosion or by another player, the player wakes prematurely and the night does not pass. ====Setting the spawn point==== Once a player has entered a bed (or right clicked the bed during daytime), their spawn point is set to the location of that bed. {{IN\|java}}, multiple players can set their spawn point on a single bed. {{IN\|bedrock}}, the last player to use a specific bed is the only player who can respawn there, and players who had previously slept there respawn at the world spawn. {{ctrl\|Using}} a bed in the daytime likewise sets the spawn point, without actually entering the bed. When a bed explodes, it does not set the spawn point. The message "Respawn point set" is displayed in chat when the respawn point is successfully changed. The check for a bed is made only when the player respawns. This means that the bed can be destroyed and replaced or even reoriented, but as long as there is a bed present in the same location, the player can respawn there. If a player's bed is absent, or if the area around the bed is made unsuitable for respawning (see below), a message is displayed saying ''You have no home bed or respawn anchor, or it was obstructed''{{only\|je}}/''Your home bed was missing or obstructed''{{only\|be}}, and the player respawns at the [[Spawn#World spawn\|world spawn]] point. When choosing where to respawn the player, the northwesternmost (lowest X- and Z-coordinates) location of the seven blocks adjacent to the head of the bed is chosen first. If this location is obstructed, the next choice is to its south (+Z), rather than the east (+X). Only when all seven locations around the head are obstructed are the three remaining ones adjacent to the foot then to be considered. For a location to be unobstructed, the block at the level of the bed must be air or non-solid (e.g. torches, but not glass) and there must be a space with a solid block below it and two non-colliding blocks for the player to stand in 0-2 blocks below the bed. It does not matter if the bed itself has blocks above it. Putting a slab one block above a bed can act as a two block tall space, as the bed is half a block tall. The bed never spawns the player on or directly below itself even if all other locations are obstructed. If a bed is obstructed, the player's spawn point is cleared after they respawn. That is, even if the bed is subsequently made usable again, the player continues to respawn at the world spawn until interacting with the bed again. Specifically, when interacting with it, the location of the ''head'' of the bed is saved as the spawn point, and if a bed is in that space (whether it is the foot or the head) then the respawn works. This can be observed by reorienting the bed with its head in the same location. Interacting with it does not produce a "Respawn point set" message as the game doesn't change the saved spawn point. If a bed is reoriented so that its foot is in this space, it still functions on the next respawn, but it can also be interacted with to update the spawn point to the new head of the bed and cause a "Respawn point set" message. Attempting the reverse, reorienting the bed so that it overlaps the original location of the foot, results in a respawn at world spawn. However, the location of the foot of the bed is also saved. If the bed is moved so that part of it overlaps the original location of the head, it can be observed that the same locations need to be obstructed to stop spawning. It is possible to respawn 2 blocks away from the bed this way. === Bouncing=== Falling onto a bed bounces the player with 66% strength – the bouncing-up velocity is 66% of the impact velocity. The player also takes 50% of normal fall damage. Baby villagers bounce on beds during the day. If the player is falling while sleeping requirements are met, and presses {{control\|use}} on a bed within reach before hitting the ground, the fall damage is delayed until the player wakes. A player can bounce on a bed while another player or villager is sleeping on it without waking the player or the villager up. Villagers can be pushed onto beds, as the bed is half a block tall. === Curing=== Each bed in the vicinity of a zombie villager has a chance to speed up the [[Zombie_Villager#Curing\|process of curing the zombie villager]]. Iron bars (such as in a prison cell) also have this effect. === Placement=== Beds require two blocks of floor space. Placement requires at least 2 blocks from the player's facing direction. When placed, the foot of the bed is placed on the block selected and the head of the bed on the block farther away from the player. {{IN\|bedrock}}, beds require solid blocks below them when placed. However, the bed remains in place if its supporting blocks are later removed. {{IN\|java}}, beds do not require supporting blocks and can be placed anywhere, provided there is enough room. ==Sounds == ===Generic=== {{Sound table/Block/Wood}} ===Unique=== {{edition\|java}}: {{Sound table \|sound=Explosion1.ogg \|sound2=Explosion2.ogg \|sound3=Explosion3.ogg \|sound4=Explosion4.ogg \|subtitle=Explosion \|source=block \|description=When a player attempts to sleep while not in the Overworld \|id=entity.generic.explode \|translationkey=subtitles.entity.generic.explode \|volume=4.0 \|pitch=0.56-0.84 \|distance=16 \|foot=1}} {{edition\|bedrock}}: {{Sound table \|type=bedrock \|sound=Explosion1.ogg \|sound2=Explosion2.ogg \|sound3=Explosion3.ogg \|sound4=Explosion4.ogg \|source=block \|description=When a player attempts to sleep while not in the Overworld \|id=random.explode \|volume=4.0 \|pitch=1.0 \|foot=1}} ==Data values== ===ID=== {{edition\|java}}: {{ID table\| \|edition=java \|showblocktags=y \|showitemtags=y \|showforms=y \|generatetranslationkeys=y \|displayname=White Bed \|spritetype=block \|nameid=white_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Orange Bed \|spritetype=block \|nameid=orange_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Magenta Bed \|spritetype=block \|nameid=magenta_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Light Blue Bed \|spritetype=block \|nameid=light_blue_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Yellow Bed \|spritetype=block \|nameid=yellow_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Lime Bed \|spritetype=block \|nameid=lime_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Pink Bed \|spritetype=block \|nameid=pink_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Gray Bed \|spritetype=block \|nameid=gray_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Light Gray Bed \|spritetype=block \|nameid=light_gray_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Cyan Bed \|spritetype=block \|nameid=cyan_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Purple Bed \|spritetype=block \|nameid=purple_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Blue Bed \|spritetype=block \|nameid=blue_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Brown Bed \|spritetype=block \|nameid=brown_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Green Bed \|spritetype=block \|nameid=green_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Red Bed \|spritetype=block \|nameid=red_bed \|blocktags=beds \|itemtags=beds}} {{ID table \|displayname=Black Bed \|spritetype=block \|nameid=black_bed \|blocktags=beds \|itemtags=beds \|foot=1}} {{ID table \|displayname=Block entity \|spritename=beds \|spritetype=block \|nameid=bed \|foot=1}} {{edition\|bedrock}}: {{ID table \|edition=bedrock \|firstcolumnname=Bed \|shownumericids=y \|showforms=y \|generatetranslationkeys=y \|displayname=Block \|spritename=Beds \|spritetype=block \|nameid=bed \|id=26 \|form=block \|itemform=item.bed}} {{ID table \|displayname=Item \|spritename=bed \|spritetype=item \|nameid=bed \|id=418 \|form=item \|translationkey=item.bed.black.name,item.bed.red.name,item.bed.green.name,item.bed.brown.name,item.bed.blue.name,item.bed.cyan.name,item.bed.silver.name,item.bed.gray.name,item.bed.pink.name,item.bed.lime.name,item.bed.yellow.name,item.bed.lightBlue.name,item.bed.magenta.name,item.bed.orange.name,item.bed.white.name \|foot=1}} {{ID table \|notnamespaced=y \|displayname=Block entity \|spritename=beds \|spritetype=block \|nameid=Bed \|foot=1}} ===Metadata=== {{see also\|Data values}} {{IN\|be}}, bed items use the following data values: {{/DV}} ===Block states=== {{see also\|Block states}} {{/BS}} ===Block data=== A bed has a block entity associated with it that holds additional data about the block. {{el\|java}}: {{see also\|Block entity format}} {{/BE}} {{el\|bedrock}}: : See [[Bedrock Edition level format/Block entity format]]. ==Advancements== {{load advancements\|Sweet Dreams}} ==History== ''For a more in-depth breakdown of changes to textures and models, including a set of renders for each state combination, see [[/Asset history]]'' {{History\|java beta}} {{History\|\|November 26, 2011\|link={{tweet\|jeb\|140410431394160640}}\|Originally, [[crying obsidian]] was intended to act as a block to reset spawn points, until beds were introduced.}} {{History\|\|1.3\|[[File:Red Bed JE1 BE1.png\|32px]] [[File:Red Bed (item) JE1 BE1.png\|32px]] Added beds. \|The only color for beds is red. \|Beds can currently be crafted using any color combination of wool. \|Sleeping in an area potentially exposed to monsters can cause [[player]]s to wake up early, with a [[skeleton]] or [[zombie]] spawned next to them. \|Trying to sleep in a bed in [[the Nether]] does nothing.}} {{History\|\|1.4\|Sleeping in a bed now resets the player's spawn position, though it does not work for most users. The spawn point unintentionally changes only if ''Leave Bed'' is clicked and the function is limited to [[multiplayer]].}} {{History\|\|1.4_01\|Beds now act as a respawn point as intended.}} {{History\|\|1.6\|snap=Test Build 3\|Trying to sleep in a bed in the Nether now causes the bed to [[explosion\|explode]].}} {{History\|\|1.7\|As blocks now pull textures from the expected places for model application, this has resulted in the bed texture shifting downward in <samp>[[terrain.png]]</samp>. No visual difference has resulted for the actual bed.}} {{History\|java}} {{History\|\|1.0.0\|snap=Beta 1.9 Prerelease 4\|Bed explosions in the Nether now light nearby blocks on fire.}} {{History\|\|\|snap=Beta 1.9 Prerelease 5\|The bottom textures of beds have been changed to the texture of the new [[oak]] planks from [[File:Red Bed JE1 (facing NWU).png\|32px]] to [[File:Red Bed JE2 BE1 (facing NWU).png\|32px]].}} {{History\|\|\|snap=Beta 1.9 Prerelease 6\|Beds no longer spawn monsters. Instead, trying to sleep when monsters are around displays a message saying ''You may not rest now, there are monsters nearby''.}} {{History\|\|1.2.4\|snap=release\|[[Cat]]s while in standing position now purposely go and sit on beds. \|[[Spruce]], [[birch]], and [[jungle tree\|jungle]] planks can now be used to craft beds.}} {{History\|\|1.5\|snap=?\|Beds now check their [[biome]] for detonation rather than just their dimension.}} {{History\|\|1.7.2\|snap=1.7.1\|[[Acacia]] planks and [[dark oak]] planks can now be used to craft beds.}} {{History\|\|1.8\|snap=14w29a\|Beds now display the cracking animation on top and bottom.}} {{History\|\|\|snap=14w33a\|Beds now make [[sound]]s when placed, and play logical sounds when stepped on and [[breaking\|broken]].<ref>{{bug\|MC-66347\|\|Beds make incorrect sounds\|Fixed}}</ref>}} {{History\|\|1.9\|snap=15w43a\|Bed now generates inside [[igloo]]s.}} {{History\|\|1.11\|snap=16w32a\|The messages "You can only sleep at night", "You may not rest now, there are monsters nearby", and "This bed is occupied" now appear on top of the hotbar, the place that the message "Press <whatever your sneak key is> to dismount" also appears when the player is riding a [[mob]].}} {{History\|\|\|snap=16w33a\|If the player is close enough to click on the bed, but not close enough to sleep in it, the message "You may not rest now, the bed is too far away" is now displayed.}} {{History\|\|1.12\|snap=17w06a\|Neutral [[zombie pigmen]] no longer prevent the player from sleeping in a bed.}} {{History\|\|\|snap=March 13, 2017\|slink={{tweet\|jeb_\|841311279784591361}}\|[[Jeb]] mentions colored beds for [[Java Edition 1.12\|1.12]].}} {{History\|\|\|snap=17w15a\|[[File:White Bed JE1.png\|32px]] [[File:Light Gray Bed JE1.png\|32px]] [[File:Gray Bed JE1.png\|32px]] [[File:Black Bed JE1.png\|32px]] [[File:Brown Bed JE1.png\|32px]] [[File:Orange Bed JE1.png\|32px]] [[File:Yellow Bed JE1.png\|32px]] [[File:Lime Bed JE1.png\|32px]] [[File:Green Bed JE1.png\|32px]] [[File:Cyan Bed JE1.png\|32px]] [[File:Light Blue Bed JE1.png\|32px]] [[File:Blue Bed JE1.png\|32px]] [[File:Purple Bed JE1.png\|32px]] [[File:Magenta Bed JE1.png\|32px]] [[File:Pink Bed JE1.png\|32px]] [[Dye]]d beds have been added. \|The "Bed" has been renamed to "Red Bed". \|Beds can now only be crafted using wool of the same color. \|[[File:Red Bed JE2.png\|32px]] The texture of red beds has been changed. The top of the beds are no longer mirrored. <!--- the numbers appear out of order but it is correct since it orders all beds in the current order in the Java Creative inventory ---> \|{{Sprite\|pos=1\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=9\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=8\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=16\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=13\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=15\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=2\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=5\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=6\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=14\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=10\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=4\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=12\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=11\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=3\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=7\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} Beds now appear 3D in the [[inventory]]. \|[[File:Red Bed JE3 (facing NWU).png\|32px]] Beds now have 3D legs.<ref>{{bug\|MC-11963\|\|bed hind legs not rendered\|Fixed}}</ref> \|Beds have been made bouncy, though they do not completely reduce all [[fall damage]]. \|Beds are now a [[block entity]].}} {{History\|\|\|snap=17w17a\|[[File:Red Bed JE4 BE2 (facing NWU).png\|32px]] The four legs of a bed are now each textured separately, and their [[model]] is different. \|[[File:White Bed JE2 BE2.png\|32px]] [[File:Light Gray Bed JE2 BE2.png\|32px]] [[File:Gray Bed JE2 BE2.png\|32px]] [[File:Black Bed JE2 BE2.png\|32px]] [[File:Brown Bed JE2 BE2.png\|32px]] [[File:Red Bed JE3 BE2.png\|32px]] [[File:Orange Bed JE2 BE2.png\|32px]] [[File:Yellow Bed JE2 BE2.png\|32px]] [[File:Lime Bed JE2 BE2.png\|32px]] [[File:Green Bed JE2 BE2.png\|32px]] [[File:Cyan Bed JE2 BE2.png\|32px]] [[File:Light Blue Bed JE2 BE2.png\|32px]] [[File:Blue Bed JE2 BE2.png\|32px]] [[File:Purple Bed JE2 BE2.png\|32px]] [[File:Magenta Bed JE2 BE2.png\|32px]] [[File:Pink Bed JE2 BE2.png\|32px]]<br> <!--- the numbers appear out of order but it is correct since it orders all beds in the current order in the Java Creative inventory ---> {{Sprite\|pos=17\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=25\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=24\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=32\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=29\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=31\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=18\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=21\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=22\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=30\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=26\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=20\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=28\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=27\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=19\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} {{Sprite\|pos=23\|image=Bed Icons 1.12.png\|size=32\|sheetsize=512}} The textures of beds have now also been changed.}} {{History\|\|1.13\|snap=17w47a\|Beds now require solid blocks below them, or they break into an item. Previously, a bed needed to be placed on solid blocks, but the blocks could later be removed.}} {{History\|\|\|snap=18w07a\|Sleeping in a bed is now important to keep [[phantom]]s from spawning.}} {{History\|\|\|snap=18w20a\|Players in [[Creative]] mode can now sleep even if monsters are nearby.}} {{History\|\|\|snap=18w22a\|Beds no longer require supporting blocks below them; they do not break into an [[item (entity)\|item]] if said blocks are removed, and can be directly placed on top of non-solid blocks.}} {{History\|\|\|snap=pre2\|The "You can only sleep at night" message when using a bed has been changed to "You can sleep only at night and during [[thunderstorm]]s."}} {{History\|\|1.14\|snap=18w43a\|[[File:White Bed JE3 BE3.png\|32px]] [[File:Light Gray Bed JE3 BE3.png\|32px]] [[File:Gray Bed JE3 BE3.png\|32px]] [[File:Black Bed JE3 BE3.png\|32px]] [[File:Brown Bed JE3 BE3.png\|32px]] [[File:Red Bed JE4 BE3.png\|32px]] [[File:Orange Bed JE3 BE3.png\|32px]] [[File:Yellow Bed JE3 BE3.png\|32px]] [[File:Lime Bed JE3 BE3.png\|32px]] [[File:Green Bed JE3 BE3.png\|32px]] [[File:Cyan Bed JE3 BE3.png\|32px]] [[File:Light Blue Bed JE3 BE3.png\|32px]] [[File:Blue Bed JE3 BE3.png\|32px]] [[File:Purple Bed JE3 BE3.png\|32px]] [[File:Magenta Bed JE3 BE3.png\|32px]] [[File:Pink Bed JE3 BE3.png\|32px]]<br>{{InvSprite\|White Bed}} {{InvSprite\|Light Gray Bed}} {{InvSprite\|Gray Bed}} {{InvSprite\|Black Bed}} {{InvSprite\|Brown Bed}} {{InvSprite\|Red Bed}} {{InvSprite\|Orange Bed}} {{InvSprite\|Yellow Bed}} {{InvSprite\|Lime Bed}} {{InvSprite\|Green Bed}} {{InvSprite\|Cyan Bed}} {{InvSprite\|Light Blue Bed}} {{InvSprite\|Blue Bed}} {{InvSprite\|Purple Bed}} {{InvSprite\|Magenta Bed}} {{InvSprite\|Pink Bed}} The textures of all beds have been changed. \|[[File:Red Bed JE5 (facing NWU).png\|32px]] The bottom textures of beds have been changed to new oak planks texture.}} {{History\|\|\|snap=18w44a\|Cats can now sleep in empty beds or sit on their owner when their owner is sleeping.}} {{History\|\|\|snap=18w47a\|[[File:Red Bed JE6 BE3 (facing NWU).png\|32px]] The bottom textures of beds have been changed to the new oak planks to texture, once again.}} {{History\|\|\|snap=18w48a\|Beds now generate in the updated [[plains]] [[village]]s.}} {{History\|\|\|snap=18w49a\|Beds now generate in the updated [[savanna]] villages and the new [[snowy tundra]] villages.}} {{History\|\|\|snap=18w50a\|Beds now generate in the updated [[desert]] and [[taiga]] villages.}} {{History\|\|\|snap=19w08a\|All mobs can now sleep in beds using [[command]]s.}} {{History\|\|\|snap=19w11a\|[[Villager]]s now claim beds and sleep in them during the night. \|Shepherd villagers now [[trading\|sell]] beds.}} {{History\|\|1.15\|snap=19w35a\|If a player tries to sleep in a bed that is occupied by a villager, that villager is now kicked out of the bed.}} {{History\|\|\|snap=19w36a\|Trying to sleep in a bed during the daytime now sets the player's spawn location to that bed.}} {{History\|\|\|snap=pre2\|Successfully changing a spawn point using a bed now displays a message in [[chat]].}} {{History\|\|1.16\|snap=20w06a\|Crimson and warped planks can now be used to craft beds.}} {{History\|\|\|snap=20w12a\|The message "Your home bed was missing or obstructed" has been changed to "You have no home bed or respawn anchor, or it was obstructed" due to the addition of the [[respawn anchor]], used to set the player's spawn in [[the Nether]].}} {{History\|\|1.16.2\|snap=20w30a\|Beds now prioritize the side of the bed the player or villager entered from and then spaces circling around the foot of the bed up to the head of the bed.}} {{History\|\|1.17\|snap=20w51a\|Added gamerules for sleeping in multiplayer.}} {{History\|\|1.18\|snap=21w44a\|Sleeping now only resets the weather cycle if it is currently raining or snowing.<ref>{{bug\|MC-63340\|\|Sleeping always resets time until rain\|Fixed}}</ref>}} {{History\|\|1.19\|snap=22w11a\|[[Mangrove]] planks can now be used to craft beds.}} {{History\|\|1.19.3\|snap=22w43a\|Bed explosions can now be properly [[blocking\|blocked]] by [[shield]]s.<ref>{{bug\|MC-200006\|\|\|Fixed}}</ref>}} {{History\|\|1.20\|snap=Pre-release 1\|Beds of any color can now be dyed into any other color.}} {{History\|pocket alpha}} {{History\|\|v0.4.0\|[[File:Red Bed JE1 BE1.png\|32px]] [[File:Red Bed (item) JE1 BE1.png\|32px]] Added beds.}} {{History\|\|v0.5.0\|Beds can now be obtained after activating the [[nether reactor]].}} {{History\|\|v0.9.0\|snap=build 1\|Beds no longer restore [[health]] in normal difficulty, making [[food]] a more required [[Survival]]-needed resource. \|Added smooth lighting to beds.}} {{History\|\|v0.11.0\|snap=build 8\|The lighting on beds has been improved.}} {{History\|\|v0.12.1\|snap=build 1\|Tamed [[cat\|ocelots]] while standing now purposely go and sit on beds. \|Beds are no longer available from the [[nether reactor]].}} {{History\|\|v0.16.0\|snap=build 1\|Beds now make a [[sound]] when placed, identical to [[block]]s like [[stone]].<ref name="lazilycodedsounds">{{bug\|MCPE-10077}} – "Incorrect sounds on beds" resolved as "Fixed".</ref>}} {{History\|pocket}} {{History\|\|1.0.0\|snap=alpha 0.17.0.1\|Beds are now generated in [[igloo]]s.}} {{History\|\|\|snap=alpha 0.17.0.2\|[[File:Leave Bed 1.0.jpg\|36px]] The ''Leave Bed'' button now has a new texture.}} {{History\|\|\|snap=alpha 1.0.0.0\|Sleeping now ends [[weather]].}} {{History\|\|1.1.0\|snap=alpha 1.1.0.0\|[[File:White Bed JE2 BE2.png\|32px]] [[File:Light Gray Bed JE2 BE2.png\|32px]] [[File:Gray Bed JE2 BE2.png\|32px]] [[File:Black Bed JE2 BE2.png\|32px]] [[File:Brown Bed JE2 BE2.png\|32px]] [[File:Orange Bed JE2 BE2.png\|32px]] [[File:Yellow Bed JE2 BE2.png\|32px]] [[File:Lime Bed JE2 BE2.png\|32px]] [[File:Green Bed JE2 BE2.png\|32px]] [[File:Cyan Bed JE2 BE2.png\|32px]] [[File:Light Blue Bed JE2 BE2.png\|32px]] [[File:Blue Bed JE2 BE2.png\|32px]] [[File:Purple Bed JE2 BE2.png\|32px]] [[File:Magenta Bed JE2 BE2.png\|32px]] [[File:Pink Bed JE2 BE2.png\|32px]]<br>[[File:White Bed (item) BE1.png\|32px]] [[File:Light Gray Bed (item) BE1.png\|32px]] [[File:Gray Bed (item) BE1.png\|32px]] [[File:Black Bed (item) BE1.png\|32px]] [[File:Brown Bed (item) BE1.png\|32px]] [[File:Orange Bed (item) BE1.png\|32px]] [[File:Yellow Bed (item) BE1.png\|32px]] [[File:Lime Bed (item) BE1.png\|32px]] [[File:Green Bed (item) BE1.png\|32px]] [[File:Cyan Bed (item) BE1.png\|32px]] [[File:Light Blue Bed (item) BE1.png\|32px]] [[File:Blue Bed (item) BE1.png\|32px]] [[File:Purple Bed (item) BE1.png\|32px]] [[File:Magenta Bed (item) BE1.png\|32px]] [[File:Pink Bed (item) BE1.png\|32px]] Added the other 15 colors of beds. \|The "Bed" has been renamed to "Red Bed". \|[[File:Red Bed JE3 BE2.png\|32px]] The texture of red beds has been changed. \|A new animation when sleeping has been added to beds. \|Beds in [[igloo]]s are now white in [[ice plains]] and brown in [[cold taiga]]s. \|Beds now bounce the [[player]] two [[block]]s up, and have 3D legs. \|Placement, stepping and breaking [[sound]]s for beds are now correctly wooden.<ref name="lazilycodedsounds"/>}} {{History\|bedrock}} {{History\|\|1.4.0\|snap=beta 1.2.14.2\|Beds can now be [[waterlogging\|waterlogged]] and require [[Water Breathing]] to sleep in.}} {{History\|\|\|snap=beta 1.2.20.1\|Colored beds can now be turned into white beds by adding [[bleach]]. This works only if {{el\|ee}} features are turned on.}} {{History\|\|1.6.0\|snap=beta 1.6.0.1\|Sleeping in a bed is now important to keep [[phantom]]s from spawning.}} {{History\|\|1.8.0\|snap=beta 1.8.0.8\|[[Cat]]s can now sleep in empty beds or sit on their [[player\|owner]] when their owner is sleeping.}} {{History\|\|1.10.0\|snap=beta 1.10.0.3\|Various beds now generate in the new [[village]]s. \|[[Villager]]s can now sleep by occupying a bed, which prevent [[player]]s from using it. \|[[Igloo]]s now generate with red beds. \|Beds are now used to count the number of available houses in [[village]]s. \|[[File:White Bed JE3 BE3.png\|32px]] [[File:Light Gray Bed JE3 BE3.png\|32px]] [[File:Gray Bed JE3 BE3.png\|32px]] [[File:Black Bed JE3 BE3.png\|32px]] [[File:Brown Bed JE3 BE3.png\|32px]] [[File:Red Bed JE4 BE3.png\|32px]] [[File:Orange Bed JE3 BE3.png\|32px]] [[File:Yellow Bed JE3 BE3.png\|32px]] [[File:Lime Bed JE3 BE3.png\|32px]] [[File:Green Bed JE3 BE3.png\|32px]] [[File:Cyan Bed JE3 BE3.png\|32px]] [[File:Light Blue Bed JE3 BE3.png\|32px]] [[File:Blue Bed JE3 BE3.png\|32px]] [[File:Purple Bed JE3 BE3.png\|32px]] [[File:Magenta Bed JE3 BE3.png\|32px]] [[File:Pink Bed JE3 BE3.png\|32px]] The textures of all beds have been changed.}} {{History\|\|1.11.0\|snap=beta 1.11.0.4\|Beds can now be [[trading\|bought]] from shepherd [[villager]]s.}} {{History\|\|1.13.0\|snap=?\|[[Player]]s now succeed in attempting to sleep on villager-occupied beds, kicking the villager off.}} {{History\|console}} {{History\|\|xbox=TU1\|xbone=CU1\|ps=1.00\|wiiu=Patch 1\|switch=1.0.1\|[[File:Red Bed JE1 BE1.png\|32px]] [[File:Red Bed (item) JE1 BE1.png\|32px]] Added beds.}} {{History\|\|xbox=TU12\|xbone=CU1\|ps=1.00\|wiiu= Patch 1\|[[Cat]]s in standing position now purposely go and sit on beds, preventing [[player]]s from using them.}} {{History\|\|xbox=TU43\|xbone=CU33\|ps=1.36\|wiiu=Patch 13\|The sleeping animation while in beds has been changed.}} {{History\|\|xbox=TU54\|xbone=CU44\|ps=1.52\|wiiu=Patch 24\|switch=1.0.4\|[[File:White Bed JE2 BE2.png\|32px]] [[File:Light Gray Bed JE2 BE2.png\|32px]] [[File:Gray Bed JE2 BE2.png\|32px]] [[File:Black Bed JE2 BE2.png\|32px]] [[File:Brown Bed JE2 BE2.png\|32px]] [[File:Orange Bed JE2 BE2.png\|32px]] [[File:Yellow Bed JE2 BE2.png\|32px]] [[File:Lime Bed JE2 BE2.png\|32px]] [[File:Green Bed JE2 BE2.png\|32px]] [[File:Cyan Bed JE2 BE2.png\|32px]] [[File:Light Blue Bed JE2 BE2.png\|32px]] [[File:Blue Bed JE2 BE2.png\|32px]] [[File:Purple Bed JE2 BE2.png\|32px]] [[File:Magenta Bed JE2 BE2.png\|32px]] [[File:Pink Bed JE2 BE2.png\|32px]]<br>[[File:White Bed (item) LCE.png\|32px]] [[File:Light Gray Bed (item) LCE.png\|32px]] [[File:Gray Bed (item) LCE.png\|32px]] [[File:Black Bed (item) LCE.png\|32px]] [[File:Brown Bed (item) LCE.png\|32px]] [[File:Orange Bed (item) LCE.png\|32px]] [[File:Yellow Bed (item) LCE.png\|32px]] [[File:Lime Bed (item) LCE.png\|32px]] [[File:Green Bed (item) LCE.png\|32px]] [[File:Cyan Bed (item) LCE.png\|32px]] [[File:Light Blue Bed (item) LCE.png\|32px]] [[File:Blue Bed (item) LCE.png\|32px]] [[File:Purple Bed (item) LCE.png\|32px]] [[File:Magenta Bed (item) LCE.png\|32px]] [[File:Pink Bed (item) LCE.png\|32px]] Added the other 15 colors of beds. \|The "Bed" has been now renamed to "Red Bed". \|[[File:Red Bed JE3 BE2.png\|32px]] [[File:Red Bed (item) LCE.png\|32px]] The textures of red beds has been changed. \|Beds are now [[dye]]able and bounce the [[player]] two [[block]]s up, and have a single 3D legs.}} {{History\|\|xbox=TU60\|xbone=CU51\|ps=1.64\|wiiu=Patch 30\|switch=1.0.11\|The sleeping animation in beds has been changed again.}} {{History\|\|xbox=TU69\|xbone=none\|ps=1.76\|wiiu=Patch 38\|switch=none\|Sleeping in a bed is now important to keep [[phantom]]s from spawning. \|Beds can now be [[waterlogging\|waterlogged]] and require {{EffectLink\|Water Breathing}} to sleep in.}} {{History\|\|xbox=none\|xbone=none\|ps=1.83\|wiiu=none\|switch=none\|The sleeping animation for beds has been reverted to how it was before [[Legacy Console Edition version history#ps-1.64\|1.64]].}} {{History\|\|xbox=none\|xbone=none\|ps=1.91\|wiiu=none\|switch=none\|Various beds now generate in the new [[village]]s. \|[[Villager]]s can now sleep by occupying a bed, which prevents [[player]]s from using it. \|Beds are now used to count the number of available houses in villages. \|Beds can now be [[trading\|bought]] from shepherd [[villager]]s.}} {{History\|New 3DS}} {{History\|\|0.1.0\|[[File:Red Bed JE1 BE1.png\|32px]] [[File:Red Bed (item) JE1 BE1.png\|32px]] Added beds.}} {{History\|\|1.9.19\|[[File:White Bed JE2 BE2.png\|32px]] [[File:Light Gray Bed JE2 BE2.png\|32px]] [[File:Gray Bed JE2 BE2.png\|32px]] [[File:Black Bed JE2 BE2.png\|32px]] [[File:Brown Bed JE2 BE2.png\|32px]] [[File:Orange Bed JE2 BE2.png\|32px]] [[File:Yellow Bed JE2 BE2.png\|32px]] [[File:Lime Bed JE2 BE2.png\|32px]] [[File:Green Bed JE2 BE2.png\|32px]] [[File:Cyan Bed JE2 BE2.png\|32px]] [[File:Light Blue Bed JE2 BE2.png\|32px]] [[File:Blue Bed JE2 BE2.png\|32px]] [[File:Purple Bed JE2 BE2.png\|32px]] [[File:Magenta Bed JE2 BE2.png\|32px]] [[File:Pink Bed JE2 BE2.png\|32px]]<br>[[File:White Bed (item) BE1.png\|32px]] [[File:Light Gray Bed (item) BE1.png\|32px]] [[File:Gray Bed (item) BE1.png\|32px]] [[File:Black Bed (item) BE1.png\|32px]] [[File:Brown Bed (item) BE1.png\|32px]] [[File:Orange Bed (item) BE1.png\|32px]] [[File:Yellow Bed (item) BE1.png\|32px]] [[File:Lime Bed (item) BE1.png\|32px]] [[File:Green Bed (item) BE1.png\|32px]] [[File:Cyan Bed (item) BE1.png\|32px]] [[File:Light Blue Bed (item) BE1.png\|32px]] [[File:Blue Bed (item) BE1.png\|32px]] [[File:Purple Bed (item) BE1.png\|32px]] [[File:Magenta Bed (item) BE1.png\|32px]] [[File:Pink Bed (item) BE1.png\|32px]] Added the other 15 colors of beds. \|The "Bed" has been renamed to "Red Bed". \|[[File:Red Bed JE3 BE2.png\|32px]] The texture of red beds has been changed. \|Beds now bounce the [[player]] two [[block]]s up and have 3D legs.}} {{History\|Education}} {{History\|\|1.0\|[[File:Red Bed JE1 BE1.png\|32px]] [[File:Red Bed (item) JE1 BE1.png\|32px]] Added beds.}} {{History\|\|1.0.1\|[[File:White Bed JE2 BE2.png\|32px]] [[File:Light Gray Bed JE2 BE2.png\|32px]] [[File:Gray Bed JE2 BE2.png\|32px]] [[File:Black Bed JE2 BE2.png\|32px]] [[File:Brown Bed JE2 BE2.png\|32px]] [[File:Orange Bed JE2 BE2.png\|32px]] [[File:Yellow Bed JE2 BE2.png\|32px]] [[File:Lime Bed JE2 BE2.png\|32px]] [[File:Green Bed JE2 BE2.png\|32px]] [[File:Cyan Bed JE2 BE2.png\|32px]] [[File:Light Blue Bed JE2 BE2.png\|32px]] [[File:Blue Bed JE2 BE2.png\|32px]] [[File:Purple Bed JE2 BE2.png\|32px]] [[File:Magenta Bed JE2 BE2.png\|32px]] [[File:Pink Bed JE2 BE2.png\|32px]]<br>[[File:White Bed (item) BE1.png\|32px]] [[File:Light Gray Bed (item) BE1.png\|32px]] [[File:Gray Bed (item) BE1.png\|32px]] [[File:Black Bed (item) BE1.png\|32px]] [[File:Brown Bed (item) BE1.png\|32px]] [[File:Orange Bed (item) BE1.png\|32px]] [[File:Yellow Bed (item) BE1.png\|32px]] [[File:Lime Bed (item) BE1.png\|32px]] [[File:Green Bed (item) BE1.png\|32px]] [[File:Cyan Bed (item) BE1.png\|32px]] [[File:Light Blue Bed (item) BE1.png\|32px]] [[File:Blue Bed (item) BE1.png\|32px]] [[File:Purple Bed (item) BE1.png\|32px]] [[File:Magenta Bed (item) BE1.png\|32px]] [[File:Pink Bed (item) BE1.png\|32px]] Added the other 15 colors of beds. \|The "Bed" has been renamed to "Red Bed". \|[[File:Red Bed JE3 BE2.png\|32px]] The texture of red beds has been changed. \|Beds now bounce the [[player]] two [[block]]s up, and have 3D legs.}} {{History\|\|1.0.27\|Colored beds can now be turned into white beds by adding [[bleach]].}} {{History\|\|1.12\|[[File:White Bed JE3 BE3.png\|32px]] [[File:Light Gray Bed JE3 BE3.png\|32px]] [[File:Gray Bed JE3 BE3.png\|32px]] [[File:Black Bed JE3 BE3.png\|32px]] [[File:Brown Bed JE3 BE3.png\|32px]] [[File:Red Bed JE4 BE3.png\|32px]] [[File:Orange Bed JE3 BE3.png\|32px]] [[File:Yellow Bed JE3 BE3.png\|32px]] [[File:Lime Bed JE3 BE3.png\|32px]] [[File:Green Bed JE3 BE3.png\|32px]] [[File:Cyan Bed JE3 BE3.png\|32px]] [[File:Light Blue Bed JE3 BE3.png\|32px]] [[File:Blue Bed JE3 BE3.png\|32px]] [[File:Purple Bed JE3 BE3.png\|32px]] [[File:Magenta Bed JE3 BE3.png\|32px]] [[File:Pink Bed JE3 BE3.png\|32px]] The textures of all beds have been changed.}} {{History\|foot}} === Data history === {{History\|java}} {{History\|\|1.13\|snap=17w47a\|The different block states for the <code>bed</code> ID have been split up into their own IDs. \|Prior to [[1.13/Flattening\|''The Flattening'']], this block's numeral ID was 26, and the item's 355.}} {{History\|foot}} === Bed "item"=== {{:Technical blocks/Bed}} ==Issues== {{Issue list}} == Trivia== * The reason beds explode in the Nether and the End is because Notch found it was the easiest solution to dimension-unique respawning.<ref>{{tweet\|Notch\|1259681657793077250\|duh\|11 May 2020}}, in response to {{tweet\|NoahBandito\|1259681319392550912\|So you're telling me the "Inteded Game Design" should actually be "Sorry, I was too lazy to code"?\|11 May 2020}}</ref> ** Dimension-unique respawning was eventually implemented via the [[respawn anchor]], and gained command support at the same time. Despite this, beds and respawn anchors still explode in invalid dimensions. * If the player quits the game while sleeping, upon return the player wakes up beside the bed. * Using the {{cmd\|teleport}} command while another player is sleeping still teleports the sleeping player, but the player wakes immediately.{{only\|java}} * If the player places a bed on [[ice]], running over the bed acts like running over ice, similar to slabs. * When placed using the {{cmd\|setblock}} command, only one half of a bed is placed, because beds are two blocks long. A single half can be slept in like a whole bed. * Villagers can sleep in the Nether and the End without causing the bed to explode.<ref>{{bug\|MC-146515}} Resolved as Works As Intended</ref> * While the block state used to determine the half of a two-block block such as [[door]]s and double-tall [[flower]]s is called ''half'', in the case of beds this is called ''part''. * Players and villagers do not drown or take damage from lava while in a bed, even if the bed is covered in lava. The red bed was the original default bed color. In [[Java Edition 1.12]] and [[Pocket Edition 1.1.0]] version of the game, the default color was changed to white. == Gallery == === All renders === <gallery> White Bed.png\|White Light Gray Bed.png\|Light gray Gray Bed.png\|Gray Black Bed.png\|Black Brown Bed.png\|Brown Red Bed.png\|Red Orange Bed.png\|Orange Yellow Bed.png\|Yellow Lime Bed.png\|Lime Green Bed.png\|Green Cyan Bed.png\|Cyan Light Blue Bed.png\|Light blue Blue Bed.png\|Blue Purple Bed.png\|Purple Magenta Bed.png\|Magenta Pink Bed.png\|Pink </gallery> === Screenshots === <gallery> Multiplayer Sleeping.png\|A sleeping player in multiplayer. Missing Bed.png\|The message that can be seen after a failed attempt to respawn at the spawn point set by a bed. Nether Bed.png\|A crater created by attempting to sleep in the Nether. Ender Bed.png\|A crater created by attempting to sleep in the End. 16 color beds.png\|All the different color variants. Old Village New Village VillagerSleeping MCEE.png\|An unemployed [[villager]] and a [[butcher]] villager goes to sleep, unaware of the zombies outside. Stackedbeds.png\|A stack of beds. Mob wakeup.png\|Player being awakened by a [[zombie]]. Day Sleeping.png\|The message that can be seen when any players attempt to sleep during daytime. Sleeping.png\|A player going to sleep in a bed on the first day of a ''Minecraft'' world. CobwebVillage.png\|A bed in an abandoned village has its bottom half replaced by wheat crops. </gallery> === In other media === <gallery> File:Rainbow Bed.png\|The [[MCE:Rainbow Bed\|rainbow bed]], a unique coloration featured in [[Minecraft Earth]]. File:The Sham.jpg\|The Sham, a villainous, sentient bed featured in the [[skin pack\|Campfire Tales]] skin pack. </gallery> ==References== {{Reflist}} {{Blocks\|Utility}} {{Items}} [[Category:Utility blocks]] [[Category:Manufactured blocks]] [[Category:Generated structure blocks]] [[Category:Block entities]] [[cs:Postel]] [[de:Bett]] [[es:Cama]] [[fr:Lit]] [[hu:Ágy]] [[it:Letto]] [[ja:ベッド]] [[ko:침대]] [[nl:Bed]] [[pl:Łóżko]] [[pt:Cama]] [[ru:Кровать]] [[th:เตียง]] [[uk:Ліжко]] [[zh:床]]</li><li>[[Milk Bucket\|Milk Bucket]]<br/>{{Item \| title=Milk Bucket \| image = Milk Bucket.png \| renewable = Yes \| effects = Clears all \| stackable = No }} A '''milk bucket'''{{fn\|Known as '''Milk Bucket''' {{in\|java}} and '''Milk''' {{in\|bedrock}}.}} is a [[drink]] obtained from {{Control\|use\|text=using}} a [[bucket]] on [[cow]]s, [[mooshroom]]s and [[goat]]s that can be consumed to clear all [[Effect\|effects]]. == Obtaining == === Harvesting === Milk buckets can be obtained from [[cow]]s, [[mooshroom]]s, and [[goat]]s by pressing {{control\|use}} while looking at them with an empty [[bucket]]. === Mob loot === A milk bucket has a chance of dropping from a [[wandering trader]], if the trader is killed while holding it.{{only\|java}} == Usage == Holding {{control\|use}} with a milk bucket starts the drinking sound and animation. {{IN\|java}}, the animation is shown only in first-person camera mode. When consumed, milk immediately removes all status [[effect]]s from the [[player]]. [[Fire]] is not a status effect; therefore, drinking milk doesn't extinguish a burning player. The benefits of area status effects granted by [[beacon]]s and [[Conduit Power\|conduit power]] are restored almost immediately in Bedrock Edition and after a few seconds in ''Java Edition''. === Crafting ingredient === {{crafting usage\|Milk Bucket}} == Sounds == {{el\|je}}: {{Sound table \|sound=Drink.ogg \|subtitle=Sipping \|source=player \|description=While a player is drinking milk \|id=entity.generic.drink \|translationkey=subtitles.entity.generic.drink \|volume=0.5 \|pitch=0.9-1.0 \|distance=16}} {{Sound table \|sound=Cow milk1.ogg \|sound2=Cow milk2.ogg \|sound3=Cow milk3.ogg \|source=player \|subtitle=Cow gets milked \|description=When a cow is milked \|id=entity.cow.milk \|translationkey=subtitles.entity.cow.milk \|volume=1.0 \|pitch=1.0 \|distance=16}} {{Sound table \|sound=Mooshroom milk1.ogg \|sound2=Mooshroom milk2.ogg \|sound3=Mooshroom milk3.ogg \|subtitle=Goat gets milked \|description=When a regular goat is milked \|source=neutral \|id=entity.goat.milk \|translationkey=subtitles.entity.goat.milk \|volume=1.0 \|pitch=1.0 \|distance=16}} {{Sound table \|sound=Goat screaming milk1.ogg \|sound2=Goat screaming milk2.ogg \|sound3=Goat screaming milk3.ogg \|sound4=Goat screaming milk4.ogg \|sound5=Goat screaming milk5.ogg \|subtitle=Goat gets milked \|description=When a screaming goat is milked \|source=neutral \|id=entity.goat.screaming.milk \|translationkey=subtitles.entity.goat.milk \|volume=1.0 \|pitch=1.0 \|distance=16}} {{Sound table \|sound=Wandering trader drink milk1.ogg \|sound2=Wandering trader drink milk2.ogg \|sound3=Wandering trader drink milk3.ogg \|sound4=Wandering trader drink milk4.ogg \|sound5=Wandering trader drink milk5.ogg \|subtitle=Wandering Trader drinks milk \|source=neutral \|description=While a wandering trader is drinking milk to become visible during daytime \|id=entity.wandering_trader.drink_milk \|translationkey=subtitles.entity.wandering_trader.drink_milk \|volume=0.5 \|pitch=0.9-1.0 \|distance=16 \|foot=1}} {{el\|be}}: {{Sound table \|type=bedrock \|sound=Drink.ogg \|source=player \|description=While a player is drinking milk \|id=random.drink \|volume=0.35 \|pitch=0.9-1.1}} {{Sound table \|sound=Cow milk1.ogg \|sound2=Cow milk2.ogg \|sound3=Cow milk3.ogg \|source=neutral \|description=When a cow is milked \|id=mob.cow.milk \|volume=1.0 \|pitch=1.0}} {{Sound table \|sound=Mooshroom milk1.ogg \|sound2=Mooshroom milk2.ogg \|sound3=Mooshroom milk3.ogg \|description=When a regular goat is milked \|source=neutral \|id=mob.mooshroom.suspicious_milk \|volume=1.0 \|pitch=1.0/0.9/1.1}} {{Sound table \|sound=Goat screaming milk1.ogg \|sound2=Goat screaming milk2.ogg \|sound3=Goat screaming milk3.ogg \|sound4=Goat screaming milk4.ogg \|sound5=Goat screaming milk5.ogg \|description=When a screaming goat is milked \|source=neutral \|id=mob.goat.milk.screamer \|volume=1.0 \|pitch=1.0}} {{Sound table \|sound=Wandering trader drink milk1.ogg \|sound2=Wandering trader drink milk2.ogg \|sound3=Wandering trader drink milk3.ogg \|sound4=Wandering trader drink milk4.ogg \|sound5=Wandering trader drink milk5.ogg \|source=neutral \|description=While a wandering trader is drinking milk to become visible during daytime \|id=mob.wanderingtrader.drink_milk \|volume=1.0 \|pitch=0.8-1.2 \|foot=1}} == Data values == === ID === {{edition\|java}}: {{ID table \|edition=java \|showforms=y \|generatetranslationkeys=y \|displayname=Milk Bucket \|spritetype=item \|nameid=milk_bucket \|form=item \|foot=1}} {{edition\|bedrock}}: {{ID table \|edition=bedrock \|showaliasids=y \|shownumericids=y \|showforms=y \|notshowbeitemforms=y \|generatetranslationkeys=y \|displayname=Milk \|spritetype=item \|nameid=milk_bucket \|aliasid=bucket / 1 \|id=361 \|form=item \|translationkey=item.milk.name \|foot=1}} == Achievements == {{load achievements\|The Lie}} == Advancements == {{Load advancements\|Husbandry}} == Video == <div style="text-align:center">{{yt\|eyxea_d0b3s}}</div> == History == {{History\|java alpha}} {{History\|\|v1.0.8\|[[File:Milk Bucket JE1 BE1.png\|32px]] Milk has been introduced, but it has no purpose and is obtainable only through inventory editing.}} {{History\|\|v1.0.11\|Milk can now be obtained by {{control\|use\|text=milking}} a [[cow]] with a [[bucket]]. However, it is not yet drinkable.}} {{History\|\|v1.0.17\|Milk buckets can now be emptied.}} {{History\|java beta}} {{History\|\|1.2\|Milk has been incorporated into the [[crafting]] recipe of [[cake]].}} {{History\|\|1.2_01\|[[Squid]] can now be milked by right-clicking on their mouth if part of their body was exposed to [[air]] or if they were not touching another [[block]]. An easy way to accomplish this is to pull a squid with a [[fishing rod]] away from other blocks and then milk it.}} {{History\|\|1.3_01\|Squid milking has been removed.}} {{History\|java}} {{History\|\|1.0.0\|snap=Beta 1.9 Prerelease\|Milk can now be obtained by milking [[mooshroom]]s.}} {{History\|\|\|snap=Beta 1.9 Prerelease 2\|Milk has been made drinkable. \|According to a tweet by [[Jeb]] on September 30th 2011, milk was made a cure for all status effects.<ref>{{tweet\|jeb_\|119842906528944129\|@Nexusdog_UK I haven't! In beta 1.9 pre2 milk works like a clear-everything drink\|September 30, 2011}}</ref> \|Milk is no longer emptiable.}} {{History\|\|1.13\|snap=17w47a\|Prior to [[1.13/Flattening\|''The Flattening'']], this [[item]]'s numeral ID was 335.}} {{History\|\|\|snap=18w20a\|"Milk" has been renamed to "Milk Bucket".}} {{History\|\|1.14\|snap=18w43a\|[[File:Milk Bucket JE2 BE2.png\|32px]] The texture of milk buckets has been changed.}} {{History\|\|1.14\|snap=19w06a\|[[Wandering trader]]s now drink from milk buckets at dawn, and have a change to drop them.}} {{History\|\|1.17\|snap=21w13a\|Milk can now be obtained by milking [[goat]]s.}} {{History\|upcoming java}} {{History\|\|Villager Trade Rebalance<br>(Experimental)\|link=Java Edition 1.20.2\|snap=23w31a\|Wander traders now have a chance to [[trading\|buy]] a milk bucket from the player.}} {{History\|pocket alpha}} {{History\|\|v0.7.0\|[[File:Milk Bucket JE1 BE1.png\|32px]] Added milk buckets. \|Milk buckets are not yet drinkable.}} {{History\|\|v0.11.0\|snap=build 4\|Drinking milk now removes [[status effects]]. \|Added milk buckets to the Creative inventory.{{verify\|type=update}}{{info needed}}<!---same update?--->}} {{History\|bedrock}} {{History\|\|1.4.0\|snap=beta 1.2.14.2\|Moved all bucket items, including milk, from the Equipment tab to the Items tab in the [[Creative inventory]].{{verify\|type=update}}{{info needed}}<!---please check snapshots, only 1 major release version was checked each--->}} {{History\|\|1.10.0\|snap=beta 1.10.0.3\|[[File:Milk Bucket JE2 BE2.png\|32px]] The texture of milk buckets has been changed.}} {{History\|\|1.16.100\|snap=beta 1.16.100.56\|The ID of milk has been changed from <code>bucket/1</code> to <code>milk_bucket</code>.}} {{History\|\|1.16.200\|snap=beta 1.16.200.52\|Milk can now be obtained by milking [[goat]]s.}} {{History\|console}} {{History\|\|xbox=TU1\|xbone=CU1\|ps=1.0\|wiiu=Patch 1\|switch=1.0.1\|[[File:Milk Bucket JE1 BE1.png\|32px]] Added milk buckets.}} {{History\|Ps4}} {{History\|\|1.90\|[[File:Milk Bucket JE2 BE2.png\|32px]] The texture of milk buckets has been changed.}} {{History\|New 3DS}} {{History\|\|0.1.0\|[[File:Milk Bucket JE1 BE1.png\|32px]] Added milk buckets.}} {{History\|foot}} == Issues == {{issue list}} == See also == [[Water Bucket]] [[Lava]] [[Food]] [[Cake]] [[Honey Bottle]] (alternative to remove poison effect) [[Medicine]] == Notes == {{fnlist}} == References == {{reflist}} == External Links == [https://www.minecraft.net/en-us/article/taking-inventory--milk-bucket Taking Inventory: Milk Bucket] – Minecraft.net on October 8, 2019 {{Items}} [[Category:Food]] [[Category:Renewable resources]] [[Category:Tools]] [[cs:Mléko]] [[de:Milcheimer]] [[es:Cubo con leche]] [[fr:Seau de lait]] [[hu:Tej]] [[it:Secchio di latte]] [[ja:ミルク入りバケツ]] [[ko:우유 양동이]] [[nl:Emmer melk]] [[pl:Wiadro mleka]] [[pt:Balde de leite]] [[ru:Ведро с молоком]] [[th:ถังนม]] [[uk:Відро молока]] [[zh:奶桶]]</li></ul>	beta 1.16.200.52	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]
	release	Goats have been made inaccessible in the full release.
Upcoming Bedrock Edition
1.16.210 {{Extension DPL}}<ul><li>[[Glass Bottle\|Glass Bottle]]<br/>{{about\|the empty bottle\|\|Bottle}} {{Item \| image = Glass Bottle.png \| renewable = Yes \| stackable = Yes (64) }} A '''glass bottle''' is an [[item]] that can hold [[water]], [[potion]]s, [[Honey Bottle\|honey]], or [[dragon's breath]]. == Obtaining == Glass bottles can be obtained by crafting, drinking from bottles, [[fishing]], or from [[witch]] drops. === Crafting === {{Crafting \|A2= Glass \|C2= Glass \|B3= Glass \|Output= Glass Bottle,3 \|type= Brewing }} === Drinking === Drinking a [[potion]] or [[Honey Bottle\|honey bottle]] returns the empty glass bottle. Throwing a splash potion or a lingering potion does not return a glass bottle, but brewing a lingering potion gives back a glass bottle. === Mob loot === [[Witch]]es have a chance of dropping 0–6 glass bottles upon death. This is increased by 3 per level of [[Looting]], for a maximum of 0–15 glass bottles. === Mud === {{control\|Using}} a [[water bottle]], [[splash water bottle]] or [[lingering water bottle]] on [[dirt]], [[coarse dirt]] or [[rooted dirt]] will transforming it into a [[mud]] block, at the same time leaving the player with an empty glass bottle. === Cauldrons === {{control\|Using}} a water bottle (or, {{in\|bedrock}}, a potion, splash potion, or lingering potion) on a [[cauldron]] that is not yet full adds that liquid to the cauldron, leaving the player with an empty glass bottle. == Usage == Glass bottles can be filled to make [[water bottle]]s, which can then be used to [[brew]] items with a [[brewing stand]]. Glass bottles are also used to hold the resulting [[potion]]. === Collecting liquids === ==== Water ==== A bottle may be filled with water by holding it in the hand and {{control\|using}} it on a [[water]] source block or a [[cauldron]] that has water in it. It can also be filled using a waterlogged block.{{only\|java}}<ref>{{bug\|MCPE-83420}}</ref> Also, a bottle may be filled by powering a [[dispenser]] containing a bottle and pointed at a water source block. This does not work with cauldrons.<ref>{{bug\|MC-165196\|\|\|Invalid}}</ref> If filled via a water source, the water is unaffected. If filled via a cauldron, {{frac\|1\|3}} of the water in the cauldron is removed. Therefore, using a cauldron to fill water bottles is inefficient, except in [[the Nether]] where it is normally the only way to fill bottles. ==== Potion ==== {{IN\|bedrock}}, a bottle may be filled with potion by {{control\|using}} it on a [[cauldron]] containing potion. When the bottle is filled, {{frac\|1\|3}} of the cauldron's potion is removed. ==== Honey ==== If a [[beehive\|bee nest]] or [[beehive]] is full, the player can {{control\|use}} a glass bottle on the block, or may power a [[dispenser]] that contains a bottle and is pointed at the block, which empties the block and creates a [[honey bottle]]. Honey bottles can also be emptied by using them in crafting recipes (such as [[sugar]] or [[honey block]]). However, a lingering potion use on tipped arrow recipe does not give the bottle back. ==== Dragon's breath ==== {{control\|Using}} a glass bottle in clouds emitted when the [[ender dragon]] breathes or shoots a [[dragon fireball]] fills the bottle with [[dragon's breath]]. When put 2 or more dragon's breath in the brewing stand, after the brewing process, a glass bottle will drop as an [[Item (entity)\|entity]]. However, if put only 1 dragon's breath in the brewing stand, after the brewing process, the glass bottle is consumed and cannot be retrieved.<ref>{{bug\|MC-259583}}</ref> === Trading === Expert-level cleric [[villager]]s have a 50% chance to buy 9 glass bottles for one [[emerald]] as part of their trade.{{only\|bedrock}} Expert-level cleric villagers have a {{frac\|2\|3}} chance to buy 9 glass bottles for one emerald.{{only\|java}} === Crafting ingredients === {{Crafting usage\|Glass Bottle}} == Sounds == {{edition\|java}}: {{Sound table \|rowspan=2 \|sound=Bottle fill water1.ogg \|sound2=Bottle fill water2.ogg \|sound3=Bottle fill water3.ogg \|sound4=Bottle fill water4.ogg \|subtitle=Bottle fills \|source=block \|description=When a bottle is filled with a liquid from a cauldron, or honey from a bee nest or beehive \|id=item.bottle.fill \|translationkey=subtitles.item.bottle.fill \|volume=1.0 \|pitch=1.0 \|distance=16}} {{Sound table \|subtitle=Bottle fills \|source=neutral \|description=When a bottle is filled with water from a water source \|id=item.bottle.fill \|translationkey=subtitles.item.bottle.fill \|volume=1.0 \|pitch=1.0 \|distance=16}} {{Sound table \|sound=Bottle empty1.ogg \|sound2=Bottle empty2.ogg \|subtitle=Bottle empties \|source=block \|description=When a water bottle is emptied \|id=item.bottle.empty \|translationkey=subtitles.item.bottle.empty \|volume=1.0 \|pitch=1.0 \|distance=16}} {{Sound table \|sound=Bottle fill dragon breath1.ogg \|sound2=Bottle fill dragon breath2.ogg \|subtitle=Bottle fills \|source=neutral \|description=When a bottle is filled with dragon's breath \|id=item.bottle.fill_dragonbreath \|translationkey=subtitles.item.bottle.fill \|volume=1.0 \|pitch=1.0 \|distance=16 \|foot=1}} {{edition\|java}}: {{Sound table \|type=bedrock \|rowspan=4 \|sound=Water Splash Old.ogg \|source=block \|description=When water from a bottle is placed in a cauldron<wbr><ref group=sound name=potionsplash>{{Bug\|MCPE-174867}}</ref> \|id=cauldron.fillwater \|volume=0.1 \|pitch=1.0}} {{Sound table \|source=block \|description=When water from a bottle is taken from a cauldron<wbr><ref group=sound name=potionsplash/> \|id=cauldron.takewater \|volume=0.1 \|pitch=1.0}} {{Sound table \|source=block \|description=When a bottle is filled with a potion from a cauldron<wbr><ref group=sound name=potionsplash/> \|id=cauldron.fillpotion \|volume=0.1 \|pitch=1.0}} {{Sound table \|source=block \|description=When a potion bottle is emptied into a cauldron<wbr><ref group=sound name=potionsplash/> \|id=cauldron.takepotion \|volume=0.1 \|pitch=1.0}} {{Sound table \|sound=Bottle empty1.ogg \|sound2=Bottle empty2.ogg \|source=sound<!--bottle--> \|description=When a bottle is emptied<wbr>{{Upcoming\|BE 1.20.40}} \|id=bottle.empty \|volume=1.0 \|pitch=1.0}} {{Sound table \|sound=Bottle fill water1.ogg \|sound2=Bottle fill water2.ogg \|sound3=Bottle fill water3.ogg \|sound4=Bottle fill water4.ogg \|source=sound<!--bottle--> \|description=When a bottle is filled<wbr>{{Upcoming\|BE 1.20.40}} \|id=bottle.fill \|volume=1.0 \|pitch=1.0}} {{Sound table \|sound=Fill water bucket1.ogg \|sound2=Fill water bucket2.ogg \|sound3=Fill water bucket3.ogg \|source=block \|description=When a bottle is filled with honey from a bee nest or beehive<wbr><ref group=sound>{{Bug\|MCPE-53881}}</ref> \|id=bucket.fill_water \|volume=1.0 \|pitch=1.0}} {{Sound table \|sound=Bottle fill dragon breath1.ogg \|sound2=Bottle fill dragon breath2.ogg \|source=sound \|description=When a bottle is filled with dragon's breath \|id=bottle.dragonbreath \|volume=0.7<wbr>{{Until\|BE 1.20.40}}<br>1.0<wbr>{{Upcoming\|BE 1.20.40}} \|pitch=1.0 \|foot=1}} == Data values == === ID === {{edition\|java}}: {{ID table \|edition=java \|showforms=y \|generatetranslationkeys=y \|displayname=Glass Bottle \|spritetype=item \|nameid=glass_bottle \|form=item \|foot=1}} {{edition\|bedrock}}: {{ID table \|edition=bedrock \|shownumericids=y \|showforms=y \|notshowbeitemforms=y \|generatetranslationkeys=y \|displayname=Glass Bottle \|spritetype=item \|id=427 \|nameid=glass_bottle \|form=item \|foot=1}} == Achievements == {{Load achievements\|You Need a Mint;Local Brewery;Bee Our guest}} == Advancements == {{load advancements\|Local Brewery;You Need a Mint;Bee Our Guest}} == History == {{History\|java}} {{History\|\|1.0.0\|snap=Beta 1.9 Prerelease 2\|[[File:Glass Bottle JE1 BE1.png\|32px]] Added glass bottles.}} {{History\|\|\|snap=Beta 1.9 Prerelease 3\|[[File:Water Bottle JE1 BE1.png\|32px]] Glass bottles have been given their sole function of picking up [[water]] for the [[brewing]] of [[potion]]s.}} {{History\|\|1.4.2\|snap=12w38b\|[[Witch]]es now have a chance of [[drops\|dropping]] glass bottles upon [[death]].}} {{history\|\|1.9\|snap=15w33a\|[[File:Dragon's Breath JE1 BE1.png\|32px]] Glass bottles can now be used to obtain [[dragon's breath]].}} {{history\|\|\|snap=15w43a\|A glass bottle can be found in the [[brewing stand]] in an [[igloo]] basement.}} {{history\|\|\|snap=15w43c\|The glass bottle has been removed from igloo basements.}} {{History\|\|\|snap=15w50a\|Added [[sound]]s: <code>item.bottle.fill</code> and <code>item.bottle.fill_dragonbreath</code>.}} {{History\|\|1.13\|snap=17w47a\|Prior to [[1.13/Flattening\|''The Flattening'']], this [[item]]'s numeral ID was 374.}} {{History\|\|1.14\|snap=18w43a\|[[File:Glass Bottle JE2 BE2.png\|32px]] [[File:Water Bottle JE2 BE2.png\|32px]] [[File:Dragon's Breath JE2 BE2.png\|32px]] The textures of glass bottles, [[water bottle]]s and [[dragon's breath]] have been changed.}} {{History\|\|\|snap=19w11a\|Cleric [[villager]]s now [[trading\|buy]] glass bottles.}} {{History\|\|1.15\|snap=19w34a\|[[File:Honey Bottle JE1.png\|32px]] Glass bottles can now be used to collect [[Honey Bottle\|honey]]. \|[[Dispenser]]s may now use glass bottles to collect [[water]] and honey.}} {{History\|\|\|snap=19w46a\|Using glass bottles to collect honey now unlocks the [[Bee Our Guest]] advancement.}} {{History\|\|1.19\|snap=22w11a\|Converting [[dirt]], [[coarse dirt]] or [[rooted dirt]] into [[mud]] using a [[water bottle]], [[splash water bottle]] or [[lingering water bottle]] now leaves the player with an empty glass bottle.}} {{History\|pocket alpha}} {{History\|\|v0.12.1\|snap=build 1\|[[File:Glass Bottle JE1 BE1.png\|32px]] Added glass bottles.}} {{History\|\|v0.14.0\|snap=build 1\|Glass bottles can now be used to empty [[cauldron]]s filled with [[water]] or [[potion]]s. \|Glass bottles can now be dropped by [[witch]]es. \|Potions and [[splash potion]]s can now be used to fill cauldrons, which turns them into glass bottles.}} {{History\|pocket}} {{History\|\|1.0.0\|snap=alpha 0.17.0.1\|[[File:Dragon's Breath JE1 BE1.png\|32px]] Glass bottles can now be used to obtain [[dragon's breath]]. \|[[Lingering potion]]s can now be used to fill [[cauldron]]s, which turns them into glass bottles.}} {{History\|bedrock}} {{History\|\|1.10.0\|snap=beta 1.10.0.3\|[[File:Glass Bottle JE2 BE2.png\|32px]] The texture of glass bottles has been changed.}} {{History\|\|1.11.0\|snap=beta 1.11.0.4\|Glass bottles can now be [[trading\|sold]] to cleric [[villager]]s.}} {{History\|\|1.14.0\|snap=beta 1.14.0.1\|[[File:Honey Bottle BE1.png\|32px]] Glass bottles can now be used to collect [[Honey Bottle\|honey]]. \|[[Dispenser]]s may now use glass bottles to collect [[water]] and honey.}} {{History\|console}} {{History\|\|xbox=TU7\|xbone=CU1\|ps=1.0\|wiiu=Patch 1\|[[File:Glass Bottle JE1 BE1.png\|32px]] Added glass bottles.}} {{History\|PS4}} {{History\|\|1.90\|[[File:Glass Bottle JE2 BE2.png\|32px]] The texture of glass bottles has been changed.}} {{History\|new 3ds}} {{History\|\|0.1.0\|[[File:Glass Bottle JE1 BE1.png\|32px]] Added glass bottles.}} {{History\|\|1.7.10\|[[File:Dragon's Breath JE1 BE1.png\|32px]] Glass bottles can now be used to obtain [[dragon's breath]].}} {{history\|foot}} == Issues == {{issue list}} ==References== {{Reflist}} {{Items}} [[cs:Lahvička]] [[de:Glasflasche]] [[es:Frasco de cristal]] [[fr:Fiole]] [[hu:Üvegpalack]] [[it:Ampolla]] [[ja:ガラス瓶]] [[ko:유리병]] [[nl:Glazen fles]] [[pl:Szklana butelka]] [[pt:Frasco]] [[ru:Колба]] [[zh:玻璃瓶]] [[Category:Renewable resources]]</li><li>[[Black Dye\|Black Dye]]<br/>{{Item \| image = Black Dye.png \| renewable = Yes \| stackable = Yes (64) }} '''Black dye''' is a [[Dye#Primary\|primary color dye]] similar to an [[ink sac]]. == Obtaining == === Trading === [[Wandering trader]]s have a chance to [[trading\|trade]] 3 black dyes for 1 [[emerald]].{{only\|java}} === Crafting === {{Crafting \|head=1 \|showname=0 \|Ink Sac \|Output=Black Dye \|type=Material }} {{Crafting \|Wither Rose \|Output=Black Dye \|type=Material \|foot=1 }} == Usage == {{dye usage}} === Crafting ingredient === {{crafting usage\|ignore=Banner\|continue=1}} {{banner crafting usage}} === Loom ingredient === {{Banner loom usage\|Black Dye}} === Trading === Apprentice-level Shepherd villagers have a 20%{{only\|bedrock}} or {{frac\|2\|7}}{{only\|java}} chance to buy 12 black dye for an emerald. == Data values == === ID === {{edition\|java}}: {{ID table \|edition=java \|showforms=y \|generatetranslationkeys=y \|displayname=Black Dye \|spritetype=item \|nameid=black_dye \|form=item \|foot=1}} {{edition\|bedrock}}: {{ID table \|edition=bedrock \|showaliasids=y \|shownumericids=y \|showforms=y \|notshowbeitemforms=y \|generatetranslationkeys=y \|displayname=Black Dye \|spritetype=item \|nameid=black_dye \|aliasid=dye / 16 \|id=395 \|form=item \|translationkey=item.dye.black_new.name \|foot=1}} == History == {{History\|java}} {{History\|\|1.14\|snap=18w43a\|[[File:Black Dye JE1 BE1.png\|32px]] Added black dye.}} {{History\|\|\|snap=18w44a\|Black dyes now can changed the text color on the [[sign]]s to black.}} {{History\|\|\|snap=19w05a\|Added the [[wandering trader]], which sell black dyes.}} {{History\|\|\|snap=19w11a\|Black dyes can now be [[trading\|bought]] by shepherd villagers.}} {{History\|\|1.15\|snap=Pre-release 1\|Black dye can now be used to craft [[prismarine\|dark prismarine]], just like [[Bedrock Edition]].}} {{History\|\|1.17\|snap=20w45a\|Black dyes can now used to craft newly added [[black candle]]s.}} {{History\|\|\|snap=21w19a\|Black dyes can no longer used to craft black candles.}} {{History\|\|\|snap=Pre-release 1\|Black dyes can once again used to craft black candles.}} {{History\|\|1.20<br>(Experimental)\|link=1.19.3\|snap=22w42a\|Black dyes now can change the text color on [[hanging sign]]s to black.}} {{History\|bedrock}} {{History\|\|1.8.0\|snap=beta 1.8.0.10\|[[File:Black Dye JE1 BE1.png\|32px]] Added black dye.}} {{History\|\|1.11.0\|snap=beta 1.11.0.4\|Black dye can now be [[trading\|sold]] to shepherd [[villager]]s.}} {{history\|\|1.13.0\|snap=beta 1.13.0.9\|Black dye can now be [[crafting\|crafted]] from [[flower\|wither roses]].}} {{History\|\|1.16.100\|snap=beta 1.16.100.56\|The ID of black dye has been changed from <code>dye/16</code> to <code>black_dye</code>.}} {{History\|ps4}} {{History\|\|1.83\|[[File:Black Dye JE1 BE1.png\|32px]] Added black dye.}} {{History\|foot}} == Issues == {{issue list}} {{Items}} [[Category:Dyes]] [[Category:Renewable resources]] [[de:Schwarzer Farbstoff]] [[es:Tinte negro]] [[fr:Teinture noire]] [[ja:黒色の染料]] [[ko:검은색 염료]] [[pl:Czarny barwnik]] [[pt:Corante preto]] [[th:สีย้อมสีดำ]] [[zh:黑色染料]]</li></ul>	beta 1.16.210.51	Goats now only drop 2 goat horns each.
		Goats now drop 1-2 mutton.
		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.53	Goats now avoid walking onto powder snow while path-finding.

↑ BE-104156
↑ 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)

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)

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)

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)

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? --Lxazl5770_zh.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

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

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.

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

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.
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)

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)

User page problem.

For any user page but mine it always says "This user has not filled out their profile page yet." I can tell this is a problem as while looking at the abuse filter, examining individual changes, when I go to a user page that the person edited and added stuff, it says this, and it says this in the for the page history too. Gameking1happy (talk) 19:15, 16 February 2021 (UTC)

Yes, it is showing, this is to prevent other people from editing their userpage. --TreeIsLife (talk) 19:18, 16 February 2021 (UTC)

That is nonesense. See my comment below. Dhranios (talk) (Join the wiki videos project!) 19:18, 16 February 2021 (UTC)

Known fandom problem, they're looking into it; you can still view the pages if you use visual editor. Dhranios (talk) (Join the wiki videos project!) 19:18, 16 February 2021 (UTC)

Yes, doesn't make sense why they would prevent others from viewing your userpage. I would get preventing editing, but viewing is obviously has no harm and is most likely a glitch on Fandom's part. James Haydon (talk) 19:20, 16 February 2021 (UTC)

Reinstate Tutorials/Obtaining discontinued blocks and items

Currently, Tutorials/Obtaining discontinued blocks and items is a page with no text other than a soft redirect to a Miraheze about discontinued blocks and items.

I am in favour of reinstating this page because it is useful, and has all the information needed on one page. Many players find it neat and challenging to grab all of these discontinued items and show them off to their friends. The page before it’s update was very helpful and detailed all of the blocks, plus a nice roadmap for gaining all of the blocks through their versions. The Miraheze page has all of the items on separate pages, no roadmap, and full of fluff that can be made into a short paragraph if rewritten. John502 (talk) 03:32, 18 February 2021 (UTC)

The reason why the migrate it is because maybe they feel it as an official wiki for obtaining discontinued blocks and items. TheGreatSpring (talk) 03:51, 18 February 2021 (UTC)

"All of the items on separate pages" because it's a wiki, "no roadmap" that's just not true, "and full of fluff that can be made into a short paragraph" no not at all, it says as much info as it can. Tho I may be biased because I made and own the bedrock edition version of that wiki --Gtbot2007 (talk) 15:26, 18 February 2021 (UTC)

"all the information needed on one page" seriously? What existed on those pages was a tiny fraction of what has been obtainable throughout the game's history. - User-12316399 (talk) 19:38, 18 February 2021 (UTC)

Why are there no quotes?

The wandering trader used to have quote from "Meet the Wandering Trader", but that is no more. The same applies to other pages. Why?--Olivia Capucine Elisabet (talk) 16:13, 21 February 2021 (UTC)

Because there was a community decision about a year ago to scrap these, as they hogged page space while providing little to no useful information to the article. - User-12316399 (talk) 16:56, 21 February 2021 (UTC)

Yes I do think that having quotes on every page is stupid, especially if they aren't related to said thing but only mention it. The only exception is on pages for items and locations in Minecraft Dungeons since they have these quotes in-game rather than in a YouTube video. James Haydon (talk) 17:03, 21 February 2021 (UTC)

Apperance sections

Should we have them or not?--Olivia Capucine Elisabet (talk) 17:44, 21 February 2021 (UTC)

Signatures

I'm not sure if this is related to UCP but several signatures are resetting including mine, TheGreatSpring's, and Madminecrafter12. Is their any fix to this, is it related to UCP?Humiebee^{talk contribs} 01:43, 22 February 2021 (UTC)

Hey Humie! I'd imagine it is related to UCP, since your userpage isn't showing up for me either, which is a "known bug" with UCP (this roll out is going great, huh?)

For what it's worth, I can see your sig right now.-- DigiDuncan (talk) 02:18, 22 February 2021 (UTC)

Don't call me humie I recently changed my signature to attempt to reverse the bug. This bug also happened before the user page bug.Humiebee^{talk contribs} 03:04, 22 February 2021 (UTC)

Sorry, didn't know about the name thing 😅 Wish I had more info, all I know is that this UCP rollout has messed up a lot, including my own personal Wiki and account, and many features of the platform. -- DigiDuncan (talk) 03:49, 22 February 2021 (UTC)

Securly for Chromebooks blocks part of content.

Securly for Chromebooks blocks part of content (right for Useful pages). I reached 400 edits! Android 1123581321 (talk) 12:55, 24 February 2021 (UTC)

[1] BE-104156

[2] MCPE-104159 — "Goat attacks armor stands" — resolved as "Fixed".

[1]

[2]