Minecraft Wiki talk:Community portal/Archive 32

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)

More Facts In Did You Know...

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

The did you know relies on a certain template, Template:DidYouKnow. It does not always have the same facts, it refreshes every day. There are not 5 facts, here are all the facts. If you want to add more facts, you can add them in the editcopy. Keep in mind you can edit the editcopy and add what you think is good, but it will not show up on the front page until an admin decides they belong there. Blockofnetherite ^{Talk Contributions} 04:45, 27 December 2020 (UTC)

Oh, cool! I guess this topic is totally irrelevant then. || Remember this thing? File:Nether Reactor Core Revision 1.png Because I do. --Ninji2701 13:50, 27 December 2020 (UTC)

Repurpose

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

5000 content pages milestone

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

I noticed that a few days back, so you aren't the first to see this. James Haydon (talk) 04:02, 16 January 2021 (UTC)

BDJP007301 created the 5000th article yesterday. Also, does this also includes deleted pages? TheGreatSpring (talk) 04:22, 16 January 2021 (UTC)

It does not, hence why it has become this milestone several times already. Dhranios (talk) (Join the wiki videos project!) 05:53, 16 January 2021 (UTC)

Well there are subpages of articles which are not articles (many of them are templates only meant to be transcluded on one page) which are counted as articles, which means there are probably less than 5,000 "proper" articles. (Note that redirects, project pages, template pages, category pages, file pages, user pages, etc. are not counted as articles. )Fadyblok240 (talk) 17:36, 21 January 2021 (UTC)

Articles about Mojang employees: A proposal

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

• We should try to include as much information on employees that is publicly available through reliable sources, whether it be through LinkedIn profiles, interviews with publications such as news sites, or simply through the Twitter accounts of the employees themselves. As long as the information is available publicly, it should be documented on the wiki, sourced back to the article or tweet in question.

• However, there has to be a limit as to what information should indeed be allowed on here. Of course, its general understanding that emails, addresses, and phone numbers are never to be added to articles out of respect for privacy. In regards to concessions that have been made in the past, such as the situation with Ez, or retracting information that had been OK up until recently, such concessions should be reviewed as to whether they should remain as is, or be considered null and void pending as to when this policy does become active.

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

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

“

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

„

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

I still think this should be taken further, and say that articles should only exist for notable employees where the majority of the content is about their work. We shouldn't encourage going into details about personal lives and such, which having all these stub articles does.  Nixinova   T   C   19:29, 2 February 2021 (UTC)

Definitely keep the personal life stuff to a minimum at best. BDJP ^(t|c) 20:42, 2 February 2021 (UTC)

In my opinion, we should keep any pages that have a lot of content (pages without stubs) but pages with stubs should be put into like a draft. Anyone is free to make a page but it needs more content. As for not having like personal details, I also support that but a notable exception would be Helen Zbihlyj as she directly put a little bit of her personal life on her user page as it is a primary and the most reliable source possible. I would like the employee pages to also have more about their work as well and all those stub articles can be clumped into an Employees article.

All in all, I  Support keeping all pages which have enough content and  Removing or converting any pages with a stub and have no content (for instance, Peter Hont which is just one of the many pages that has no info, only saying that they work in Minecraft Dungeons.) For birth dates, I really don't see any harm if they posted it on twitter or some other social media thing. Also I wish to  Remove all pages with no sources as well.Humiebee (talk) 21:35, 2 February 2021 (UTC)

I’ve created an example of how an expanded article would look here. BDJP ^(t|c) 01:02, 9 February 2021 (UTC)

I  Support the revised article.Humiebee (talk) 03:05, 15 February 2021 (UTC)

I'm going to wait on any further comments for a week, but if there are no further objections then I will implement this on the bio page. BDJP ^(t|c) 14:36, 19 February 2021 (UTC)

Support the new proposal, but it would make absolutely no sense for the new guideline to be part of the style guide but not part of the notability guideline. What about splitting the notability guidelines from the style guide? Fadyblok240 (talk) 23:12, 19 February 2021 (UTC)

Are pufferfish passive, neutral or hostile

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

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

Splitting PS4 history

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

 Neutral, while it is done the same with PE and bedrock, PS4 is a legacy console edition, as it was also replaced by bedrock. I don't see harm in doing it this way, nor harm in reverting it. Dhranios (talk) (Join the wiki videos project!) 12:13, 6 January 2021 (UTC)

 Oppose PS4 is part of LCE, no reason to split its history.  Nixinova   T   C   19:29, 7 January 2021 (UTC)

 Comment I get your point, but the PS4 edition outlasted all the other Legacy Console editions, and was the only legacy console version to have the Texture Update. James Haydon (talk) 19:32, 7 January 2021 (UTC)

Barely, only for like 10 updates.  Nixinova   T   C   21:27, 10 January 2021 (UTC)

True, they only spanned 1.14, or Bedrock Edition 1.8.0 - 1.13.0.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‌/Yes‌ Any thoughts?Humiebee^{talk contribs} 22:35, 7 January 2021 (UTC)

The same can be said the other way around. If we end up saying yes in 1.17, while it's not in the snapshots yet, people who open the snapshots will be presented with misinformation.

It's better to stick with the current latest release and snapshot info, not the whole planned update. (Plans can change, after all...) Dhranios (talk) (Join the wiki videos project!) 23:33, 7 January 2021 (UTC)

True... but it would be more helpful in general becuase more Java Edition players use Java Edition 1.16.4 than .Humiebee^{talk contribs} 23:37, 7 January 2021 (UTC)

For those people, those templates don't really concern them. When the update releases, they'll check the update page instead and go from there. Dhranios (talk) (Join the wiki videos project!) 23:40, 7 January 2021 (UTC)

Wanted Page: Moving minecart

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

Yes. They are entities. TheGreatSpring (talk | contribs) (Tagalog translation) 00:28, 11 January 2021 (UTC)

Minecarts themselves are already entities. Moving minecrafts are no different, just that they are moving, similar to a player walking. So no need for a new pageHumiebee (talk) 00:39, 11 January 2021 (UTC)

Exactly, in the same way as evoker fangs. They only damage they player and have no real behavior nor do they interact with them. James Haydon (talk) 00:51, 11 January 2021 (UTC)

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

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

Upcoming Bedrock Edition 1.17.0 {{Extension DPL}}<ul><li>[[Dye|Dye]]<br/>{{Item | title = Dyes | image = White Dye.png | extratext = View [[#Gallery|all renders]] | renewable = Yes | stackable = Yes (64) }} '''Dyes''' are a set of sixteen items used to change the color of [[wool]], [[carpet]]s, [[terracotta]], [[concrete powder]], [[glass]], [[shulker box]]es, [[bed]]s, [[candle]]s, the patterns on [[banner]]s, [[firework star]]s, certain mobs, and text on [[sign]]s and [[hanging sign]]s. {{IN|bedrock}} they can also be used to dye water in a [[cauldron]] (which is thereafter used to dye leather [[armor]]); {{in|java}} leather armor can be dyed directly. {{IN|education}} dyes can also be used to dye [[balloon]]s and [[glow stick]]s. {{IN|bedrock|education}}, [[bone meal]], [[ink sac]]s, [[lapis lazuli]], and [[cocoa bean]]s can generally substitute for [[white dye]], [[black dye]], [[blue dye]], and [[brown dye]], respectively, in crafting recipes and for use in dyeing items or mobs. However, they have other important uses that aren't related to color, and are therefore not considered true dyes. They are mentioned in this article only in regard to their use as dyeing agents; see their individual articles for complete information about them. [[File:Dye Recipes.png|400px|thumb|A guide for creating all the dyes]] == Obtaining == <!--[[File:Dye Chart.png|350px|thumb|A guide to crafting all the dyes.{{until|java 1.14}}]]--> Dyes can be produced by crafting them from plants (mainly flowers), by crafting dyes of different colors together, by smelting plants, or by trading with a [[wandering trader]]. {{loadPage|Crafting/Dye|Crafting|h3}} === Smelting === {{smelting|head=1|Sea Pickle|Lime Dye|0,2}} {{smelting|foot=1|Cactus|Green Dye|1||b=Lapis Lazuli|c=Any fuel|d=1}} === Trading === [[Wandering trader]]s can sell 3 dyes for an [[emerald]]. {{IN|bedrock}}, they can also sell 3 lapis lazuli, bone meal, cocoa beans, or ink sacs for one emerald. Apprentice-level cleric [[villager]]s sell one lapis lazuli per emerald. === Chest loot === {{#invoke:LootChest|base3|blue-dye,green-dye,orange-dye,light-blue-dye,yellow-dye,white-dye}} === Other === Ink sacs can also be created using 1 iron, 1 sulfur, and 4 oxygen in the [[compound creator]]. {{only|bedrock|education}} == Usage == Similar to their use in crafting, [[bone meal]], [[ink sac]]s, [[lapis lazuli]], and [[cocoa beans]] can be substituted for the corresponding dye in any of the following usages unless otherwise specified.{{only|bedrock}} <!--- sections are ordered by craftable dyeable blocks, dyeable items, version exclusive sections, and non-crafting miscellaneous uses---> === Dyeing wool and mobs === Players can dye wool by placing [[wool]] and any dye in a crafting grid. {{Crafting |nocat=1 |Any Wool |Matching Dye |Output=Any Wool }} Dyes can be {{control|use|text=used}} on sheep to change the color of the wool. Shearing a colored sheep drops the corresponding color of the wool, and the sheep retains the color when the wool regenerates. [[Breeding]] colored sheep produces a lamb colored as one of the parent sheep, or a color resulting from the combination of both parents' color. The color combining follows the same rules that dyes use – red and yellow sheep produce an orange lamb, but a blue and yellow sheep cannot create a green lamb. The unlimited reproduction of colored sheep makes dyeing and shearing sheep infinitely more efficient than just dyeing wool directly. Dye can also be used on a tamed [[wolf]] or [[cat]] to change the color of its collar from the default red to the color of the dye. === Dyeing carpets === Carpets can be dyed. {{Crafting |Any Carpet |Matching Dye |Output= Matching Carpet |type= Building block }} === Dyeing terracotta === [[Terracotta]] can be dyed by placing 8 blocks around a dye on a crafting table. {{Crafting |nocat=1 |A1=Terracotta |B1=Terracotta |C1=Terracotta |A2=Terracotta |B2=Matching Dye |C2=Terracotta |A3=Terracotta |B3=Terracotta |C3=Terracotta |Output=Matching Dyed Terracotta,8 }} === Creating concrete powder === Dyes can also be used to craft [[concrete powder]], which can then be set into their respective [[concrete]] blocks (they cannot be dyed directly). {{Crafting |nocat=1 |Sand |Gravel |Sand |Gravel |Matching Dye |Gravel |Sand |Gravel |Sand |Output=Matching Concrete Powder,8 }} === Staining glass === [[Stained glass]] can be stained by placing 8 blocks of glass around a dye on a [[crafting table]]. Just like regular glass, stained glass can be crafted into stained glass panes. The recipe for this is the same as with regular glass. {{Crafting |nocat=1 |A1=Glass |B1=Glass |C1=Glass |A2=Glass |B2=Matching Dye |C2=Glass |A3=Glass |B3=Glass |C3=Glass |Output=Matching Stained Glass,8 |head=1 }} {{Crafting |nocat=1 |A1= Glass Pane |B1= Glass Pane |C1= Glass Pane |A2= Glass Pane |B2= Matching Dye |C2= Glass Pane |A3= Glass Pane |B3= Glass Pane |C3= Glass Pane |Output= Matching Stained Glass Pane,8 |type= Decoration block |foot=1 }} === Dyeing shulker boxes === [[Shulker box]]es are generated in a light shade of purple (like the [[purpur block]]), but can be dyed any color. They can also be re-dyed as often as desired. {{Crafting |ignoreusage=1 |showname=1 |Any Shulker Box |Matching Dye |Output=Matching Shulker Box }} === Dyeing beds === Players can dye beds by placing a [[bed]] and any color dye in a crafting grid. {{Crafting |nocat=1 |Any Bed |Matching Dye |Output=Matching Bed }} === Dyeing candles === Players can dye [[candles]] by placing an undyed candle and any color dye in a crafting grid. {{Crafting |ignoreusage=1 |Candle |Matching Dye |Output=Matching Dyed Candle }} === Banner patterns === {{main|Banner#Patterns}} Dyes are used in most banner patterns to determine the pattern and color displayed. === Dyeing armor === [[File:DyeGraph2.png|200px|thumb|A graph showing all combinations of two dyes on a [[tunic]].]] Leather [[armor]] can be dyed by: * Crafting dyes with a piece of leather armor or leather [[horse armor]].{{Only|java}} * Dousing the leather armor or leather [[horse armor]] in a [[cauldron]] to which dyes have been added.{{Only|bedrock}} There are 5,713,438<ref>https://anrar4.github.io/DyeLeatherArmor/</ref> (34.1% of sRGB) colors leather armor can be, as it is possible to put more than one dye on the crafting bench alongside the leather armor. Armor can be dyed multiple times with previous colors affecting the final outcome. Colored armor can be reverted to their original color using a [[cauldron]] with undyed water. The game has a specific formula for calculating the color of dyed armor: each color, in the RGB color model, has a red value, green value, and blue value. For each dye in the crafting grid, and the armor itself (if it is already dyed), the red, green, and blue values are added to running totals. In addition, a running total of the highest value (be it red, green, or blue) is also kept. After this, each total is divided by the number of colors used. This effectively produces the average red, green, blue, and maximum values. The maximum value of the average RGB values is also calculated. Finally, each average RGB value is multiplied by the average maximum value and divided by the maximum of the average RGB values. The modified average RGB values are then used as the final color. This procedure can be summed up with the following equations: for each color (all "total" variables start at 0 before counting): totalRed = totalRed + redValue totalGreen = totalGreen + greenValue totalBlue = totalBlue + blueValue totalMaximum = totalMaximum + max(redValue, greenValue, blueValue) numberOfColors = numberOfColors + 1 averageRed = totalRed / numberOfColors averageGreen = totalGreen / numberOfColors averageBlue = totalBlue / numberOfColors averageMaximum = totalMaximum / numberOfColors maximumOfAverage = max(averageRed, averageGreen, averageBlue) gainFactor = averageMaximum / maximumOfAverage resultRed = averageRed * gainFactor resultGreen = averageGreen * gainFactor resultBlue = averageBlue * gainFactor Due to the way this formula works, the resulting color can never be darker than the average of the input colors and is often lighter and more saturated. Of course, the resulting color can never be lighter or more saturated than the lightest or most saturated input color. In addition, this formula never creates an RGB value higher than 255 (which would be invalid in the 8-bit RGB color model). If leather armor is renamed on an [[anvil]], it retains its name when dyed or undyed. ;Mixing Samples : {{ItemSprite|Yellow Dye}} + {{ItemSprite|Yellow Dye}} = {{Tint|leather-chestplate| #{{CalcDye| yellow=2 }} | code=1}} : {{ItemSprite|Red Dye}} + {{ItemSprite|Blue Dye}} + {{ItemSprite|White Dye}} = {{Tint|leather-chestplate| #{{CalcDye| red=1 | blue=1 | white=1}} | code=1}} : {{ItemSprite|Green Dye}} + {{ItemSprite|Red Dye}} + {{ItemSprite|Pink Dye}} = {{Tint|leather-chestplate| #{{CalcDye| green=1 | red=1 | pink=1}} | code=1}} === Dyeing firework stars === A [[firework star]] can have a single color or a combination of up to eight colors when crafted with dyes. Adding one or more dyes to a crafted firework star adds a "fade to color" effect to it, overwriting any existing fade colors. {{Crafting |head=1 |ignoreusage=1 |ingredients=[[Gunpowder]] +<br>Any Dye (1–8) +<br>Extra ingredient (optional) |Gunpowder |Matching Dye |Diamond;Glowstone Dust;Head;Gold Nugget;Feather;Fire Charge; |Output=Matching Firework Star }} {{Crafting |ignoreusage=1 |Matching Firework Star |Any Dye |Output=Matching Firework Star |foot=1 }} === Creating balloons === Dye can be used to craft balloons.{{only|education}} {{Crafting |nocat=1 |A1= Latex |B1= Matching Dye |C1= Latex |A2= Latex |B2= Helium |C2= Latex |A3= Latex |B3= Lead |C3= Latex |Output= Matching Balloon }} === Creating glow sticks === Dye can also be used to craft glow sticks.{{only|education}} {{Crafting |nocat=1 |A1= Polyethylene |B1= Hydrogen Peroxide |C1= Polyethylene |A2= Polyethylene |B2= Matching Dye |C2= Polyethylene |A3= Polyethylene |B3= Luminol |C3= Polyethylene |Output= Matching Glow Stick }} === Dyeing water inside cauldrons === Water can be dyed in a cauldron by holding any dye in the hand and pressing {{Ctrl|use}} on a cauldron filled with water.{{only|bedrock}} === Signs === Dye can be {{control|used}} on a [[sign]] or a [[hanging sign]] to change the text color. {{IN|bedrock}}, [[ink sac]]s cannot be used for this purpose; black dye must be used to change the text to black. === Trading === Apprentice, journeyman and expert-level shepherd [[villager]]s buy any of the 12 dyes for an [[emerald]]. == Color values == The "color codes" are used to determine the color imparted on sheep, wolf and cat collars, firework stars, [[beacon]] beams, and dyed leather armor. The hex value is shown in the extended tooltips of dyed leather armor; however, to set the color using an NBT data tag in a [[command]], the decimal value must be used instead. The color values for firework stars are slightly different from the ones listed below, and use [[Item colors#Firework stars|these values]] instead. {| class="wikitable" style="margin:2px; border: 1px solid silver; text-align: left;" data-description="Data values" ! rowspan=2 | Description ! colspan=2 style="text-align:center" | Color Code |- ! Dec ! <abbr title="Hexadecimal color code">Hex</abbr> |- | style="text-align:center" | White || 16383998 || {{color|#F9FFFE}} |- | style="text-align:center" | Light gray || 10329495 || {{color|#9D9D97}} |- | style="text-align:center" | Gray || 4673362 || {{color|#474F52}} |- | style="text-align:center" | Black || 1908001|| {{color|#1D1D21}} |- | style="text-align:center" | Brown || 8606770 || {{color|#835432}} |- | style="text-align:center" | Red || 11546150 || {{color|#B02E26}} |- | style="text-align:center" | Orange || 16351261 || {{color|#F9801D}} |- | style="text-align:center" | Yellow || 16701501 || {{color|#FED83D}} |- | style="text-align:center" | Lime || 8439583 || {{color|#80C71F}} |- | style="text-align:center" | Green || 6192150 || {{color|#5E7C16}} |- | style="text-align:center" | Cyan || 1481884|| {{color|#169C9C}} |- | style="text-align:center" | Light blue || 3847130 || {{color|#3AB3DA}} |- | style="text-align:center" | Blue || 3949738 || {{color|#3C44AA}} |- | style="text-align:center" | Purple || 8991416 || {{color|#8932B8}} |- | style="text-align:center" | Magenta || 13061821 || {{color|#C74EBD}} |- | style="text-align:center" | Pink || 15961002 || {{color|#F38BAA}} |} == Sounds == {{edition|java}}: {{Sound table |rowspan=2 |sound=Dye.ogg |subtitle=Dye stains |source=block |description=When dye is used on a [[sign]] |id=item.dye.use |translationkey=subtitles.item.dye.use |volume=1.0 |pitch=1.0/0.9/0.95/1.1 |distance=16}} {{Sound table |subtitle=Dye stains |source=player |description=When dye is used on a [[sheep]] |id=item.dye.use |translationkey=subtitles.item.dye.use |volume=1.0 |pitch=1.0/0.9/0.95/1.1 |distance=16 |foot=1}} {{edition|bedrock}}: {{Sound table |type=bedrock |sound=Dye.ogg |source=sound |description=When dye is used on a sign |id=sign.dye.use |volume=1.0 |pitch=1.0}} {{Sound table |rowspan=3 |sound=Water Splash Old.ogg |source=block |description=When dye is added to a cauldron |id=cauldron.adddye |volume=0.1 |pitch=1.0}} {{Sound table |source=block |description=When armor is dyed using a cauldron |id=cauldron.dyearmor |volume=0.1 |pitch=1.0}} {{Sound table |source=block |description=When dye is removed from armor using a cauldron |id=cauldron.cleanarmor |volume=0.1 |pitch=1.0 |foot=1}} == Achievements == {{load achievements|Rainbow Collection;Tie dye outfit}} == Video == {{Video note|These videos are outdated, as it does not include details of the [[Java Edition 1.7.2|1.7.2]] update's changes to the dyeing system/production chain.}} <div style="text-align:center"> <span style="display:inline-block">{{yt|8YD7oauNZHE}}</span> <span style="display:inline-block">{{yt|7tETaRt7STM}}</span> </div> == History == {{History|java beta}} {{History||January 3, 2011|link=https://web.archive.org/web/0/http://notch.tumblr.com/post/2582321901/2011-here-we-go|Notch mentions adding a "paint" feature if he can figure out how.}} {{History||January 10, 2011<ref group="n">Supposed time when fragment was filmed. Based on modified date of client.jar/gui/trap.png in [[Beta 1.2]].</ref>|link=https://www.youtube.com/watch?v=cBF2ugTzXqQ&t=181s|[[File:Red Dye (pre-release).png|32px]] Shown rose red in development as part of [[Minecraft: The Story of Mojang]].}} {{History||1.2|[[File:Ink Sac JE1 BE1.png|32px]] [[File:Red Dye JE1 BE1.png|32px]] [[File:Green Dye JE1 BE1.png|32px]] [[File:Cocoa Beans JE1 BE1.png|32px]] [[File:Lapis Lazuli JE1 BE1.png|32px]] [[File:Purple Dye JE1 BE1.png|32px]] [[File:Cyan Dye JE1 BE1.png|32px]] [[File:Light Gray Dye JE1 BE1.png|32px]] [[File:Gray Dye JE1 BE1.png|32px]] [[File:Pink Dye JE1 BE1.png|32px]] [[File:Lime Dye JE1 BE1.png|32px]] [[File:Yellow Dye JE1 BE1.png|32px]] [[File:Light Blue Dye JE1 BE1.png|32px]] [[File:Magenta Dye JE1 BE1.png|32px]] [[File:Orange Dye JE1 BE1.png|32px]] [[File:Bone Meal JE1 BE1.png|32px]] Added dyes. |[[File:Black Dye (Recreated).png|32px]] [[File:Red Dye (pre-release).png|32px]] [[File:Green Dye (Recreated).png|32px]] [[File:Brown Dye (Recreated).png|32px]] [[File:Blue Dye (Recreated).png|32px]] [[File:Purple Dye (Recreated).png|32px]] [[File:Cyan Dye (Recreated).png|32px]] [[File:Light Gray Dye (Recreated).png|32px]] [[File:Gray Dye (Recreated).png|32px]] [[File:Pink Dye (Recreated).png|32px]] [[File:Lime Dye (Recreated).png|32px]] [[File:Yellow Dye (Recreated).png|32px]] [[File:Light Blue Dye (Recreated).png|32px]] [[File:Magenta Dye (Recreated).png|32px]] [[File:Orange Dye (Recreated).png|32px]] [[File:White Dye (Recreated).png|32px]] Leftovers of old textures can be seen in [[items.png]] with 100% opacity. The white dye texture was reused for [[Sugar]]. | The colors were as follows:{{verify|Did the color codes remain the same between Beta 1.2 and Java 1.11.2?}} {{:Color/Java Edition dye colors before 17w06a}} }} {{History|java}} {{History||1.1|snap=11w49a|[[Sheep]] can now regrow their [[wool]] by eating [[grass block|grass]]. Dyed sheep regrow wool in their new color.}} {{History||1.3.1|snap=12w19a|[[File:Cocoa Beans JE2.png|32px]] The texture of [[cocoa beans]] has been changed.}} {{History|||snap=1.3|[[File:bone meal changes.gif|32px]] The textures of [[bone meal]], [[cactus green]], cocoa beans and [[rose red]] have been changed. The textures have been lowered one pixel.}} {{History||1.4.2|snap=12w34a|Added the ability to dye leather [[armor]] and [[wolf]] collars.}} {{History||1.4.4|snap=1.4.3|Color codes have been changed. The colors of red, brown, blue, purple, cyan, pink, light blue, magenta and orange were adjusted a little vividly.}} {{History||1.6.1|snap=13w19a|[[Stained clay]] can now be crafted using dyes.}} {{history||1.7.2|snap=13w36a|With the addition of new [[flower]]s, many secondary and tertiary dyes are now primary dyes.}} {{History|||snap=13w41a|[[Stained glass]] can now be crafted using dyes.}} {{History||1.8|snap=14w02a|As cleric [[villager]]s now sell lapis lazuli, all dyes have become fully renewable.}} {{History|||snap=14w30a|Added [[banner]]s, which can be dyed.}} {{History||1.9|snap=15w34a|Added [[shield]]s, which can be dyed indirectly by applying a matching [[banner]].}} {{History||1.11|snap=16w39b|Dyes are now used to change the color of [[shulker box]]es.}} {{History||1.12|snap=17w06a|Dyes are now used to craft [[concrete powder]]. |Color codes have been changed. All colors are adjusted more vividly. The changes were as follows: {{:Color/Java Edition dye color changes in 17w06a}} |Light blue dye, stained glass, and stained glass panes, did not change colors in this update. This means that they still use old colors.<ref name="unchanged dyes">{{Bug|MC-214643}}<br>{{Bug|MC-214641}}</ref> }} {{History|||snap=17w15a|Dyes can now apply color to white [[bed]]s.}} {{History||1.13|snap=17w47a|The different data values for the <code>dye</code> ID have been split up into their own IDs.}} {{History||1.14|snap=18w43a|[[Bone meal]], [[ink sac]]s, [[cocoa beans]] and [[lapis lazuli]] are no longer considered dyes. |[[File:White Dye JE1 BE1.png|32px]] [[File:Black Dye JE1 BE1.png|32px]] [[File:Brown Dye JE1 BE1.png|32px]] [[File:Blue Dye JE1 BE1.png|32px]] Added [[white dye|white]], [[black dye|black]], [[brown dye|brown]] and [[blue dye]]s. |"Rose Red", "Dandelion Yellow" and "Cactus Green" have been renamed to "Red Dye", "Yellow Dye" and "Green Dye", respectively. |[[Glass pane]]s and [[carpet]]s can now be dyed. |[[File:Light Gray Dye JE2 BE2.png|32px]] [[File:Gray Dye JE2 BE2.png|32px]] [[File:Red Dye JE2 BE2.png|32px]] [[File:Orange Dye JE2 BE2.png|32px]] [[File:Yellow Dye JE2 BE2.png|32px]] [[File:Lime Dye JE2 BE2.png|32px]] [[File:Green Dye JE2 BE2.png|32px]] [[File:Cyan Dye.png|32px]] [[File:Light Blue Dye JE2 BE2.png|32px]] [[File:Purple Dye JE2 BE2.png|32px]] [[File:Magenta Dye JE2 BE2.png|32px]] [[File:Pink Dye JE2 BE2.png|32px]] The textures of light gray, gray, red, orange, yellow, lime, green, cyan, light blue, purple, magenta, and pink dyes, have been changed. The color texture for light blue dye was not changed to reflect the updated colors from 1.12.<ref name="unchanged dyes"></ref>}} {{History|||snap=18w44a|The color of the text on [[sign]]s can now be changed with dye.}} {{History|||snap=18w49a|Yellow dyes can now be found in [[chest]]s in [[village]] mason houses.}} {{History|||snap=18w50a|Green dyes can now be found in [[chest]]s in [[desert]] [[village]] houses.}} {{History|||snap=19w05a|Added the [[wandering trader]], which can sell any type of dye.}} {{History|||snap=19w11a|All 16 types of dyes can now be [[trading|bought]] by shepherd villagers.}} {{History||1.16.2|snap=Pre-release 2|Reversed the order of dyes to match other colored items in the [[Creative inventory]].<ref name="reverse dye">{{Bug|MC-136553}}</ref> |Regrouped dyes in the Creative inventory such that white, blue, brown, and black dyes are within and not [[cocoa beans]], [[ink sacs]], [[lapis lazuli]], and [[bone meal]].<ref name="regroup dye">{{Bug|MC-177684}}</ref>}} {{History||1.17|snap=20w45a|Added [[candle]]s, which can be dyed.}} {{History|||snap=21w03a|Added a sound for applying dyes.}} {{History|||snap=21w19a|Candles can no longer be dyed.}} {{History|||snap=Pre-release 1|Candles can now once again be dyed.}} {{History||1.20<br>(Experimental)|link=1.19.3|snap=22w42a|The color of the text on [[hanging sign]]s can now be changed with dye.}} {{History||1.20<br>(Experimental)|link=1.19.4|snap=23w07a|[[Torchflower]]s can now be crafted into orange dye.|[[Pink petals]] can now be crafted into pink dye.}} {{History||1.20|snap=23w12a|[[Pitcher plant]]s can now be crafted into cyan dye.|Blue, light blue, orange, white, and yellow dye can now be found in [[suspicious gravel]] and [[suspicious sand]] in [[trail ruins]].}} {{History|||snap=23w14a|Pitcher plants can now craft two [[cyan dye]] instead of one.}} {{History|||snap=23w16a|Blue, light blue, orange, white, and yellow dye no longer generates in [[suspicious sand]] in [[trail ruins]].|Due to the split of the archaeological loot tables for the suspicious gravel within the [[trail ruins]]; blue, light blue, orange, white, and yellow dye now are in the common loot.}} {{History|pocket alpha}} {{History||v0.3.0|[[File:Bone Meal JE1 BE1.png|32px]] [[File:Light Gray Dye JE1 BE1.png|32px]] [[File:Gray Dye JE1 BE1.png|32px]] [[File:Ink Sac JE1 BE1.png|32px]] [[File:Cocoa Beans JE1 BE1.png|32px]] [[File:Red Dye JE1 BE1.png|32px]] [[File:Orange Dye JE1 BE1.png|32px]] [[File:Yellow Dye JE1 BE1.png|32px]] [[File:Lime Dye JE1 BE1.png|32px]] [[File:Green Dye JE1 BE1.png|32px]] [[File:Cyan Dye JE1 BE1.png|32px]] [[File:Light Blue Dye JE1 BE1.png|32px]] [[File:Lapis Lazuli JE1 BE1.png|32px]] [[File:Purple Dye JE1 BE1.png|32px]] [[File:Magenta Dye JE1 BE1.png|32px]] [[File:Pink Dye JE1 BE1.png|32px]] Added dyes. Only [[dandelion yellow]] and [[lapis lazuli]] are currently obtainable and have functionality.}} {{History||v0.3.2|[[Cactus green]] is now obtainable by smelting [[cacti]].}} {{History||v0.3.3|[[Bone meal]] is now obtainable via [[crafting]].}} {{History||v0.4.0|[[Cyan dye]], [[light blue dye]], [[lime dye]], [[magenta dye]], [[orange dye]], [[pink dye]], and [[purple dye]] are now obtainable via crafting. |[[Rose red]] is now obtainable by smelting red [[mushroom]]s. |All available dyes, excluding bone meal, can now be used to craft their respective [[wool]] color.}} {{History||v0.8.0|snap=build 1|[[File:Cocoa Beans JE3 BE2.png|32px]] The texture of cocoa beans has been changed.}} {{History|||snap=build 3|[[Ink sac]]s, [[cocoa bean]]s, [[gray dye]], and [[light gray dye]] are now available in the [[creative]] [[inventory]]. |Rose red can now be obtained from [[beetroot]]s.}} {{History||v0.9.0|snap=build 1|Cocoa beans can now be obtained from [[cocoa pod]]s. |The [[rose]] has been removed and replaced with a new poppy [[flower]] that can be crafted into rose red.}} {{History|||snap=build 3|All new [[flower]]s can now be [[crafting|crafted]] into dyes. Because of this, many secondary and tertiary dyes are now primary dyes. |[[Gray dye]] and [[light gray dye]] can now be obtained in [[survival]].}} {{History|||snap=build 11|[[Terracotta|Stained clay]] can now be crafted using dyes.}} {{History||v0.11.0|snap=build 1|[[Ink sac]]s can now be obtained from [[squid]]. |Added the ability to dye [[wolf]] collars.}} {{History||v0.12.1|snap=build 1|Red [[mushroom]]s can no longer be smelted to obtain [[rose red]].}} {{History||v0.14.0|snap=build 1|[[Cauldron]]s now used for leather dyeing, by applying a dye to a [[water]]-filled cauldron.}} {{History||v0.16.0|snap=build 1|[[Cocoa bean]]s can no longer be crafted.}} {{History|pocket}} {{History||1.0.0|snap=alpha 0.17.0.1|Added a ''Dye'' button for [[sheep]]. |Added [[shulker]]s, which can be dyed. |Added [[stained glass]]. Stain glass cannot be [[crafting|crafted]], but purple glass generates in [[end city|end cities]].}} {{History||1.1.0|snap=alpha 1.1.0.0|Dyes can now apply color to a white [[bed]]s. |Dyes are now used to craft [[concrete powder]]. |The color palette has been changed.}} {{History|bedrock}} {{History||1.2.0|snap=beta 1.2.0.2|Dyes can now be used for [[banner]] crafting. |Dyes can now be used to craft [[firework star]]s. |[[Stained glass]] is now [[crafting|craftable]], using dyes.}} {{History||1.4.0|snap=beta 1.2.20.1|[[Lime dye]] can now be obtained from smelting [[sea pickle]]s. |Dyes can now used to craft [[glow stick]]s and [[balloon]]s.}} {{History||1.8.0|snap=beta 1.8.0.8|Dyes can now be used to dye [[cat]] collars.}} {{History|||snap=beta 1.8.0.10|[[File:White Dye JE1 BE1.png|32px]] [[File:Black Dye JE1 BE1.png|32px]] [[File:Brown Dye JE1 BE1.png|32px]] [[File:Blue Dye JE1 BE1.png|32px]] Added [[white dye|white]], [[brown dye|brown]], [[black dye|black]] and [[blue dye]]s, which can be crafted from [[lapis lazuli]], [[bone meal]], [[cocoa beans]] and [[ink sac]]s. This, however, the later four still use as dyes.<ref>{{Bug|MCPE-42473}}</ref> |"Rose Red", "Dandelion Yellow" and "Cactus Green" have been renamed to "Red Dye", "Yellow Dye" and "Green Dye", respectively.}} {{History||1.9.0|snap=beta 1.9.0.0|Blue and white dye can now be obtained from [[cornflower]]s and [[lily of the valley]]s.}} {{History||1.10.0|snap=beta 1.10.0.3|[[Glass pane]]s and [[carpet]]s can now be dyed. |Only a single dye is now required to apply a banner pattern in a [[loom]]. |Various dyes except black dye, white dye, brown dye and blue dye are now [[trading|sold]] by [[wandering trader]]s. |[[File:Bone Meal JE2 BE2.png|32px]] [[File:Light Gray Dye JE2 BE2.png|32px]] [[File:Gray Dye JE2 BE2.png|32px]] [[File:Ink Sac JE2 BE2.png|32px]] [[File:Cocoa Beans JE4 BE3.png|32px]] [[File:Red Dye JE3 BE3.png|32px]] [[File:Orange Dye JE2 BE2.png|32px]] [[File:Yellow Dye JE2 BE2.png|32px]] [[File:Lime Dye JE2 BE2.png|32px]] [[File:Green Dye JE2 BE2.png|32px]] [[File:Cyan Dye.png|32px]] [[File:Light Blue Dye JE2 BE2.png|32px]] [[File:Lapis Lazuli JE2 BE2.png|32px]] [[File:Purple Dye JE2 BE2.png|32px]] [[File:Magenta Dye JE2 BE2.png|32px]] [[File:Pink Dye JE2 BE2.png|32px]] The textures of bone meal, light gray, gray, ink sac, cocoa beans, red, orange, yellow, lime, green, cyan, light blue, lapis lazuli, purple, magenta, and pink dyes have been changed.}} {{History||1.11.0|snap=beta 1.11.0.4|Dye can now be [[trading|sold]] to shepherd [[villager]]s.}} {{History||1.16.210|snap=beta 1.16.210.59|The color of the text on [[sign]]s can now be changed with dye.}} {{History|||snap=beta 1.16.210.60|The ability to dye the color of the text on [[sign]]s was temporarily removed.}} {{History||1.16.220|snap=beta 1.16.220.50|The color of the text on [[sign]]s can now be changed with dye again.}} {{History||1.17.10|snap=beta 1.17.10.22|Added [[candles]], which can be dyed.}} {{History|console}} {{History||xbox=TU1|xbone=CU1|ps=1.0|wiiu=Patch 1|switch=1.0.1|[[File:Bone Meal JE1 BE1.png|32px]] [[File:Light Gray Dye JE1 BE1.png|32px]] [[File:Gray Dye JE1 BE1.png|32px]] [[File:Ink Sac JE1 BE1.png|32px]] [[File:Cocoa Beans JE1 BE1.png|32px]] [[File:Red Dye JE1 BE1.png|32px]] [[File:Orange Dye JE1 BE1.png|32px]] [[File:Yellow Dye JE1 BE1.png|32px]] [[File:Lime Dye JE1 BE1.png|32px]] [[File:Green Dye JE1 BE1.png|32px]] [[File:Cyan Dye JE1 BE1.png|32px]] [[File:Light Blue Dye JE1 BE1.png|32px]] [[File:Lapis Lazuli JE1 BE1.png|32px]] [[File:Purple Dye JE1 BE1.png|32px]] [[File:Magenta Dye JE1 BE1.png|32px]] [[File:Pink Dye JE1 BE1.png|32px]] Added dyes.}} {{History||xbox=TU9|[[File:Cocoa Beans JE3 BE2.png|32px]] The texture of cocoa beans has been changed.}} {{History||xbox=none|xbone=none|ps=1.83|wiiu=none|switch=none|[[File:White Dye JE1 BE1.png|32px]] [[File:Black Dye JE1 BE1.png|32px]] [[File:Brown Dye JE1 BE1.png|32px]] [[File:Blue Dye JE1 BE1.png|32px]] Added [[white dye|white]], [[black dye|black]], [[brown dye|brown]], and [[blue dye|blue]] dyes, which can crafted from [[bone meal]], [[ink sac]], [[cocoa beans]], and [[lapis lazuli]]. |"Rose Red", "Dandelion Yellow" and "Cactus Green" have been renamed to "Red Dye", "Yellow Dye" and "Green Dye", respectively.}} {{History||ps=1.90|[[File:Bone Meal JE2 BE2.png|32px]] [[File:Light Gray Dye JE2 BE2.png|32px]] [[File:Gray Dye JE2 BE2.png|32px]] [[File:Ink Sac JE2 BE2.png|32px]] [[File:Cocoa Beans JE4 BE3.png|32px]] [[File:Red Dye JE2 BE2.png|32px]] [[File:Orange Dye JE2 BE2.png|32px]] [[File:Yellow Dye JE2 BE2.png|32px]] [[File:Lime Dye JE2 BE2.png|32px]] [[File:Green Dye JE2 BE2.png|32px]] [[File:Cyan Dye.png|32px]] [[File:Light Blue Dye JE2 BE2.png|32px]] [[File:Lapis Lazuli JE2 BE2.png|32px]] [[File:Purple Dye JE2 BE2.png|32px]] [[File:Magenta Dye JE2 BE2.png|32px]] [[File:Pink Dye JE2 BE2.png|32px]] The textures of bone meal, light gray, gray, ink sac, cocoa beans, red, orange, yellow, lime, green, cyan, light blue, lapis lazuli, purple, magenta, and pink dyes have been changed.}} {{History|3ds}} {{History||0.1.0|[[File:Bone Meal JE1 BE1.png|32px]] [[File:Light Gray Dye JE1 BE1.png|32px]] [[File:Gray Dye JE1 BE1.png|32px]] [[File:Ink Sac JE1 BE1.png|32px]] [[File:Cocoa Beans JE3 BE2.png|32px]] [[File:Red Dye JE1 BE1.png|32px]] [[File:Orange Dye JE1 BE1.png|32px]] [[File:Yellow Dye JE1 BE1.png|32px]] [[File:Lime Dye JE1 BE1.png|32px]] [[File:Green Dye JE1 BE1.png|32px]] [[File:Cyan Dye JE1 BE1.png|32px]] [[File:Light Blue Dye JE1 BE1.png|32px]] [[File:Lapis Lazuli JE1 BE1.png|32px]] [[File:Purple Dye JE1 BE1.png|32px]] [[File:Magenta Dye JE1 BE1.png|32px]] [[File:Pink Dye JE1 BE1.png|32px]] Added dyes from [[Pocket Edition v0.15.4 alpha]].}} {{History|foot}} <gallery> Pre-release dyes.png|Pre-release dye textures hidden within [[Items.png]]. </gallery> ;Notes {{reflist|group=n}} == Gallery == <gallery> White Dye.png|White Dye Light Gray Dye.png|Light Gray Dye Gray Dye.png|Gray Dye Black Dye.png|Black Dye Brown Dye.png|Brown Dye Red Dye.png|Red Dye Orange Dye.png|Orange Dye Yellow Dye.png|Yellow Dye Lime Dye.png|Lime Dye Green Dye.png|Green Dye Cyan Dye.png|Cyan Dye Light Blue Dye.png|Light Blue Dye Blue Dye.png|Blue Dye Purple Dye.png|Purple Dye Magenta Dye.png|Magenta Dye Pink Dye.png|Pink Dye </gallery> ==Issues== {{issue list}} == Trivia == * Players can obtain each one of every color with 1 cocoa bean, 2 yellow dye, 2 ink sac, 3 green dye, 4 lapis lazuli, 4 red dye, and 6 bone meal (2 bones). * The dyed sheep breeding behavior mirrors [[wikipedia:Lamarckism|Lamarck's theory]], in which the organisms evolve inheriting the external changes and adaptations of the previous generation, transmitting them to their offspring. * In ''Bedrock Edition'', tertiary colors, along with their regular crafting recipes, can be crafted with primary colors. E.g.: Magenta can be crafted with one rose red and two bone meals. * The colors of the dyes match the chat colors in [[color codes]] except for brown (dye only), light aqua, and gold (color codes only). * The texture for light blue dye still uses the color from prior to the 1.12 World of Color update.<ref name="unchanged dyes"></ref> == References == {{reflist}} == External Links == * Tools for calculating leather dye combination: [https://minecraft.tools/en/armor.php minecraft.tools] (webapp); [https://github.com/pudquick/pyMCdyes/ pyMCDyes] (open-source Python script, outdated); [https://anrar4.github.io/DyeLeatherArmor/ DyeLeatherArmor]: a tool for calculating an exact crafting recipe for any sRGB color {{Items}} [[Category:Dyes]] [[Category:Renewable resources]] [[cs:Barvivo]] [[de:Farbstoff]] [[es:Tinte]] [[fr:Teinture]] [[hu:Színezés]] [[it:Colorante]] [[ja:染料]] [[ko:염료]] [[nl:Kleurstof]] [[pl:Barwniki]] [[pt:Corante]] [[ru:Красители]] [[th:สีย้อม]] [[uk:Барвники]] [[zh:染料]]</li><li>[[Reality Vision|Reality Vision]]<br/>{{Joke feature}} {{Item | title = Reality Vision | image = Reality Vision.png | renewable = No | stackable = Yes (64) }} The '''Reality vision''' was a joke [[helmet]]. == Usage == Reality vision was equipped via the [[helmet]] slot. When equipped, it showed a [[wikipedia:Mini-map|minimap]] in the bottom-center of the screen (which moved when the [[player]]'s camera moves). The minimap showed all [[chunk]]s that were currently rendered. The player's location was represented by a green [[beacon]] beam marker on the map. It displayed a vision overlay (similar to the [[pumpkin]] overlay). The overlay would change to a new overlay if the player went into third person (unlike the pumpkin overlay), which made the screen appear like an old [[wikipedia:Television|television]] screen. The overlay was called <code>cantseeshit<!-- Do not change this; this is that word that is actually used-->captain.png</code> in the assets folder. It activated a [[Shaders|shader]] when equipped (<code>scan_pincushion</code>). == Sounds == {{Sound table |sound=Equipvr.ogg |subtitle=''None'' |source=player |description=When equipped |id=item.reality_vision.use |translationkey=''None'' |volume=1.0 |pitch=1.0 |distance=16 |foot=1}} == Data values == === ID === {{ID table |edition=java |shownumericids=y |showforms=y |generatetranslationkeys=y |displayname=Reality Vision |spritetype=item |nameid=reality_vision |id=500 |form=item |translationkey=item.realityVision.name |foot=1}} == History == {{History|java}} {{History||1.RV-Pre1|[[File:Reality_Vision_(item).png|32px]] [[File:Reality Vision.png|32px]] Added reality vision.}} {{History|foot}} == Issues == Reality Vision is an unsupported item due to being an [[Wikipedia:April Fools' Day|April Fools']] joke, and therefore such issues relating to them will not be fixed. == Trivia == * [[Sign]]s display the text "OBEY" while equipped, a reference to the movie [[wikipedia:They Live|''They Live'']]. == Gallery == <gallery> Sign2.png|The [[sign]] texture found in the game files. OBEY.png|OBEY seen in a sign. OBEY sign in 1.RV-Pre1..png|OBEY seen in a sign, but seen from a better perspective. TechGear.png|A [[player]] wearing reality vision, featured in this [[wikipedia:April Fools' Day|April Fools']] joke version. </gallery> {{Items}} {{Jokes}} [[Category:Non-renewable resources]] [[Category:Joke items]] [[pt:Visão da realidade]] [[es:Reality Vision]]</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>[[Redstone Comparator|Redstone Comparator]]<br/>{{Block | image = | image2 = | transparent = Yes | light = No | tool = any | renewable = Yes | stackable = Yes (64) | flammable = No | lavasusceptible = No | group = Redstone Comparator | group2 = Subtracting | group3 = Powered | group4 = Powered+Subtracting | 1-1 = Redstone Comparator.png | 2-1 = Subtracting Redstone Comparator.png | 3-1 = Powered Redstone Comparator.png | 4-1 = Powered Subtracting Redstone Comparator.png }} {{Many images}} A '''redstone comparator''' is a [[block]] that can produce an [[Redstone Dust|output signal]] from its front by reading [[chest]]s, [[lectern]]s, [[beehive]]s and similar blocks, or repeat a signal without changing its strength. It can also be set to either stop outputting a signal when its side input recieves a stronger one (front torch off), or subtract its side input's signal strength from its output (front torch on). == Obtaining == === Natural generation === Redstone comparators generate in [[Ancient City|ancient cities]]. === Breaking === A redstone comparator can be broken instantly with any [[tool]], or by hand, and drops itself as an item. {{Breaking row|Redstone Comparator|horizontal=y}} A redstone comparator is removed and dropped as an item if: * its attachment block is moved, removed, or destroyed; * [[water]] flows into its space;{{only|java}} * a [[piston]] tries to push it or moves a block into its space. If [[lava]] flows into a redstone comparator's space, the redstone comparator is destroyed without dropping as an item. === Crafting === {{Crafting |B1=Redstone Torch |A2=Redstone Torch |B2=Nether Quartz |C2=Redstone Torch |A3=Stone |B3=Stone |C3=Stone |Output= Redstone Comparator |type=Redstone }} == Usage == A redstone comparator can be placed on the top of any [[opaque]] block with a solid full-height top surface (including upside-down [[slab]]s and upside-down [[stairs]]). {{IN|be}}, a comparator can also be placed on [[wall]]s and fences. For more information about placement on transparent blocks, see [[Opacity/Placement]]. The redstone comparator has a front and a back — the arrow on the top of the comparator points to the front. When placed, the comparator faces away from the player. The comparator has two miniature redstone torches at the back and one at the front. The back torches turn on when the comparator's output is greater than zero (the arrow on top also turns red). The front torch has two states that can be toggled by {{control|using}} the comparator: * Down and unpowered (indicating the comparator is in "comparison mode") * Up and powered (indicating the comparator is in "subtraction mode") The redstone comparator can take a signal strength input from its rear as well as from both sides. Side inputs are accepted only from [[redstone dust]], [[block of redstone]], [[redstone repeater]]s, other comparators, and [[observer]]s in specific scenarios. The redstone comparator's front is its output. It takes 1 [[redstone tick]] (2 game ticks, or 0.1 seconds barring lag) for signals to move through a redstone comparator, either from the rear or from the sides. This applies to changing signal strengths as well as simply to turning on and off. Redstone comparators check their power state before their scheduled ticks update. This results in redstone comparators not usually responding to 1-tick fluctuations of power or signal strength — for example, a [[clock circuit|1-clock]] input is treated as always off from the side, and always on from the rear. This happens because the signal changes back to its original state before the redstone comparator checks its input states. However, certain setups such as powering any input with two separate observer pulses at the same time will cause a redstone comparator to respond to 2 gametick pulses. The redstone comparator has four functions: maintain signal strength, compare signal strength, subtract signal strength, and measure certain block states (primarily the fullness of containers). === Maintain signal strength === A redstone comparator with no powered sides outputs the same signal strength as its rear input. === Compare signal strength === [[File:Comparators Explained.png|Comparators in comparison mode.|thumb]] A redstone comparator in comparison mode (front torch down and unpowered) compares its rear input to its two side inputs. If either side input is greater than the rear input, the comparator output turns off. If neither side input is greater than the rear input, the comparator outputs the same signal strength as its rear input. The formula for calculating the output signal strength is as follows: <code>output = rear × [[Wikipedia:Iverson bracket|[]]'''''left''''' ≤ '''''rear''''' AND '''''right''''' ≤ '''''rear'''''[[Wikipedia:Iverson bracket|<nowiki>]]]</code> {{-}} === Subtract signal strength === [[File:Redstone comparator.png|thumb|The greatest of the side inputs A and C is subtracted from the rear input B, outputting 1. If either A or C were greater than B, it would output 0.]] A redstone comparator in subtraction mode (front torch up and powered) subtracts the signal strength of the higher side input from the signal strength of the rear input. <code>output = max('''''rear''''' − max('''''left''', '''right'''''), 0)</code> For example: if the signal strength is 6 at the left input, 7 at the right input and 4 at the rear, the output signal has a strength of ''max(4 − max(6, 7), 0) = max(4−7, 0) = max(−3, 0) = 0''. If the signal strength is 9 at the rear, 2 at the right input and 5 at the left input, the output signal has a strength of ''max(9 − max(2, 5), 0) = max(9−5, 0) = 4''. === Measure block state === {{Schematic | caption = A redstone comparator can measure the fullness of a chest, as well as other block states, even through an opaque block. |rd-ew!|rc-w!|ch|SB|rc-e!|rd-ew! }} A redstone comparator treats certain blocks behind it as power sources and outputs a signal strength proportional to the block's state. The comparator may be separated from the measured block by an opaque block. However, {{in|je}}, if the opaque block is powered to signal strength 15, then the comparator outputs 15 no matter the fullness of the container.<ref>{{bug|MC-64394}} (resolved as "Works As Intended")</ref> [[Category:Java Edition specific information]] {{-}} ==== Fullness of containers ==== {| class="wikitable floatright" style="margin-left: 0.5em; margin-right: 0; text-align: center;" |+ Minimum Items for Container Signal Strength |- !Containers !{{BlockSprite|Furnace|link=Furnace}}<br>{{BlockSprite|Blast Furnace|link=Blast Furnace}}<br>{{BlockSprite|Smoker|link=Smoker}} !{{BlockSprite|Hopper|link=Hopper}}<br>{{EntitySprite|Minecart with Hopper|link=Minecart with Hopper}}<br>{{BlockSprite|Brewing Stand|link=Brewing Stand}} !{{BlockSprite|Dispenser|link=Dispenser}}<br>{{BlockSprite|Dropper|link=Dropper}} !{{BlockSprite|Chest|link=Chest}}<br>{{EntitySprite|Minecart with Chest|link=Minecart with Chest}}<br>{{BlockSprite|Shulker Box|link=Shulker Box}}<br>{{BlockSprite|Barrel|link=Barrel}} ![[Double Chest|{{Schematic|size=16|ch-s|-|ch-n}} ]] !{{BlockSprite|Jukebox|link=Jukebox}} |- !Total Slots !3!!5!!9!!27!!54!!1 |- !Power Level ! colspan="5" |Number of Items !Music Disc |- |0||0||0||0||0||0||No disc |- |1||1||1||1||1||1||"13" |- |2||14||23||42||1s 60||3s 55||"cat" |- |3||28||46||1s 19||3s 55||7s 46||"blocks" |- |4||42||1s 5||1s 60||5s 51||11s 37||"chirp" |- |5||55||1s 28||2s 37||7s 46||15s 28||"far" |- |6||1s 5||1s 51||3s 14||9s 42||19s 19||"mall" |- |7||1s 19||2s 10||3s 55||11s 37||23s 10||"mellohi" |- |8||1s 32||2s 32||4s 32||13s 32||27s||"stal" |- |9||1s 46||2s 55||5s 10||15s 28||30s 55||"strad" |- |10||1s 60||3s 14||5s 51||17s 23||34s 46||"ward" |- |11||2s 10||3s 37||6s 28||19s 19||38s 37||"11" |- |12||2s 23||3s 60||7s 5||21s 14||42s 28||"wait" |- |13||2s 37||4s 19||7s 46||23s 10||46s 19||"Pigstep" |- |14||2s 51||4s 42||8s 23||25s 5||50s 10||"Otherside"<br>"Relic" |- |15||3s||5s||9s||27s||54s||"5" |} A redstone comparator can output a signal indicating how full a container is. (0 for empty, 15 for full, etc.) The table on the right is described more in detail, later in this section. Containers that can be measured by a comparator include: * {{BlockLink|Furnace}} * {{BlockLink|Blast Furnace}} * {{BlockLink|Smoker}} * {{BlockLink|Brewing Stand}} * {{BlockLink|Hopper}} * {{ItemLink|Minecart with Hopper}} on top of a [[detector rail]] * {{BlockLink|Dispenser}} * {{BlockLink|Dropper}} * {{BlockLink|Chest}} * {{BlockLink|Trapped Chest}} * {{ItemLink|Minecart with Chest}} on top of a [[detector rail]] * {{BlockLink|Barrel}} * {{SchematicSprite|size=16|ch-e}}{{SchematicSprite|size=16|ch-w}} Large chest * {{SchematicSprite|size=16|ch-e}}{{SchematicSprite|size=16|ch-w}} Large trapped chest * {{BlockLink|Shulker Box}} (any color) Generally speaking, the comparator output signal strength represents the average fullness of the slots, based on how many of that item form a full stack (64, 16, or 1 for non-stackable items). The ''Minimum Items for Container Signal Strength'' table (right) shows the minimum '''''full-stack-equivalent (FSE)''''' to produce different signal strengths from common containers. A '''''full-stack-equivalent''''' quantifies how many normal 64-stackable items are needed to output a corresponding signal strength. The 's' is a constant 64, with the additional amount needed following after. One may also consider the terms: '''c''umulative-weight''''' or '''''weighted-sum''''' instead of '''''full-stack-equivalent'''''. Items that stack to a max of 16 ([[snowball]]s, [[sign]]s, [[ender pearl]]s, etc.), contribute +4 to the ''full-stack-equivalent'' for each unity (count of 1 item). Similarly, items that stack to 1 ([[minecart]], [[boat]], etc.) contribute +64, and items that stack to 64 contribute +1. Example 1: 3 ender pearls will contribute a 3 x 4 = 12 ''full-stack-equivalent''. Example 2: 16 ender pearls and 60 redstone dust contributes a 16x4 + 60x1 = 124 ''full-stack-equivalent''. Example 3: 1 minecart and 60 redstone dust contributes a 1x64 + 60x1 = 124 ''full-stack-equivalent''. Example 4: To produce a signal strength of 10 from a hopper, one requires a ''full-stack-equivalent'' of at least 3s + 14 = 206 but strictly less than than 3s + 37 = 229. This can be done with 3 minecarts, and 14 dirt. When a comparator measures a large chest or large trapped chest, it measures the entire large chest (54 slots), not just the half directly behind the comparator. A chest or trapped chest that cannot be opened (either because it has an opaque block, [[ocelot]], or [[cat]] above it) always produces an output of 0 no matter how many items are in the container — shulker boxes can always be measured, even if they cannot open. ;Calculating signal strength from items :When a container is empty, the output is off. :When it is not empty, the output signal strength is calculated as follows: :<code>'''''signal strength''''' = floor(1 + (('''''sum of all slots' fullnesses''''') / ('''''number of slots in container''''')) × 14)</code> :<code>fullness of a slot = '''''number of items in slot''''' / '''''max stack size for this type of item'''''</code> :''Example:'' 300 blocks in a dispenser (which has 9 slots), where each block stacks to a maximum of 64 has a 300 ''full-stack-equivalent.'' This produces an output with a signal strength of 8: <blockquote> 1 + ((300 items / 64 items per slot) / 9 slots) × 14 = 8.292, floored is 8 </blockquote> ;Calculating items from signal strength :It can be useful in redstone circuits to use containers with comparators to create signals of a specific strength. The number of items required in a container to produce a signal of desired strength is calculated as follows: :<code>items required = max('''''desired signal strength''''', roundup(('''''total slots in container''''' × 64 / 14) × (desired signal strength − 1)))</code> :''Example:'' To use a furnace (which has 3 slots) to create a strength 9 signal, players need 110 items: <blockquote> max(9, (3×64/14) × (9−1)) = 109.714, rounded up is 110 </blockquote> {{-}} ==== Miscellaneous ==== [[File:Comparator storage.png|Comparators used to measure containers.|thumb]] Some non-container blocks can also be measured by a redstone comparator: ;{{BlockLink|Beehive}} and {{BlockLink|Bee nest}} : A hive or nest outputs a signal strength equal to the amount of honey in the hive/nest. ;{{BlockLink|Cake}} : A cake outputs a signal strength relative to the amount of cake remaining. Each slice is worth 2 signal strength, with 7 total slices, for an output of 14 for a full cake. [[File:Cauldron Redstone Strength Values.png|Cauldron signal strength|thumb]] ;{{BlockLink|Cauldron}} : A cauldron outputs different signal strengths depending on how much water or powdered snow is inside. From completely empty to completely full, the output values are 0, 1, 2, and 3. If lava or powder snow is inside, the strength is always 3. [[File:Composter Redstone Strength Values.png|Composter signal strength|thumb]] ;{{BlockLink|Composter}} : A composter outputs different signal strengths depending on the level inside. From completely empty to completely full, the output values are 0, 1, 2, 3, 4, 5, 6, 7 and 8. ;{{Anchor|CommandBlock}}{{BlockLink|Command Block}} : A command block stores the "success count" of the last command executed, which represents the number of times the most recently used command of this command block succeeded. A "success" is defined by the [[command]]'s success conditions: if a red error message is returned in the chat, the command was not successful. : Most commands can succeed once per execution, but certain commands (such as those that accept players as arguments) can succeed multiple times, and the comparator outputs the number of times it succeeded (maximum 15 when sent to redstone dust, but in the code it is able to go up to the 32-bit integer limit, and can be used in contraptions with no redstone dust with those values). : A command block continues to store the success count of the last command executed until it executes its command again, thus the comparator continues to output the same signal strength even after the command block is no longer being activated (it doesn't turn off when the signal to the command block turns off). ;{{BlockLink|End Portal Frame}} : An end portal frame outputs a full signal of 15 if it contains an [[eye of ender]] and zero otherwise. [[File:Item frame and comparator.png|A comparator can measure the presence and rotation of an item frame's contents.|thumb]] ;{{EntityLink|Item Frame}} : A comparator can measure the state of an [[item frame]]'s contents. An item frame comparator outputs 0 if the item frame is empty, or 1 to 8 for any item depending on its rotation: 1 at initial placement, plus 1 for each 45° of rotation for a maximum of 8. : For an item frame that holds a map, a unit of rotation is 90° instead of 45°, but a comparator still outputs power levels 1 to 8. It takes two full rotations to cycle through all comparator outputs, and each orientation of the map corresponds to two output levels that differ by 4. : The comparator must be placed behind the block the item frame is attached to, facing away from the item frame. The block must be a full block, and the item frame cannot be submerged in water. Having a sign in the same block as the item frame will prevent the frame from sending a signal as well.{{only|java}} ;{{BlockLink|Jukebox}} : A jukebox outputs a signal strength indicating which music disc is currently playing. See the ''Minimum Items for Container Signal Strength'' table above. ;{{BlockLink|Lectern}} : A lectern outputs a signal strength that depends on what page the player is currently on. The calculation used is: :<code>'''''signal strength''''' = floor(1 + (('''''current page''''' - 1) / ('''''number of pages in book''''' - 1)) × 14)</code> :This results in page 1 having a signal strength of 1, and the last page having a signal strength of 15. The exception is a single page book, which will output a signal strength of 15. :For example, a book with 15 pages will output a signal equal to the current page number. A book with 5 pages will output signal strengths of 1, 4, 8, 11 and 15 for the different pages. A book with 100 pages will have the signal strength increase to the next level on pages 1, 9, 16, 23, 30, 37, 44, 51, 58, 65, 72, 79, 86, 93 and 100. : ;{{BlockLink|Respawn Anchor}} : A respawn anchor outputs a signal strength of 0, 3, 7, 11, or 15, depending on the "charged" value. ;{{BlockLink|Sculk Sensor}} : A sculk sensor outputs a signal strength depending on the type of vibration that is detected. ;{{BlockLink|Chiseled Bookshelf}} : A chisled bookshelf outputs a signal strength between 1 and 6 indicating the last slot interacted with. When no slot has been interacted with yet, it outputs 0. {{-}} == Sounds == === Generic === {{Edition|Java}}: {{Sound table/Block/Stone/JE}} {{Edition|Bedrock}}: {{Sound table/Block/Wood/BE}} === Unique === {{edition|java}}: {{Sound table |rowspan=2 |sound=Click.ogg |subtitle=Comparator clicks |source=block |description=When a comparator is set to subtraction mode |id=block.comparator.click |translationkey=subtitles.block.comparator.click |volume=0.3 |pitch=0.55 |distance=16}} {{Sound table |subtitle=Comparator clicks |source=block |description=When a comparator is set to comparison mode |id=block.comparator.click |translationkey=subtitles.block.comparator.click |volume=0.3 |pitch=0.5 |distance=16 |foot=1}} {{edition|bedrock}}: {{Sound table |type=bedrock |rowspan=2 |sound=Click.ogg |source=block |description=When a comparator is set to subtraction mode |id=block.click |volume=0.2 |pitch=0.55}} {{Sound table |source=block |description=When a comparator is set to comparison mode |id=block.click |volume=0.2 |pitch=0.5 |foot=1}} == Data values == === ID === {{edition|java}}: {{ID table |edition=java |showforms=y |generatetranslationkeys=y |displayname=Redstone Comparator |spritetype=block |nameid=comparator |foot=1}} {{ID table |displayname=Block entity |spritename=redstone-comparator |spritetype=block |nameid=comparator |foot=1}} {{edition|bedrock}}: {{ID table |edition=bedrock |firstcolumnname=Redstone Comparator |shownumericids=y |showforms=y |generatetranslationkeys=y |displayname=Unpowered block |spritename=unpowered-comparator |spritetype=block |nameid=unpowered_comparator |id=149 |form=block |translationkey=-}} {{ID table |displayname=Powered block |spritename=powered-comparator |spritetype=block |nameid=powered_comparator |id=150 |form=block |translationkey=-}} {{ID table |displayname=Item |spritename=redstone-comparator |spritetype=item |nameid=comparator |id=522 |form=item |foot=1}} {{ID table |notnamespaced=y |displayname=Block entity |spritename=redstone-comparator |spritetype=block |nameid=Comparator |foot=1}} === Block states === {{see also|Block states}} {{/BS}} === Block data === A redstone comparator has a block entity associated with it that holds additional data about the block. {{el|je}}: {{see also|Block entity format}} {{/BE}} {{el|be}}: : See [[Bedrock Edition level format/Block entity format]]. == Advancements == {{Load advancements|the power of books}} == Video == <div style="text-align:center">{{yt|J7Z20Zzz3yU}}</div> == History == {{info needed section|If {{bug|MC-50242}} also affected comparators?}} ''For a more in-depth breakdown of changes to repeater textures and models, including a set of renders for each state combination, see [[/Asset history]]'' {{History|java}} {{History||November 24, 2012|link=https://youtube.com/watch?v=YG9RNyRhIow&t=6m56s|[[Jeb]] stated that there may be a "capacitor" in [[Minecraft]]. }} {{History||December 27, 2012|link={{tweet|Dinnerbone|284388625595125760}}|[[Dinnerbone]] released [https://web.archive.org/web/20190710120115/https://imgur.com/a/FBKed pictures] of the first version of the "comparator", stating it was a replacement for the "capacitor" idea that has variable, alternate inputs.}} {{History||January 2, 2013|link={{tweet|Dinnerbone|286428595423965184}}|Dinnerbone released one more [http://dinnerbone.com/media/uploads/2013-01/screenshots/2013-01-02_12.06.47.png picture] of the comparator. The picture itself showing a digital-to-analog converter, using the comparator as the main [[block]].}} {{History||1.5|snap=13w01a|[[File:Redstone Comparator (S) JE1.png|32px]] [[File:Powered Redstone Comparator (S) JE1.png|32px]] [[File:Subtracting Redstone Comparator (S) JE1.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE1.png|32px]] [[File:Redstone Comparator (item) JE1 BE1.png|32px]] Added redstone comparators. |Redstone comparators have 0 delay. At this point, block ID 149 was used for unpowered comparators, and block ID 150 for powered comparators.}} {{History|||snap=13w01b|A delay of 1 game tick ({{frac|1|2}} redstone tick) has now been added to redstone comparators to fix bugs. |The ability to measure containers to redstone comparators has now been added.}} {{History|||snap=13w02a|[[File:Redstone Comparator (S) JE2.png|32px]] [[File:Powered Redstone Comparator (S) JE2.png|32px]] [[File:Subtracting Redstone Comparator (S) JE2.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE2.png|32px]] The appearance of redstone comparators has now been changed - the top texture has changed to show [[quartz]] in the middle and the sides now use the [[smooth stone]] texture rather than the smooth stone slab side texture. |The algorithm for measuring containers has now been changed so that redstone comparators output a signal with as few as 1 [[item]] in the container.}} {{History|||snap=13w02b|Redstone comparators now treat large [[chest]]s as a single container.}} {{History|||snap=13w03a|Redstone comparators now output success count of [[command block]]s. |Redstone comparators now measure container [[minecart]]s on [[detector rail]]s.}} {{History|||snap=13w04a|Redstone comparators now measure [[jukebox]]es.}} {{History|||snap=13w05a|Redstone comparators no longer cause constant [[block]] updates. The delay has now been made consistent, and side input no longer causes a pulse output. |Block 150 (later <code>powered_comparator</code>) is no longer used; powered state is now represented by the 8s bit on block 149 (later <code>unpowered_comparator</code>).}} {{History|||snap=13w05b|Redstone comparator delay has now been changed from 1 game tick (1/2 [[redstone]] tick) to 2 game ticks (1 redstone tick).}} {{History|||snap=13w09c|The redstone signal strength from a redstone comparator next to a [[brewing stand]] with 3 [[water bottle]]s in it is now the same as one with 3 water bottles and 1 ingredient in it.}} {{History||1.6.1|snap=13w18a|Redstone comparators now measure [[cauldron]]s and [[end portal frame]]s.}} {{History||1.8|snap=14w04a|Redstone comparators now measure [[item frame]]s.}} {{History|||snap=14w10a|The torches under redstone comparators have now been shortened, which has changed the underside appearance from [[File:Redstone Comparator UNKVER1 (facing NWU).png|32px]] [[File:Powered Redstone Comparator UNKVER1 (facing NWU).png|32px]] [[File:Subtracting Redstone Comparator UNKVER1 (facing NWU).png|32px]] [[File:Powered Subtracting Redstone Comparator UNKVER1 (facing NWU).png|32px]] to [[File:Redstone Comparator UNKVER2 (facing NWU).png|32px]].}} {{History|||snap=14w25a|[[File:Redstone Comparator (S) JE3.png|32px]] [[File:Powered Redstone Comparator (S) JE3.png|32px]] [[File:Subtracting Redstone Comparator (S) JE3.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE3.png|32px]] The torches on comparators are now subject to ambient occlusion. |Comparators set to subtract mode appear to be powered as well regardless of incoming power. The subtracting-only model still exists and can be achieved through {{cmd|setblock}}.}} {{History|||snap=14w25b|[[File:Subtracting Redstone Comparator (S) JE4.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE4.png|32px]] The powered front torch when in subtraction mode is now lower. |Comparators set to subtract by hand now appear normally again.}} {{History|||snap=14w28a|Redstone comparators now measure [[cake]]s.}} {{History||1.9|snap=15w42a|With the addition of the [[blaze powder]] fuel slot, [[brewing stand]]s now have 5 slots instead of 4. Their original comparative power values from redstone comparators are listed below: {{{!}} class{{=}}"wikitable collapsible collapsed" data-description{{=}}"Original values" ! Original values {{!}}- {{!}} *0: 0 *1: 1 *2: 19 *3: 37 *4: 55 *5: 1s 10 *6: 1s 28 *7: 1s 46 *8: 2s *9: 2s 19 *10: 2s 37 *11: 2s 55 *12: 3s 10 *13: 3s 28 *14: 3s 46 *15: 4s {{!}}} }} {{History|||snap=15w47a|Redstone comparators' side inputs now take power from [[redstone block]]s.}} {{History||1.13|snap=17w47a|All 3 IDs for the redstone comparator have now been merged into one ID: <code>comparator</code>. |Redstone comparators now render their underside, which has changed their undersides from [[File:Redstone Comparator UNKVER2 (facing NWU).png|32px]] to [[File:Redstone Comparator UNKVER3 (facing NWU).png|32px]]. |Prior to [[1.13/Flattening|''The Flattening'']], these blocks' numeral IDs were 149 and 150, and the [[item]]'s 404. |As a result, the formerly unused comparator ID is now technically used again, due to both unpowered and powered versions being merged into a single comparator block ID.}} {{History||1.14|snap=18w43a|[[File:Redstone Comparator (S) JE4.png|32px]] [[File:Powered Redstone Comparator (S) JE4.png|32px]] [[File:Subtracting Redstone Comparator (S) JE5.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE5.png|32px]] [[File:Redstone Comparator (item) JE2 BE2.png|32px]] The textures of redstone comparators have now been changed.}} {{History|||snap=19w02a|Redstone comparators now measure [[lectern]]s.}} {{History|||snap=19w03a|Redstone comparators now measure [[composter]]s.}} {{History|||snap=19w12b|Redstone comparators can now be placed on [[glass]], [[ice]], [[glowstone]] and [[sea lantern]]s.}} {{History||1.15|snap=19w34a|Redstone comparators now measure how much honey is inside [[beehive|bee hive]]s and [[bee nest]]s.}} {{History||1.16|snap=20w06a|The way to calculate the input signals of redstone comparators has now been changed.}} {{History|||snap=20w11a|The changes to the way of calculating the input signals of redstone comparators from [[Java Edition 20w06a|20w06a]] have now been reverted.}} {{History|||snap=20w16a|Redstone comparators now measure [[Pigstep music disc]]s in [[jukebox]]es.}} {{History||1.17|snap=20w45a|Redstone comparators now measure [[lava cauldron]]s.}} {{History|||snap=20w46a|Redstone comparators now measure [[Cauldron#Holding powder snow|powder snow cauldron‌]]s.}} {{History||1.18|snap=21w41a|[[File:Powered Redstone Comparator (S) JE5.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE6.png|32px]] The texture of powered redstone comparator have now been changed.}} {{History||1.19|snap=22w13a|Redstone comparators now generate as part of [[ancient cities]].}} {{History||1.20<br>(Experimental)|link=1.19.3|snap=22w42a|Redstone comparators now measure [[chiseled bookshelves]].}} {{History||1.20.2|snap=23w33a|Redstone comparators now use stone sounds instead of wood sounds.<ref>{{bug|MC-182820|||Fixed}}</ref>}} {{History|pocket alpha}} {{History||v0.14.0|snap=build 1|[[File:Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Powered Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Subtracting Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE2 BE1.png|32px]]{{verify|Was this the model used?}} [[File:Redstone Comparator (item) JE1 BE1.png|32px]] Added redstone comparators.}} {{History|pocket}} {{History||1.0.0|snap=alpha 0.17.0.1|Redstone comparators now measure [[end portal frame]]s.}} {{History||1.0.5|snap=alpha 1.0.5.0|Redstone comparators now output success count of [[command block]]s.}} {{History||1.1.0|snap=alpha 1.1.0.0|Redstone comparators now measure [[shulker box]]es.}} {{History|bedrock}} {{History||1.2.0|snap=beta 1.2.0.2|Redstone comparators now measure [[jukebox]]es. |Redstone comparators now render their underside, which has changed their undersides from [[File:Redstone Comparator UNKVER1 (facing NWU).png|32px]] to [[File:Redstone Comparator UNKVER3 (facing NWU).png|32px]]}} {{History||1.10.0|snap=beta 1.10.0.3|[[File:Redstone Comparator (S) BE.png|32px]] [[File:Powered Redstone Comparator (S) BE.png|32px]] [[File:Subtracting Redstone Comparator (S) BE.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) BE.png|32px]] [[File:Redstone Comparator (item) JE2 BE2.png|32px]] The textures of redstone comparators have now been changed.}} {{History||1.11.0|snap=beta 1.11.0.1|Redstone comparators now measure [[smoker]]s, [[blast furnace]]s, [[lectern]]s and [[composter]]s.}} {{History||1.18.10|snap=beta 1.18.10.20|[[File:Powered Redstone Comparator (S) JE5.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE6.png|32px]] The texture of powered redstone comparator have now been changed.}} {{History||1.20.30|snap=beta 1.20.30.20|Redstone comparators now use the <code>minecraft:cardinal_direction</code> [[block state]] instead of <code>direction</code>.}} {{History|console}} {{History||xbox=TU19|xbone=CU7|ps=1.12|wiiu=Patch 1|switch=1.0.1|[[File:Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Powered Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Subtracting Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE2 BE1.png|32px]]{{verify|Was this the model used?}} [[File:Redstone Comparator (item) JE1 BE1.png|32px]] Added redstone comparators.}} {{History||xbox=TU31|xbone=CU19|ps=1.22|wiiu=Patch 3|switch=1.0.1|Redstone comparators can now measure [[item frame]]s.}} {{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Redstone Comparator (S) BE.png|32px]] [[File:Powered Redstone Comparator (S) BE.png|32px]] [[File:Subtracting Redstone Comparator (S) BE.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) BE.png|32px]]{{verify|Was this the model used?}} [[File:Redstone Comparator (item) JE2 BE2.png|32px]] The textures of redstone comparators have now been changed.}} {{History|3ds}} {{History||0.1.0|[[File:Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Powered Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Subtracting Redstone Comparator (S) JE2 BE1.png|32px]] [[File:Powered Subtracting Redstone Comparator (S) JE2 BE1.png|32px]]{{verify|Was this the model used?}} [[File:Redstone Comparator (item) JE2 BE2.png|32px]] Added redstone comparators.}} {{History|foot}} === Redstone comparator "items" === {{:Technical blocks/Redstone Comparator}} == Issues == {{issue list}} == Trivia == * Comparators do not emit redstone particles when powered, unlike redstone torches and repeaters.<ref>{{bug|MC-51692|||WAI}}</ref> == Gallery == <gallery> Dinnerbone Comparator 1.png|Dinnerbone showing how comparators work. Dinnerbone Comparator 2.png|Dinnerbone showing how comparators work. Dinnerbone Comparator 3.png|Dinnerbone showing how comparators work. Dinnerbone Comparators 1.png|A contraption incorporating comparators. Dinnerbone Comparators 2.png|Comparators in action. Dinnerbone Comparators 3.png|Output specific signals. Dinnerbone Comparator Thing.png|Another comparator in use. Item Frame Comparator.png|Rotating the torch in the item frame adjusts the comparator's output. </gallery> == References == {{reflist}} {{Redstone}} {{Blocks|Utility}} {{Items}} [[Category:Mechanics]] [[Category:Block entities]] [[Category:Redstone mechanics]] [[Category:Mechanisms]] [[Category:Manufactured blocks]] [[Category:Non-solid blocks]] [[de:Redstone-Komparator]] [[es:Comparador de redstone]] [[fr:Comparateur de redstone]] [[hu:Redstone-komparátor]] [[ja:レッドストーンコンパレーター]] [[ko:레드스톤 비교기]] [[nl:Redstonevergelijker]] [[pl:Komparator]] [[pt:Comparador de redstone]] [[ru:Компаратор]] [[uk:Редстоуновий компаратор]] [[zh:红石比较器]]</li><li>[[Slimeball|Slimeball]]<br/>{{about|the item|the mob|Slime|the block constructed with slimeballs|Slime Block|other uses|Slime (disambiguation)}} {{Item | image = Slimeball.png | renewable = Yes | stackable = Yes (64) }} A '''slimeball''' is a [[crafting]] ingredient commonly dropped by [[slime]]s, and can be sneezed out by [[panda]]s. == Obtaining == === Mob loot === ==== Slimes ==== {{see also|Tutorials/Slime farming}} If a [[slime]]'s size is 1, it drops 0–2 slimeballs when killed. The maximum number of slimeballs is increased by 1 per level of [[Looting]], for a maximum of 5 slimeballs with Looting III. ==== Pandas ==== Baby [[panda]]s have a {{frac|1|700}} chance of [[drop]]ping one slimeball when sneezing. === Crafting === {{Crafting |Slime Block |Output= Slimeball,9 |type= Miscellaneous }} === Trading === [[Wandering trader]]s sometimes offer to sell a slimeball for 4 [[emerald]]s. == Usage == === Crafting ingredient === {{crafting usage}} === Breeding === Slimeballs can be used to breed [[frog]]s and reduce the remaining growth duration of [[tadpole]]s by 10%. Both also follow a player holding a slimeball. ==Video== {{Video note|This video is outdated, as slimeballs can now also be used to craft [[lead]]s and [[slime block]]s, breed [[frog]]s, and can now be obtained from baby [[panda]]s and [[wandering trader]]s.}} {{yt|J6oR3fdbbjY}} == Data values == ===ID=== {{edition|java}}: {{ID table |edition=java |showforms=y |generatetranslationkeys=y |displayname=Slimeball |spritetype=item |nameid=slime_ball |form=item |foot=1}} {{edition|bedrock}}: {{ID table |edition=bedrock |shownumericids=y |showforms=y |notshowbeitemforms=y |generatetranslationkeys=y |displayname=Slimeball |spritetype=item |nameid=slime_ball |id=388 |form=item |foot=1}} ==History== {{History|java alpha}} {{History||v1.0.11|[[File:Slimeball JE1 BE1.png|32px]] Added slimeballs, which are dropped from [[slime]]s. At the moment, they serve no purpose.}} {{History|java beta}} {{History||1.7|Slimeballs are now used to craft [[sticky piston]]s.}} {{History|java}} {{History||1.0.0|snap=Beta 1.9 Prerelease 2|Slimeballs are used to craft [[magma cream]].}} {{History||1.6.1|snap=13w18a|[[Lead]]s, which were originally implemented in the [[13w16a]] snapshot, now have a [[crafting]] recipe that includes slimeballs.}} {{History||1.8|snap=14w02a|Nine slimeballs are now used to [[crafting|craft]] a [[slime block]]. Slime blocks also act as storage [[block]]s, being able to craft back into 9 slimeballs.}} {{History||1.13|snap=17w47a|Prior to [[1.13/Flattening|''The Flattening'']], this [[item]]'s numeral ID was 341.}} {{History||1.14|snap=18w43a|[[File:Slimeball JE2 BE2.png|32px]] The texture of slimeballs has been changed. |Slimeballs can now be obtained when a [[panda|baby panda]] sneezes.}} {{History|||snap=19w05a|Slimeballs can now be bought from [[wandering trader]]s.}} {{History||1.19|snap=22w11a|Slimeballs can now be used to breed [[frog]]s.}} {{History|pocket alpha}} {{History||v0.9.0|snap=build 1|[[File:Slimeball JE1 BE1.png|32px]] Added slimeballs. They are currently unobtainable and serve no purpose.}} {{History||v0.12.1|snap=build 1|Added slimeballs to the [[creative]] [[inventory]]. |Slimeballs can now be obtained by killing [[slime]]s. |Slimeballs are now used to craft [[magma cream]].}} {{History||v0.14.0|snap=build 1|Slimeballs are now used to craft [[slime block]]s.}} {{History||v0.15.0|snap=build 1|Slimeballs are now used to craft [[sticky piston]]s and [[lead]]s.}} {{History|bedrock}} {{History||1.8.0|snap=beta 1.8.0.8|Slimeballs can now be obtained when a [[panda|baby panda]] sneezes.}} {{History||1.10.0|snap=beta 1.10.0.3|[[File:Slimeball JE2 BE2.png|32px]] The texture of slimeballs has been changed. |Slimeballs can now be obtained via [[trading]] with [[wandering trader]]s.}} {{History|console}} {{History||xbox=TU1|xbone=CU1|ps=1.0|wiiu=Patch 1|switch=1.0.1|[[File:Slimeball JE1 BE1.png|32px]] Added slimeballs.}} {{History||xbox=TU3|Slimeballs are now used to craft [[sticky piston]]s.}} {{History||xbox=TU5|Slimeballs are found in the Miscellaneous tab in the [[Creative inventory]].}} {{History||xbox=TU9|Moved slimeballs to the Materials tab in the Creative inventory.}} {{History||xbox=none|xbone=none|ps=1.83|wiiu=none|switch=none|Slimeballs can now be obtained when a [[panda|baby panda]] sneezes.}} {{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Slimeball JE2 BE2.png|32px]] The texture of slimeballs has been changed.}} {{History|New 3DS}} {{History||0.1.0|[[File:Slimeball JE1 BE1.png|32px]] Added slimeballs.}} {{History|foot}} ==Issues == {{issue list}} == External Links == *[https://www.minecraft.net/en-us/article/taking-inventory--slimeball Taking Inventory: Slimeball] – Minecraft.net on June 24, 2021 {{Items}} [[Category:Renewable resources]] [[cs:Sliz]] [[de:Schleimball]] [[es:Bola de slime]] [[fr:Boule de Slime]] [[hu:Nyálkagolyó]] [[it:Palla di slime]] [[ja:スライムボール]] [[ko:슬라임볼]] [[nl:Slijmbal]] [[pl:Kula szlamu]] [[pt:Bola de slime]] [[ru:Слизь]] [[th:ลูกเมือก]] [[uk:Слизова кулька]] [[zh:黏液球]]</li></ul></nowiki> 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. release Goats have been made inaccessible in the full release. Upcoming Bedrock Edition 1.16.210 {{Extension DPL}}<ul><li>[[Brewing Stand|Brewing Stand]]<br/>{{Block | image = <gallery> Brewing Stand (empty) JE10.png | Empty Brewing Stand (right) JE10.png | Right Brewing Stand (left) JE10.png | Left Brewing Stand (full) JE10.png | Full </gallery> | transparent = Yes | light = Yes (1) | tool = Wooden Pickaxe | renewable = Yes | stackable = Yes (64) | flammable = No | lavasusceptible = No }} A '''brewing stand''' is a [[block]] used for [[brewing]] [[potion]]s using [[Glass Bottle|bottles]] and suitable ingredients. It also serves as a [[cleric]]'s [[job site block]]. == Obtaining == === Breaking === A brewing stand can be obtained using any [[pickaxe]]. If mined without a pickaxe, it drops nothing {{in|JE}}, while it drops itself {{in|BE}}. {{breaking row|horizontal=1|Brewing Stand|Pickaxe|Wood|foot=1}} === Natural generation === Brewing stands generate in [[end ship]]s. They have two [[potion of Healing|Instant Health II potions]] in their holders. A brewing stand also generates in the basement of [[igloo]]s with a [[splash potion of Weakness]] in it. Brewing stands can generate without potions in [[village]] churches. === Crafting === {{Crafting |head=1 |showdescription=1 |B1= Blaze Rod |A2= Any stone-tier block |B2= Any stone-tier block |C2= Any stone-tier block |Output= Brewing Stand |type= Brewing |description=Can use cobblestone and its other variants interchangeably. |foot=1 }} == Usage == [[File:Brewing Stand GUI.png|thumb|right|176px|Brewing stand GUI {{in|java}}]] By default, the interface of a brewing stand is labeled "Brewing Stand", but this name can be customized by naming it in an [[anvil]] before placing it. Brewing stands cannot be pushed by [[piston]]s {{in|java}}. === Brewing === {{main|Brewing}} The main purpose of brewing stands is to allow for the [[brewing]] of [[potion]]s. Its interface can be opened by pressing {{control|use}} on them. Brewing stands need [[blaze powder]] as fuel. Each piece brews 20 batches of potions, with each stage of brewing counting separately. Unlike [[furnace]]s, there is no time limit; fuel is consumed only when there are [[Glass Bottle|bottles]] and an ingredient to brew into it. Brewing stands interact with [[hopper]]s as follows: * They accept brewing ingredients from hoppers pointing down into the top. * Any valid potion recipe can be preloaded for "hands-free" brewing of a complex recipe, with the [[Nether Wart|nether wart]] falling through into the stand for the first step. * Bottles and fuel are accepted from hoppers pointing into the side. * Finished products can be pulled out by hoppers below, but each stage of brewing counts as a batch of "finished" potions. {{IN|education}}, elements can be combined in the brewing stand to make the [[medicine]] potions: antidote, elixir, eye drops, and tonic. === Changing profession === If a village has a brewing stand that has not been claimed by a villager, any villager who hasn't already picked a [[job site]] block in the village has a chance to change their profession into cleric. === Light source === Brewing stands emit a light level of 1. == Sounds == === Generic === {{Sound table/Block/Stone}} === Unique === {{edition|java}}: {{Sound table |rowspan=2 |sound=Brewing Stand brew1.ogg |sound2=Brewing Stand brew2.ogg |subtitle=Brewing Stand bubbles |source=block |description=When a potion finishes brewing |id=block.brewing_stand.brew |translationkey=subtitles.block.brewing_stand.brew |volume=1.0 |pitch=1.0 |distance=16}} {{Sound table |subtitle=Cleric works |source=neutral |description=Randomly while a cleric is working |id=entity.villager.work_cleric |translationkey=subtitles.entity.villager.work_cleric |volume=1.0 |pitch=0.8-1.2 |distance=16}} {{Sound table |sound=Door close.ogg |sound2=Door open.ogg |subtitle=Chest locked<ref group=sound name=lock>{{Bug|MC-98316||Wrong subtitles caused by missing distinction}}</ref> |source=block |description=When a player attempts to open a brewing stand locked using the {{nbt|string|Lock}} tag |id=block.chest.locked|idnote=<ref group=sound name=lock/> |translationkey=subtitles.block.chest.locked|translationkeynote=<ref group=sound name=lock/> |volume=1.0 |pitch=1.0 |distance=16 |foot=1}} {{Edition|Bedrock}}: {{Sound table |type=bedrock |rowspan=2 |sound=Brewing Stand brew1.ogg |sound2=Brewing Stand brew2.ogg |source=block |description=When a potion finishes brewing |id=random.potion.brewed |volume=1.0 |pitch=1.0}} {{Sound table |source=block |description=Randomly while a cleric is working |id=random.potion.brewed |volume=1.0 |pitch=1.0 |foot=1}} == Data values == === ID === {{edition|java}}: {{ID table |edition=java |showforms=y |generatetranslationkeys=y |displayname=Brewing Stand |spritetype=block |nameid=brewing_stand |translationkey=block.minecraft.brewing_stand, item.minecraft.brewing_stand |foot=1}} {{ID table |displayname=Block entity |spritename=brewing-stand |spritetype=block |nameid=brewing_stand |foot=1}} {{edition|bedrock}}: {{ID table |edition=bedrock |firstcolumnname=Brewing Stand |shownumericids=y |showforms=y |generatetranslationkeys=y |displayname=Block |spritename=brewing-stand |spritetype=block |nameid=brewing_stand |id=117 |form=block |itemform=item.brewing_stand |translationkey=-}} {{ID table |displayname=Item |spritename=brewing-stand |spritetype=item |nameid=brewing_stand |id=431 |form=item |foot=1}} {{ID table |notnamespaced=y |displayname=Block entity |spritename=brewing-stand |spritetype=block |nameid=BrewingStand |foot=1}} === Block states === {{see also|Block states}} {{/BS}} === Block data === A brewing stand 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]]. == Achievements == {{load achievements|Local Brewery}} == Advancements == {{Load advancements|Local Brewery}} == History == {{History|java}} {{History||1.0.0|snap=Beta 1.9 Prerelease 2|[[Cauldron]]s are implemented to be used to brew [[potion]]s, but are not available in-game yet.}} {{History|||snap=September 30, 2011|slink={{tweet|jeb|119762786619359232}}|[[File:Brewing Stand (pre-release).png|32px]] [[Jens Bergensten|Jeb]] reveals that brewing is done through a brewing stand instead of a [[cauldron]].}} {{History|||snap=Beta 1.9 Prerelease 3|[[File:Brewing Stand (empty) JE1 BE1.png|32px]] [[File:Brewing Stand (right) JE1.png|32px]] [[File:Brewing Stand (left) JE1.png|32px]] [[File:Brewing Stand (full) JE1.png|32px]] [[File:Brewing Stand (item) JE1 BE1.png|32px]] Added brewing stands. |Brewing [[potion]]s with brewing stands currently take 30 seconds. |When the first brewing stand was shown by Jeb, it had an additional 2D sub-stand for [[Glass Bottle|bottles]], but the stands for bottles are now designed in 3D.<ref>{{tweet|jeb|119763532312096769|I'm fully aware the potions are very thin (diet?), but it looks cute. (Always work in progress, of course)|September 30, 2011}}</ref>}} {{History||1.1|snap=12w01a|Brewing time for brewing stands has been reduced to 20 seconds.}} {{History||1.3.1|snap=12w15a|{{key|Shift}} + clicking can now be used to put items in brewing stands.}} {{History||1.8|snap=14w11a|[[File:Brewing Stand (empty) JE2.png|32px]] [[File:Brewing Stand (right) JE2.png|32px]] [[File:Brewing Stand (left) JE2.png|32px]] [[File:Brewing Stand (full) JE2.png|32px]] The [[model]] of brewing stands has been changed. Stands with no bottles appear glitched from some angles, the left and right slots appear identical when filled in (although both distinct appearences still exist as metadata), and the arm angles have changed due to the 22.5º rotation limit. |Brewing stands' targeting [[hitbox]] is now a full cube - previously it was a cuboid around the base plates.}} {{History|||snap=14w11b|[[File:Brewing Stand (empty) JE3.png|32px]] [[File:Brewing Stand (right) JE3.png|32px]] [[File:Brewing Stand (left) JE3.png|32px]] [[File:Brewing Stand (full) JE3.png|32px]] Empty brewing stands' model have been fixed, although the other changes still remain.}} {{History|||snap=14w25a|[[File:Brewing Stand (empty) JE4.png|32px]] [[File:Brewing Stand (right) JE4.png|32px]] [[File:Brewing Stand (left) JE4.png|32px]] [[File:Brewing Stand (full) JE4.png|32px]] Brewing stand models have changed such that bottles in the left and right slots now indeed appear different. However, the leftmost one appears stretched. Arms are also now affected by directional shading.<ref>{{bug|MC-68302|||WAI}}</ref>}} {{History||1.9|snap=15w31a|Brewing stands now generate in [[End City|end cities]].}} {{History|||snap=15w33a|Brewing stands can now brew [[Lingering Potion|lingering potion]]s.}} {{History|||snap=15w33c|A bug where the [[player]] couldn't put in a [[splash potion]] to make a lingering potion has been fixed.}} {{History|||snap=15w42a|Brewing stands now require [[Blaze Powder|blaze powder]] to operate.}} {{History|||snap=15w43a|Brewing stands now generate in the basement of [[igloo]]s. |Each blaze powder now fuels 20 brewing stand operations rather than 30.}} {{History|||snap=15w44a|[[File:Brewing Stand (empty) JE5.png|32px]] [[File:Brewing Stand (right) JE5.png|32px]] [[File:Brewing Stand (left) JE5.png|32px]] [[File:Brewing Stand (full) JE5.png|32px]] Brewing stand models no longer have a stretched bottle.}} {{History|||snap=15w47b|[[Sound]]s have been added for brewing stands.}} {{History||1.11|snap=16w32a|The block entity ID has been changed from <code>Cauldron</code> to <code>brewing_stand</code>.}} {{History||1.13|snap=17w47a|Prior to [[Java Edition 1.13/Flattening|''The Flattening'']], this [[block]]'s numeral ID was 117, and the [[item]]'s 379.}} {{History||1.14|snap=18w43a|[[File:Brewing Stand (empty) JE6 BE2.png|32px]] <!-- [[File:Brewing Stand (left) JE6 BE2.png|32px]] [[File:Brewing Stand (right) JE6 BE2.png|32px]] -->[[File:Brewing Stand (Full) JE6 BE2.png|32px]] [[File:Brewing Stand (item) JE2.png|32px]] The textures of brewing stands have been changed.}} {{History|||snap=18w44a|[[File:Brewing Stand (item) JE3 BE2.png|32px]] The texture of the brewing stand [[item]] has been changed.}} {{History|||snap=18w48a|Brewing stands now generate in the updated [[plains]] [[village]]s.}} {{History|||snap=18w49a|Brewing stands now generate in the updated [[savanna]] villages and the new [[Snowy Tundra|snowy]] villages.}} {{History|||snap=18w50a|Brewing stands now generate in the updated [[desert]] and [[taiga]] villages.}} {{History|||snap=19w03c|The three plates, but not the rod, of a brewing stand now use correct cullface arguments.}} {{History|||snap=19w11a|Brewing stands now serve as cleric [[villager]]s' job site block.}} {{History||1.16.2|snap=20w28a|Brewing stands can now be [[crafting|crafted]] with [[blackstone]].}} {{History||1.17|snap=21w07a|Brewing stands can now be crafted with [[deepslate|grimstone]] (now deepslate).}} {{History||1.17|snap=21w08a|Brewing stands can no longer be crafted with deepslate. |Brewing stands can now be crafted with [[Cobbled Deepslate|cobbled deepslate]].}} {{History|||snap=21w11a|<!--[[File:Brewing Stand (empty) JE7.png|32px]] [[File:Brewing Stand (right) JE7.png|32px]] [[File:Brewing Stand (left) JE7.png|32px]] [[File:Brewing Stand (Full) JE7.png|32px]] Changed [[lighting]].-->Tweaked the brewing stand GUI texture.}} {{History||1.18|snap=21w39a|[[File:Brewing Stand (empty) JE8.png|32px]] [[File:Brewing Stand (right) JE8.png|32px]] [[File:Brewing Stand (left) JE8.png|32px]] [[File:Brewing Stand (full) JE8.png|32px]] The default [[brightness]] has been changed from "Moody" to 50.}} {{History||1.19|snap=22w11a|[[File:Brewing Stand (empty) JE9.png|32px]] [[File:Brewing Stand (right) JE9.png|32px]] [[File:Brewing Stand (left) JE9.png|32px]] [[File:Brewing Stand (full) JE9.png|32px]] Changed texture and model.}} {{History|||snap=22w17a|[[File:Brewing Stand (empty) JE10.png|32px]] [[File:Brewing Stand (right) JE10.png|32px]] [[File:Brewing Stand (left) JE10.png|32px]] [[File:Brewing Stand (full) JE10.png|32px]] Changed base texture and model.}} {{History|pocket alpha}} {{History||v0.12.1|snap=build 1|[[File:Brewing Stand (empty) JE1 BE1.png|32px]] [[File:Brewing Stand (item) JE1 BE1.png|32px]] Added brewing stands.}} {{History|pocket}} {{History||1.0.0|snap=alpha 0.17.0.1|Brewing stands now generate in [[igloo]] basements. |Brewing stands now generate in [[end ship]]s.}} {{History|bedrock}} {{History||1.2.0|snap=beta 1.2.0.2|Brewing stands now require [[blaze powder]] to operate.}} {{History||1.10.0|snap=beta 1.10.0.3|[[File:Brewing Stand (empty) JE6 BE2.png|32px]] [[File:Brewing Stand (item) JE3 BE2.png|32px]] The textures of brewing stands have been changed.|A brewing stand can now generate in [[village]] temples.}} {{History||1.16.100|snap=beta 1.16.100.52|Brewing stands can now be [[craft]]ed with [[blackstone]].}} {{History||1.17.0|snap=beta 1.17.0.50|Brewing stands can now be [[craft]]ed with [[cobbled deepslate]].}} {{History||1.19.0|snap=beta 1.19.0.20|[[File:Brewing Stand (empty) JE10.png|32px]] [[File:Brewing Stand (right) JE10.png|32px]] [[File:Brewing Stand (left) JE10.png|32px]] [[File:Brewing Stand (full) JE10.png|32px]] Slightly changed its texture, to make their arms connect to their bases.}} {{History|console}} {{History||xbox=TU7|xbone=CU1|ps=1.0|wiiu=Patch 1|switch=1.0.1|[[File:Brewing Stand (empty) JE1 BE1.png|32px]] [[File:Brewing Stand (item) JE1 BE1.png|32px]] Added brewing stands.}} {{History||xbox=TU43|xbone=CU33|ps=1.36|wiiu=Patch 13|Brewing stands now appear in [[igloo]]s. The lack of a fuel requirement means that potions can now be made without going to the Nether.}} {{History||xbox=TU46|xbone=CU36|ps=1.38|wiiu=Patch 15|Brewing stands now require [[blaze powder]] to operate.}} {{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Brewing Stand.png|32px]] [[File:Brewing Stand (item) JE3 BE2.png|32px]] The textures of brewing stands have been changed.}} {{History|new 3ds}} {{History||0.1.0|[[File:Brewing Stand (empty) JE1 BE1.png|32px]] [[File:Brewing Stand (item) JE1 BE1.png|32px]] Added brewing stands.}} {{History|foot}} <gallery> File:Brewingstand Potion.png|The first picture of a brewing stand. A [[giant mushroom]] is also seen in this picture. </gallery> === Brewing stand "item" === {{:Technical blocks/Brewing Stand}} == Issues == {{issue list}} == Trivia == * Even when the brewing stand is not in use, there is still smoke coming out of the top of it. * In ''[[Java Edition]]'', when a brewing stand is broken, particles from a bottle appear, even if no bottle is in the stand. * No matter what potion (including water bottles) is in the stand it always looks like a full red bottle. * Brewing stands always face east, no matter what direction they are placed. * According to [[Michael Stoyke|Searge]], for thematic reasons, a brewing stand was added to the basement of the [[igloo]]. Because of this, blaze powder was required for fuel to preserve game progression. In this way, the player is prevented from using it before going to the Nether.<ref>https://minecraft.net/en-us/article/meet-blaze</ref> == Gallery == <gallery> File:Brewing stand in action.png|A brewing stand in action. File:Igloobasement.png|A brewing stand in an igloo basement. File:1.8 and below brewing stand.png|The GUI of the brewing stand in 1.8.x and below. </gallery> == See also == *[[Glass Bottle]] *[[Splash Potion]] == References == {{reflist}} == External links == *[https://www.minecraft.net/en-us/article/taking-inventory--brewing-stand Taking Inventory: Brewing Stand] – Minecraft.net on October 11, 2019 {{Blocks|Utility}} {{items}} [[Category:Job blocks]] [[Category:Utility blocks]] [[Category:Manufactured blocks]] [[Category:Generated structure blocks]] [[Category:Storage]] [[Category:Block entities]] [[Category:Light sources]] [[de:Braustand]] [[es:Soporte para pociones]] [[fr:Alambic]] [[hu:Főzőállvány]] [[it:Alambicco]] [[ja:醸造台]] [[nl:Brouwstandaard]] [[pl:Statyw alchemiczny]] [[pt:Suporte de poções]] [[ru:Варочная стойка]] [[uk:Варильна стійка]] [[zh:酿造台]]</li><li>[[Melon Seeds|Melon Seeds]]<br/>{{Block |image = <gallery> Melon Stem Age 0.png | Age 0 Melon Stem Age 1.png | Age 1 Melon Stem Age 2.png | Age 2 Melon Stem Age 3.png | Age 3 Melon Stem Age 4.png | Age 4 Melon Stem Age 5.png | Age 5 Melon Stem Age 6.png | Age 6 Melon Stem Age 7.png | Age 7 </gallery> | image2 = <gallery> Attached Melon Stem (N).png | North Attached Melon Stem (E).png | East Attached Melon Stem (S).png | South Attached Melon Stem (W).png | West </gallery> | transparent = Yes | light = No | tool = none | renewable = Yes | stackable = Yes (64) | flammable = No | lavasusceptible = No }}'''Melon seeds''' are items obtained from [[Melon Slice|melon slices]] that can be used to grow melon stems. '''Melon stems''' are plants grown on [[farmland]] that, over time, grow [[melon]]s on dirt, mud and moss blocks adjacent to them. == Obtaining == === Breaking === When broken, a melon stem drops 0–3 melon seeds. The chance for melon seeds to drop increases with the stem's age. {| class="wikitable" ! rowspan="3" |[[Resource location]] ! rowspan="3" | Source ! colspan="4" | Default |- | colspan="1" rowspan="2" style="text-align:center" | Nothing || colspan="3" style="text-align:center" |{{ItemLink|Melon Seeds|Melon seeds}} |- | style="text-align:center" | 1 || style="text-align:center" | 2 || style="text-align:center" | 3 |- | rowspan="8" |<code>blocks/melon_stem</code> |{{BlockLink|Melon Stem|Melon stem}} <code>age = 0</code> | style="text-align:center" |81.3%|| style="text-align:center" |17.42%|| style="text-align:center" |1.24%|| style="text-align:center" |0.03% |- |{{BlockLink|Melon Stem|Melon stem}} <code>age = 1</code> | style="text-align:center" |65.1%|| style="text-align:center" |30.04%|| style="text-align:center" |4.62%|| style="text-align:center" |0.24% |- |{{BlockLink|Melon Stem|Melon stem}} <code>age = 2</code> | style="text-align:center" |51.2%|| style="text-align:center" |38.4%|| style="text-align:center" |9.6%|| style="text-align:center" |0.8% |- |{{BlockLink|Melon Stem|Melon stem}} <code>age = 3</code> | style="text-align:center" |39.44%|| style="text-align:center" |43.02%|| style="text-align:center" |15.64%|| style="text-align:center" |1.9% |- |{{BlockLink|Melon Stem|Melon stem}} <code>age = 4</code> | style="text-align:center" |29.13%|| style="text-align:center" |44.44%|| style="text-align:center" |22.22%|| style="text-align:center" |3.7% |- |{{BlockLink|Melon Stem|Melon stem}} <code>age = 5</code> | style="text-align:center" |21.6%|| style="text-align:center" |43.2%|| style="text-align:center" |28.8%|| style="text-align:center" |6.4% |- |{{BlockLink|Melon Stem|Melon stem}} <code>age = 6</code> | style="text-align:center" |15.17%|| style="text-align:center" |39.82%|| style="text-align:center" |34.84%|| style="text-align:center" |10.16% |- |{{BlockLink|Melon Stem|Melon stem}} <code>age = 7</code> | style="text-align:center" |10.16%|| style="text-align:center" |34.84%|| style="text-align:center" |39.82%|| style="text-align:center" |15.17% |- | rowspan="1" |<code>blocks/attached_melon_stem</code> |{{BlockLink|Attached Melon Stem|Attached Melon stem}} | style="text-align:center" |10.16%|| style="text-align:center" |34.84%|| style="text-align:center" |39.82%|| style="text-align:center" |15.17% |} === Natural generation === Melon stems generate naturally in stem farm inside [[woodland mansion]]s. Melon stems generate in 20% of the farm plots in [[savanna]] [[village]]s, and 10% of the farm plots in [[desert]] villages. === Chest loot === {{LootChestItem|melon-seeds}} === Crafting === {{Crafting |Melon Slice |Output= Melon Seeds |type= Material }} === Trading === [[Wandering trader]]s sell melon seeds for 1 [[emerald]]. == Usage == === Farming === {{see also|Tutorials/Pumpkin and melon farming}} Melon seeds can be planted only on [[farmland]], as stems. Over time, a stem grows through several stages<sup>[''[[Talk:Pumpkin Seeds|needs testing]]'']</sup> and, at its final growth stage, will produce [[melon]]s on any adjacent [[dirt]], [[Coarse Dirt|coarse dirt]], [[Rooted Dirt|rooted dirt]], [[Grass Block|grass block]], [[farmland]], [[podzol]], [[mycelium]], [[Moss Block|moss block]], [[mud]] or [[Muddy Mangrove Roots|muddy mangrove roots]]. If a melon is already occupying a spot adjacent to a stem it does not grow more melons until the melons is removed. A single stem can grow an unlimited number of melons. Melon stems need a minimum light level of 10 in the block above the stem to grow and give melons. Melon seeds are affected by [[bone meal]] only with respect to stem growth; bone meal does not help produce the actual melons. === Breeding === Like other seeds, melon seeds can be used to [[breed]] [[chicken]]s, lead chickens around, and make baby chickens grow up faster by 10% of the remaining time. === Taming === Like other seeds, melon seeds can be used to tame [[parrot]]s. === Composting === Placing melon seeds into a [[composter]] has a 30% chance of raising the compost level by 1. == Melon Stem == A '''melon stem''' is the block that is planted on [[farmland]] when melon seeds are used on it. It starts underground, and rises up as the plant grows. The stem is colored green when young, and then yellow once fully grown. The stem curves once a melon has grown from it. A fully-grown single stem connects to any [[melon]] in an adjacent square, thus there are 5 possible appearances to a stem. If there are multiple melons it can connect to, it favors the east, then west, north, and south. When the melon is removed, the stem returns to its straight shape. == Sounds == {{Sound table/Block/Hard crop}} == Data values == === ID === {{edition|java}}: {{ID table |edition=java |showblocktags=y |showforms=y |generatetranslationkeys=y |displayname=Melon Stem |spritetype=block |nameid=melon_stem |blocktags=bee_growables, crops |form=block}} {{ID table |displayname=Attached Melon Stem |spritetype=block |nameid=attached_melon_stem |form=block}} {{ID table |displayname=Melon Seeds |spritetype=item |nameid=melon_seeds |form=item |foot=1}} {{edition|bedrock}}: {{ID table |edition=bedrock |shownumericids=y |showforms=y |generatetranslationkeys=y |displayname=Melon Stem |spritetype=block |nameid=melon_stem |id=105 |form=block |translationkey=-}} {{ID table |displayname=Melon Seeds |spritetype=item |nameid=melon_seeds |id=293 |form=item |foot=1}} === Block states === {{see also|Block states}} {{/BS}} == Advancements == {{load advancements|A Seedy Place}} == History == {{info needed section|check if stems floated above farmland upon initial implementation}} {{History|java beta}} {{History||1.8|snap=Pre-release|[[File:Melon Seeds JE1 BE1.png|32px]] Added melon seeds. |[[File:Melon Stem Age 0 JE1.png|32px]] [[File:Stem Age 1 JE1.png|32px]] [[File:Melon Stem Age 2 JE1.png|32px]] [[File:Melon Stem Age 3 JE1.png|32px]] [[File:Melon Stem Age 4 JE1.png|32px]] [[File:Melon Stem Age 5 JE1.png|32px]] [[File:Melon Stem Age 6 JE1.png|32px]] [[File:Melon Stem Age 7 JE1.png|32px]] Added the melon stem, with seven stages of growth. |Melon seeds can found in the new [[mineshaft]] [[chest]]s. |[[File:Attached Melon Stem (N) JE1.png|32px]] [[File:Attached Melon Stem (E) JE1.png|32px]] [[File:Attached Melon Stem (S) JE1.png|32px]] [[File:Attached Melon Stem (W) JE1.png|32px]] Melon stems have four slightly visually distinct appearances for each facing direction - the bent part of the stem rotates, but the other two planes do not. |[[File:Melon Stem Age 8 JE1.png|32px]] [[File:Melon Stem Age 9 JE1.png|32px]] [[File:Melon Stem Age 10 JE1.png|32px]] [[File:Melon Stem Age 11 JE1.png|32px]] [[File:Melon Stem Age 12 JE1.png|32px]] [[File:Melon Stem Age 13 JE1.png|32px]] [[File:Melon Stem Age 14 JE1.png|32px]] [[File:Melon Stem Age 15 JE1.png|32px]] Melon stem data values 8–15 now show a glitched formation, with a floating stem with an attached stem cross eventually emerging below. |[[File:Attached Stem Age 8 JE1.png|32px]] [[File:Attached Stem Age 9 JE1.png|32px]] [[File:Attached Stem Age 10 JE1.png|32px]] [[File:Attached Stem Age 11 JE1.png|32px]] [[File:Attached Stem Age 12 JE1.png|32px]] [[File:Attached Stem Age 13 JE1.png|32px]] [[File:Attached Stem Age 14 JE1.png|32px]] [[File:Attached Stem Age 15 JE1.png|32px]] Melon stem blocks with data values higher than 7 can now attach to adjacent fruits, which results in buggy stem textures with [[vines]] in the mix due to vines being below attached stems in [[terrain.png]].}} {{History|||snap=Pre-release 2 ;)|Melon stems can now be grown faster using [[bone meal]].}} {{History|java}} {{History||1.3.1|snap=1.3|The texture of melon stems has been moved one pixel to the left in [[terrain.png]]. |[[File:Melon Stem Age 0 JE2.png|32px]] [[File:Melon Stem Age 1 JE2.png|32px]] [[File:Melon Stem Age 2 JE2.png|32px]] [[File:Melon Stem Age 3 JE2.png|32px]] [[File:Melon Stem Age 4 JE2.png|32px]] [[File:Melon Stem Age 5 JE2.png|32px]] [[File:Melon Stem Age 6 JE2.png|32px]] [[File:Melon Stem Age 7 JE2.png|32px]] Stems now appear slightly different. |[[File:Melon Stem Age 8 JE2.png|32px]] [[File:Melon Stem Age 9 JE2.png|32px]] [[File:Melon Stem Age 10 JE2.png|32px]] [[File:Melon Stem Age 11 JE2.png|32px]] [[File:Melon Stem Age 12 JE2.png|32px]] [[File:Melon Stem Age 13 JE2.png|32px]] [[File:Melon Stem Age 14 JE2.png|32px]] [[File:Melon Stem Age 15 JE2.png|32px]] Overgrown stems now appear slightly different. |[[File:Attached Melon Stem (N) JE2.png|32px]] [[File:Attached Melon Stem (E) JE2.png|32px]] [[File:Attached Melon Stem (S) JE2.png|32px]] [[File:Attached Melon Stem (W) JE2.png|32px]] Attached melon stems now appear slightly different. |[[File:Attached Stem Age 8 JE2.png|32px]] [[File:Attached Stem Age 9 JE2.png|32px]] [[File:Attached Stem Age 10 JE2.png|32px]] [[File:Attached Stem Age 11 JE2.png|32px]] [[File:Attached Stem Age 12 JE2.png|32px]] [[File:Attached Stem Age 13 JE2.png|32px]] [[File:Attached Stem Age 14 JE2.png|32px]] [[File:Attached Stem Age 15 JE2.png|32px]] Overgrown attached melon stems now appear slightly different.}} {{History||1.4.2|snap=12w36a|[[Chicken]]s now use [[wheat seeds]], melon seeds, and [[pumpkin seeds]], instead of [[wheat]] to breed.}} {{History||1.5|snap=13w02a|[[File:Melon Stem Age 0 JE3.png|32px]] [[File:Melon Stem Age 1 JE3.png|32px]] [[File:Melon Stem Age 2 JE3.png|32px]] [[File:Melon Stem Age 3 JE3.png|32px]] [[File:Melon Stem Age 4 JE3.png|32px]] [[File:Melon Stem Age 5 JE3.png|32px]] [[File:Melon Stem Age 6 JE3.png|32px]] Melon stems now use a squished version of their texture for immature stems, depending on age. |[[File:Melon Stem Age 8 JE3.png|32px]] [[File:Melon Stem Age 9 JE3.png|32px]] [[File:Melon Stem Age 10 JE3.png|32px]] [[File:Melon Stem Age 11 JE3.png|32px]] [[File:Melon Stem Age 12 JE3.png|32px]] [[File:Melon Stem Age 13 JE3.png|32px]] [[File:Melon Stem Age 14 JE3.png|32px]] [[File:Melon Stem Age 15 JE3.png|32px]] This also affects melon stems of ages 8–15, which are likewise stretched to accommodate its predicted size. |[[File:Attached Stem Age 8 JE3.png|32px]] [[File:Attached Stem Age 9 JE3.png|32px]] [[File:Attached Stem Age 10 JE3.png|32px]] [[File:Attached Stem Age 11 JE3.png|32px]] [[File:Attached Stem Age 12 JE3.png|32px]] [[File:Attached Stem Age 13 JE3.png|32px]] [[File:Attached Stem Age 14 JE3.png|32px]] [[File:Attached Stem Age 15 JE3.png|32px]] Melon stems of extreme ages, which are attached to adjacent fruits, now show a stretched and tinted stem appearance.}} {{History|||snap=13w03a|[[File:Melon Stem Age 0 JE4.png|32px]] [[File:Melon Stem Age 1 JE4.png|32px]] [[File:Melon Stem Age 2 JE4.png|32px]] [[File:Melon Stem Age 3 JE4.png|32px]] [[File:Melon Stem Age 4 JE4.png|32px]] [[File:Melon Stem Age 5 JE4.png|32px]] [[File:Melon Stem Age 6 JE4.png|32px]] [[File:Melon Stem Age 7 JE4.png|32px]] Melon stems are no longer squished or stretched to account for age.<ref>{{bug|MC-7111}}</ref> |[[File:Melon Stem Age 8 JE4.png|32px]] [[File:Melon Stem Age 9 JE4.png|32px]] [[File:Melon Stem Age 10 JE4.png|32px]] [[File:Melon Stem Age 11 JE4.png|32px]] [[File:Melon Stem Age 12 JE4.png|32px]] [[File:Melon Stem Age 13 JE4.png|32px]] [[File:Melon Stem Age 14 JE4.png|32px]] [[File:Melon Stem Age 15 JE4.png|32px]] Melon stems with age values 8 through 15 now show a tinted [[trapdoor]] texture. |From this version up until 14w08a, overgrown melon stems start to draw from the texture below them on the [[texture atlas]], in much the same way they previously did with terrain.png. However, as texture atlases are unstable and textures tend to change positions as new blocks and textures are added, overgrown stems change the texture they draw from every time new textures are added, which includes when textures added by [[mods]].}} {{History|||snap=13w09a|[[File:Melon Stem Age 8 JE5.png|32px]] [[File:Melon Stem Age 9 JE5.png|32px]] [[File:Melon Stem Age 10 JE5.png|32px]] [[File:Melon Stem Age 11 JE5.png|32px]] [[File:Melon Stem Age 12 JE5.png|32px]] [[File:Melon Stem Age 13 JE5.png|32px]] [[File:Melon Stem Age 14 JE5.png|32px]] [[File:Melon Stem Age 15 JE5.png|32px]] Melon stems with age values 8–15 now show a tinted [[birch wood]] texture.}} {{History||1.6.1|snap=13w24a|Melon and pumpkin stems have now been assigned separate textures. |[[File:Melon Stem Age 8 JE6.png|32px]] [[File:Melon Stem Age 9 JE6.png|32px]] [[File:Melon Stem Age 10 JE6.png|32px]] [[File:Melon Stem Age 11 JE6.png|32px]] [[File:Melon Stem Age 12 JE6.png|32px]] [[File:Melon Stem Age 13 JE6.png|32px]] [[File:Melon Stem Age 14 JE6.png|32px]] [[File:Melon Stem Age 15 JE6.png|32px]] Melon stems with age values 8–15 now show a tinted [[note block]] texture.}} {{History||1.7.2|snap=13w37a|Added the {{cmd|setblock}} [[commands|command]], allowing for invalid stem ages to be placed in the world without using external editors. This also allows them to be obtained in earlier versions via backdating.}} {{History|||snap=13w41a|[[File:Melon Stem Age 8 JE7.png|32px]] [[File:Melon Stem Age 9 JE7.png|32px]] [[File:Melon Stem Age 10 JE7.png|32px]] [[File:Melon Stem Age 11 JE7.png|32px]] [[File:Melon Stem Age 12 JE7.png|32px]] [[File:Melon Stem Age 13 JE7.png|32px]] [[File:Melon Stem Age 14 JE7.png|32px]] [[File:Melon Stem Age 15 JE7.png|32px]] Melon stems with age values 8–15 now show a tinted [[netherrack]] texture.}} {{History||1.8|snap=14w10a|[[File:Melon Stem Age 8 JE8.png|32px]] [[File:Melon Stem Age 9 JE8.png|32px]] [[File:Melon Stem Age 10 JE8.png|32px]] [[File:Melon Stem Age 11 JE8.png|32px]] Melon stems with data values 8–11 now display a tinted attached stem, with 8 facing west, 9 facing east, 10 facing north and 11 facing south. |Invalid melon stems with data values 12-15 now crash the game.}} {{History|||snap=14w25a|[[File:Melon Stem Age 0 JE5.png|32px]] [[File:Melon Stem Age 1 JE5.png|32px]] [[File:Melon Stem Age 2 JE5.png|32px]] [[File:Melon Stem Age 3 JE5.png|32px]] [[File:Melon Stem Age 4 JE5.png|32px]] [[File:Melon Stem Age 5 JE5.png|32px]] [[File:Melon Stem Age 6 JE5.png|32px]] [[File:Melon Stem Age 7 JE5.png|32px]] Melon stems now render as a single diagonal plane, or, in the case of attached stems, a diagonal and orthogonal plane. |[[File:Attached Melon Stem (N) JE3.png|32px]] [[File:Attached Melon Stem (E) JE3.png|32px]] [[File:Attached Melon Stem (S) JE3.png|32px]] [[File:Attached Melon Stem (W) JE3.png|32px]] The attached melon stem [[model]] now fully rotates to the direction the stem points. Prior to this update, the base of the melon stem would stay the same while the long attaching section would differ, resulting in four possible attached stem appearances. |Invalid overgrown melon stems have effectively been removed from the game, as attempting to place an out of range stem via {{cmd|setblock}} creates a stem of age 0 and loading a world with such stems existing causes a game crash.}} {{History|||snap=14w26a|[[File:Melon Stem Age 0 JE6.png|32px]] [[File:Melon Stem Age 1 JE6.png|32px]] [[File:Melon Stem Age 2 JE6.png|32px]] [[File:Melon Stem Age 3 JE6.png|32px]] [[File:Melon Stem Age 4 JE6.png|32px]] [[File:Melon Stem Age 5 JE6.png|32px]] [[File:Melon Stem Age 6 JE6.png|32px]] [[File:Melon Stem Age 7 JE6.png|32px]] [[File:Attached Melon Stem (N) JE4.png|32px]] [[File:Attached Melon Stem (E) JE4.png|32px]] [[File:Attached Melon Stem (S) JE4.png|32px]] [[File:Attached Melon Stem (W) JE4.png|32px]] Melon stems now correctly render as crosses again.<ref>{{bug|MC-58136}}</ref>}} {{History|||snap=14w27a|[[File:Attached Stem Age 0 14w27a.png|32px]] [[File:Attached Stem Age 1 14w27a.png|32px]] [[File:Attached Stem Age 2 14w27a.png|32px]] [[File:Attached Stem Age 3 14w27a.png|32px]] [[File:Attached Stem Age 4 14w27a.png|32px]] [[File:Attached Stem Age 5 14w27a.png|32px]] [[File:Attached Stem Age 6 14w27a.png|32px]] Due to a bug, all melon stems appear attached regardless of age or any actual attachment.<ref>{{bug|MC-60208}}</ref>}} {{History|||snap=14w28a|All melon stems appearing attached regardless of age or any actual attachment has been fixed. However, melon stems still appear attached to adjacent fruits regardless of age due to a similar bug.<ref>{{bug|MC-61716}}</ref>}} {{History|||snap=14w34d|Melon seeds can no longer be used for [[breeding]] [[chicken]]s.}} {{History||1.9|snap=15w31a|Chickens can now use melon seeds to breed again.}} {{History|||snap=15w44a|Melon seeds have been added to [[dungeon]] [[chest]]s. |The average yield of melon seeds from [[mineshaft]] chests has been decreased.}} {{History|||snap=15w45a|Melon stems must now be fully grown again to attach.}} {{History||1.11|snap=16w39a|Melon seeds can now be found inside chests in the new [[woodland mansion]]s. |Melon crops now generate inside woodland mansions.}} {{History||1.12|snap=17w18b|Placing a melon seeds in farmland now gives the player the "A Seedy Place" [[advancement]].{{verify}}}} {{History||1.13|snap=17w47a|The different block states for the <code>melon_stem</code> ID have been split up into their own IDs. |Prior to [[1.13/Flattening|''The Flattening'']], this [[block]]'s numeral ID was 105, and the [[item]]'s 362.}} {{History|||snap=17w48a|Attached melon stems no longer [[drops|drop]] seeds.}} {{History||1.14|snap=18w43a|[[File:Attached Melon Stem (N) JE5.png|32px]] [[File:Attached Melon Stem (E) JE5.png|32px]] [[File:Attached Melon Stem (S) JE5.png|32px]] [[File:Attached Melon Stem (W) JE5.png|32px]] The texture of attached melon stems has been changed.}} {{History|||snap=18w49a|Melon stems now generate in the updated [[savanna]] [[village]]s.}} {{History|||snap=18w50a|Melon stems now generate in the updated [[desert]] [[village]]s.}} {{History|||snap=19w03a|Placing melon seeds into the new [[composter]] has a 10% chance of raising the compost level by 1.}} {{History|||snap=19w05a|Melon seeds now have a 30% chance of increasing the compost level in a composter by 1. |Added [[Wandering Trader|wandering trader]]s, which sell melon seeds.}} {{History||1.15|snap=19w34a|[[Bee]]s can now pollinate melon stems.}} {{History|||snap=19w39a|Attached melon stems now [[drops|drop]] seeds again.<ref>{{bug|MC-136360}}</ref>}} {{History||1.18|snap=Pre-release 5|[[File:Melon Seeds JE2.png|32px]] The texture of melon seeds has been changed.}} {{History|pocket alpha}} {{History||v0.5.0|Added melon seeds. |[[File:Melon Stem Age 0 JE1.png|32px]] [[File:Stem Age 1 JE1.png|32px]] [[File:Melon Stem Age 2 JE1.png|32px]] [[File:Melon Stem Age 3 JE1.png|32px]] [[File:Melon Stem Age 4 JE1.png|32px]] [[File:Melon Stem Age 5 JE1.png|32px]] [[File:Melon Stem Age 6 JE1.png|32px]] [[File:Melon Stem Age 7 JE1.png|32px]] [[File:Attached Melon Stem (N) JE1.png|32px]] [[File:Attached Melon Stem (E) JE1.png|32px]] [[File:Attached Melon Stem (S) JE1.png|32px]] [[File:Attached Melon Stem (W) JE1.png|32px]]{{verify|Are these models correct?}} Added melon stems.}} {{History||v0.6.0|[[File:Melon Seeds JE1 BE1.png|32px]] Melon seeds no longer use the pumpkin seeds texture.}} {{History||v0.9.0|snap=?|Melon seeds can now be found in [[mineshaft]] chests.}} {{History||v0.12.1|snap=build 1|Melon seeds are no longer available from the [[Nether reactor]].}} {{History||v0.14.0|snap=build 1|Melon seeds can now be found in [[minecart with chest|minecarts with chests]] in [[mineshaft]]s.}} {{History|pocket}} {{History||1.0.0|snap=alpha 0.17.0.1|Melon seeds now generate inside [[dungeon]] [[chest]]s.}} {{History||1.1.0|snap=alpha 1.1.0.0|Melon crops now generate inside [[woodland mansion]]s. |Melon seeds can now be found in woodland mansion chests.}} {{History|bedrock}} {{History||1.2.0|snap=beta 1.2.0.2|Melon seeds can now be found inside [[bonus chest]]s. |Melon seeds are now used to tame [[parrot]]s.}} {{History||1.10.0|snap=beta 1.10.0.3|[[File:Attached Melon Stem (W) JE5.png|32px]]{{info needed|More accurate image}} The texture of attached melon stems has been changed. |Melon stems now generate in [[savanna]] and [[desert]] [[village]] farms. |Added [[wandering trader]]s, who [[trading|sell]] melon seeds.}} {{History||1.11.0|snap=beta 1.11.0.1|Melon seeds can now be used to fill up [[composter]]s.}} {{History||1.14.0|snap=beta 1.14.0.1|[[Bee]]s can now pollinate melon stems.}} {{History|console}} {{History||xbox=TU5|xbone=CU1|ps=1.0|wiiu=Patch 1|[[File:Melon Seeds JE1 BE1.png|32px]] Added melon seeds. |[[File:Melon Stem Age 0 JE1.png|32px]] [[File:Stem Age 1 JE1.png|32px]] [[File:Melon Stem Age 2 JE1.png|32px]] [[File:Melon Stem Age 3 JE1.png|32px]] [[File:Melon Stem Age 4 JE1.png|32px]] [[File:Melon Stem Age 5 JE1.png|32px]] [[File:Melon Stem Age 6 JE1.png|32px]] [[File:Melon Stem Age 7 JE1.png|32px]] [[File:Attached Melon Stem (N) JE1.png|32px]] [[File:Attached Melon Stem (E) JE1.png|32px]] [[File:Attached Melon Stem (S) JE1.png|32px]] [[File:Attached Melon Stem (W) JE1.png|32px]]{{verify|Are these models correct?}} Added melon stems.}} {{History||xbox=none|xbone=none|ps=1.90|wiiu=none|switch=none|[[File:Attached Melon Stem (W) JE5.png|32px]]{{info needed|More accurate image}} The texture of attached melon stems has been changed.}} {{History|New 3DS}} {{History||0.1.0|[[File:Melon Stem Age 0 JE1.png|32px]] [[File:Stem Age 1 JE1.png|32px]] [[File:Melon Stem Age 2 JE1.png|32px]] [[File:Melon Stem Age 3 JE1.png|32px]] [[File:Melon Stem Age 4 JE1.png|32px]] [[File:Melon Stem Age 5 JE1.png|32px]] [[File:Melon Stem Age 6 JE1.png|32px]] [[File:Melon Stem Age 7 JE1.png|32px]] [[File:Attached Melon Stem (N) JE1.png|32px]] [[File:Attached Melon Stem (E) JE1.png|32px]] [[File:Attached Melon Stem (S) JE1.png|32px]] [[File:Attached Melon Stem (W) JE1.png|32px]]{{verify|Are these models correct?}} Added melon stems.}} {{History|foot}} <gallery> Melon Stem with data value 15.png|The final version of the melon stem with age 15, as seen in-game. Melonstems.png|Melon stems of ages 1–15 on a modded version of 1.7.2, hence the melon stems using the melon top texture. Stems of 13w02a.png|All 16 stem sizes in 13w02a, with accompanying data values. </gallery> === Melon stem "item" === {{:Technical blocks/Melon Stem}} == Issues == {{issue list}} == Gallery == <gallery> Stem All Ages.png|All stages of growth. AllSeeds.png|All the [[seeds]] that exist in the game. </gallery> == See also == * [[Melon]] * [[Pumpkin Seeds]] ==References== {{Reflist}} {{Blocks|vegetation}} {{Items}} [[Category:Plants]] [[Category:Food]] [[Category:Non-solid blocks]] [[Category:Generated structure blocks]] [[cs:Semínka melounu]] [[de:Melone]] [[es:Semillas de sandía]] [[fr:Graines de pastèque]] [[hu:Dinnyemagok]] [[it:Anguria]] [[ja:スイカの種]] [[ko:수박씨]] [[nl:Meloenzaden]] [[pl:Nasiona arbuza]] [[pt:Sementes de melancia]] [[ru:Семена арбуза]] [[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. 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.

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

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

I  Support to use the first, because the features won't be part of 1.16.x releases, and it's more specific. Thejoaqui777 (talk) 23:54, 26 January 2021 (UTC)

They are part of the 1.16.210 betas, and it should be declared that way. Saying the beta is for 1.17 is false information. Dhranios (talk) (Join the wiki videos project!) 00:16, 27 January 2021 (UTC)

Should say 1.16.210, with "added under experimental gameplay", then 1.17 with "fully implemented".  Nixinova   T   C   00:26, 1 February 2021 (UTC)

Proposal for a Crossovers page, replacing the current Smash page

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

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

Request for a new page - but I need your help

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

It is unnotable to be given an article. TheGreatSpring (talk) 05:28, 7 February 2021 (UTC)

It is completely trivial information, so it doesn't belong anywhere on this wiki, except perhaps a subpage of your userpage. Fadyblok240 (talk) 05:40, 7 February 2021 (UTC); updated 06:12, 7 February 2021 (UTC)

Okay then...I guess I would not create it - Melvintnh327 (talk) 02:23, 11 February 2021 (UTC)

What happened?

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

Another glitch with UCP, this is the worst one so far. James Haydon (talk) 16:41, 11 February 2021 (UTC)

Fandom rolled out an update that broke the platform. They quickly rolled it back though.

While they were rolling it back though, Minecraft Wiki played the roles of: 1) London Bird Club Wiki; 2) Wookieepedia; 3) the Pixel Gun Wiki and the Game of Thrones Wiki simultaneously. Oh, and half the platform was the Raft Wiki for a few moments. --AttemptToCallNil (talk) 16:58, 11 February 2021 (UTC)

I don't think there even is a Game of Thrones wiki on Gamepedia because its not a game. So it also is affecting FANDOM wikis as well. James Haydon (talk) 17:01, 11 February 2021 (UTC)

Yes, it affected the entire platform, including all Fandom wikis. --AttemptToCallNil (talk) 17:04, 11 February 2021 (UTC)

Minecraft Story Mode NS

Hi

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

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

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

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

 Support We have pretty bad situation, on Google, even Fandom's MCW has higher ranking, so we are in bad situation --TreeIsLife (talk) 19:05, 13 February 2021 (UTC)

 Temporal oppose, let me explain. It has been some months since the discussion, but I think that we should contact first their admins. I don't want them to think that we try to compete with them, instead to colaborate. Your words look very competitive, which isn't how this wiki wants to get information. We talk with people, and try to get a deal with them to make both parts happy. So, I think that we should wait 2 months more at least to begin talking with them again, because they refused to merge due to bad communication. Thejoaqui777 (talk) 19:21, 13 February 2021 (UTC)

 Comment TreeIsLife, I agree with Thejoaqui777, why are you making this a competition? MC wiki isnt a promotion wiki. Minecraft Story Mode is a WIP and the Minecraft Story Mode in FANDOM is fine, what makes you think that MC wiki is a promotional wiki? I also  Oppose per my comment on the previous discussion. I'm fine with the namespace but not trying to outmanuver fandom, gamepedia is owned by fandom anywaysHumiebee (talk) 19:25, 13 February 2021 (UTC)

This, this, this, this, this, this and this. It's not a competition. This exact behavior is what made the initial merge proposal fail badly. Dhranios (talk) (Join the wiki videos project!) 19:33, 13 February 2021 (UTC)

 Comment to all. This is not about competition. We tried... but... it did not go well. Hummie may not know about that, but there is great server, called Minecraft Wiki Crossover, where we discussed future of MC Wikis (all of them). We had a big dream. 3 big wikis for everything Minecraft - Minecraft Wiki, Minecraft Community Wiki and Minecraft Mods Wiki. And, we wanted to start with merging of all wikis from "Minecraft Wiki Network" into this wiki. Anddddd... I created discussion post, and we had protest on that wiki. I was critized about how i wrote it, and that i wrote it into discussions. Then, i decided i will left server, and do discussion by myself. So great, i had another conflict on another wiki (double problem). Unfortunately, discussion just failed and that's it. And now everybody hates me 😔. That was joke, obviously, I said it was my fault, and we discussed we won't say nothing to community, until we will lock the wiki (meaning only discussing with admins). And now, let's say why i want to do this. Well, they are inactive and only 1 person said something, but his timestamp between answers were 1 week.--TreeIsLife (talk) 19:41, 13 February 2021 (UTC)

Minicraft?

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

 Weak oppose this wiki is about Minecraft. TheGreatSpring (talk) 23:04, 13 February 2021 (UTC)

 Comment Well, 0x10c has its own wiki page, and yet it isn't a minecraft related game, it was developed by mojang, but wasn't really minecraft-like. James Haydon (talk) 23:23, 13 February 2021 (UTC)

 Comment But it was made by Notch, and has a lot of things from Minecraft (such as creepers), even the name is based on Minecraft --Gtbot2007 (talk) 23:53, 13 February 2021 (UTC)

Minicraft already has a page, but it is a redirect. Fadyblok240 (talk) 01:26, 14 February 2021 (UTC)

I guess because it wasn't developed by mojang unlike 0x10c and it wasn't nearly publicized as much. Makes sense why it doesn't have its own page. James Haydon (talk) 01:30, 14 February 2021 (UTC)

Redirects are pages too. Fadyblok240 (talk) 02:58, 14 February 2021 (UTC)

@Fadyblok240: By page I meant articles, no need to correct me about that. James Haydon (talk) 18:41, 14 February 2021 (UTC)

But its a minecraft game unlike 0x10c

 Comment The reason I felt the need to create the 0x10c page is because, unlike other games made by Notch or Mojang, you can't actually play it because it never came out, and so it doesn't have a wiki of its own (not anymore anyway). Now, on the other hand, Minicraft is a game you can play and it does have its own wiki, but, keep in mind, it is technically an official Minecraft spinoff game, and all the other official Minecraft spinoffs get to be on this wiki, so why not that one too? Plus the Minicraft wiki is really messy and incomplete, so I definitely wouldn't be opposed to something better being added to this wiki. AlienAgent124 (talk) 03:08, 14 February 2021 (UTC)

This is what I mean --172.58.228.82 09:27, 14 February 2021 (UTC)

Pocket/Bedrock Edition version pages

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

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

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

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

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

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

Necessary, no, but it is a change I'd support. The only thing is that bedrock's beta builds aren't as distinguishable from the full build, compared to java's snapshots; betas only have 1 additional ".X", unlike snapshots which use a vastly different naming altogether. Dhranios (talk) (Join the wiki videos project!) 08:36, 14 February 2021 (UTC)

Oppose new naming scheme (the example given isn't actually relevant, the "/snapshot" isn't part of the version), and "beta" is useful for disambiguating. "The articles don't need to be exactly the same as shown in game"; they are though. Support parameter rename.  Nixinova   T   C   18:55, 14 February 2021 (UTC)

Although the existence of "alpha/beta" , "v" , parentheses and spaces have certain significance, it's not so significant as to benefit from changing the title. Now the whole title is long and scattered. According to what you said, "it is useful for disambiguating". But most of the time, the correct page cannot be found. In daily communication, few people would say "beta 1.16.210.59", most people would say "1.16.210.59" directly. Personally, I’m used to find pages directly with URLs instead of search functions. If the users who don’t know much about Wiki type an extra space or a wrong letter, and then find that the page does not exist, they won't know what to do (for example, I want to find "Bedrock Edition beta 1.16.210.59" but input "Bedrock Edition v1.16.210.59" or "Bedrock Edition 1.16.210.59"). If you ask "Why not use the search function?", if the title is changed to "Bedrock Edition 1.16.210.59", wouldn't the search function still be useful? Without various prefixes and suffixes, wouldn't the search efficiency be higher?--SkyE |  Talk · Contributions · Logs 13:24, 16 February 2021 (UTC)

 One more problem. Word "alpha" was not shown since 0.14, can we recognize that versions from 0.14 to 0.16 belong the Alpha development stage? --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

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

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

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

Style 1 - Append onto existing MCW:STYLE page.

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

Style 2 - A subpage of MCW:STYLE.

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

Style 3 - A page within the Minecraft Dungeons namespace.

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

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

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

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

Style 1

I don't fully agree with this approach. Pertaining to keeping different kind of information simultaneously can be difficult to navigate and may lead to some confusion. A similar problem to this is the difference of information between Java and Bedrock. So as to resolve, the community decided to use {{in}}/{{only}} whenever the provided information contain disparities. This solution should not be used in terms of information that are fundamental to the wiki, like style guides. Another solution such as adding a background color or new section wouldn't help as much. Furthermore, similar styling to background color has already been defined and it requires new knowledge for people to realize the distinction.

Style 2

I totally agree in separating the page from the main style guide. By separating the page, there will be more freedom for expansion whilst not polluting the current page with MCD guides. Regarding misdirections, they are enough to be resolved by using a hat note or message box. For page name, I would say that Minecraft_Wiki:Style_guide/Minecraft_Dungeons is good enough.

Before talking about extensions to the style guide, maybe the editors of Minecraft Dungeons articles could work harder to follow the basic style guidelines that already exist, such as not using title case in headings, not capitalizing things in text that aren't proper nouns, refraining from filling articles with indiscriminate lists of trivia (which I have worked hard to clean up), and so on. The last thing we need is new guidance that conflicts with or creates exceptions to guidelines we already have. Amatulic (talk) 02:38, 1 June 2021 (UTC)

Style 3

It would be more appropriate to put meta information in the Minecraft Wiki namespace. As for MCD:Style, I guess it can be used as a redirect to the MCW namespace for shortcut. Also I wouldn't personally be bothered with the design aspect of the page.

In addition, I feel like the sidebar could have the style guide to link specifically when you are in the MCD namespace. Thus resolving the concern of exposure of the page, especially to MCD editors. Other maintenance/community pages like community portal, projects, etc. shouldn't be a concern, at least for now. – ItsPlantseed ⟨₰|₢⟩ 11:20, 16 February 2021 (UTC)

Having a dynamic sidebar that alters to suit the namespace the user is in would be a brilliant implementation and not just for the style guide exposure. I do recall a discussion in the discord where an issue that prevents namespace dependent sidebars from functioning was mentioned. I suppose until that is resolved, we can’t poke the sidebar in a dynamic fashion. Could have Dungeons Style Guide be under Style Guide until that fix arrives.

Style 1 could certainly end up becoming messy and unclear for all members involved, I agree with your views.

Style 2 & 3 design aspect is agreeably low priority and appropriate location should have possess weight. Some design aspects can be determined by the page through the source so things can be solved on that front.

Minecraft_Wiki:Style_guide/Minecraft_Dungeons with MCD:Style and MCW:Style Dungeons as redirects perhaps? Maybe only the one redirect shortcut is required. 🍍 Raybeano99 (Talk) 14:55, 16 February 2021 (UTC)

Centralised Datapage

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

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

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

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

Wiki channel in the Official Dungeons Discord

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

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

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

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

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

Tabbed Mob pages

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

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

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

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

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

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

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

Oppose, I don't think this is a useful way of using tabs. Tabs tend to cause accessibility and technical problems as you said (I'd also add that links to anchors in non-default tabs may not work). Fandom staff keep telling editors that research has shown tabs are not an effective way of conveying information as tabs other than the first will be ignored by a large portion of readers. I'm not sure about your third point, I'd say this isn't a factor at all. About the second point, is "fun related" a typo for "unrelated"? I'm not sure what "fun related" means. --AttemptToCallNil (talk) 18:29, 8 April 2021 (UTC)

Typo… not sure how fun got in there. Has been corrected.

Yeah I could envision folk not recognising the tabs as clickable and missing the information enclosed within them thinking about it more. Wondering if there are other ways that the merge could be achieved… or perhaps the standard information suffixing might not be as encumbering as initially imagined. Would love any different ideas. 🍍 Raybeano99 (Talk) 18:54, 8 April 2021 (UTC)

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)

If correct, that was the reason --TreeIsLife (talk) 09:06, 18 March 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)