Talk: Community portal

This is the community's main discussion page.
Talk about anything wiki-related here!
Sign your posts with ~~~~, add new posts below others, and click "Add topic" above for new topics.
Note that this page is NOT for suggesting new ideas about the game. That belongs on the feedback site.

Weird list formatting in Navboxes (fixed)

Hello there, I just noticed that the horizontal lists in navboxes have some weird spacing if there are child nodes. (Example: Template:Blocks) After every opening bracket, there is a text node containing a space, and after every closing bracket, there is some space missing.

Does someone know how to fix this? I would try to, but I don't want to break other stuff. | violine1101^(Talk) 10:54, 19 November 2017 (UTC)

I'm not sure myself why this happens, but I'm certain I've not seen it do this at least before the host move. I observe that for some reason the spacing at the end of a single list item is used up by the closing bracket of the sublist in it. From what I understand looking at it for the first time, the closing brackets are not included in the spacing caused by :after spacing in each li element, or the spacing of the element itself. – Jack McKalling ^{(t • c • p)} 11:09, 19 November 2017 (UTC)

Okay I think I figured it out. I was right about the spacing, a negative spacing was used on the wrong side of the bracket. I've called in help to fix this on the stylesheet.– Jack McKalling [

] 00:11, 7 December 2017 (UTC)

Fixed, see here. Let me know if you spot anything else, Violine1101. – Jack McKalling [

] 08:31, 7 December 2017 (UTC)

Thank you. I wish I noticed earlier that this has been solved. | violine1101^(Talk) 15:30, 22 February 2018 (UTC)

Seasons

I see this done way too much, so I decided to post about it here. Can we please stop using seasons as time indicators. Seasons are not global, what is summer in the northern hemisphere is winter in the southern one. I know quarters (Q1, Q2, Q3, and Q4) are also far from perfect but I think they're way better than seasons.

This is not aimed towards anyone in specific, but I see people do this every so often and I figured I might as well try to stop them by posting here (small chance, I know. But still). --Pepijn (talk) 12:08, 25 November 2017 (UTC)

Maybe we could discuss putting this in the style guide? – Sealbudsman ^talk/_contr 18:55, 26 November 2017 (UTC)

Agree I get annoyed by this as well (people seem to forget about the southern hemisphere a lot). – Nixinova

06:47, 21 April 2018 (UTC)

Where should data and protocol versions be documented?

There's two pieces of version-specific information that aren't currently documented on this wiki:

Protocol versions, which are used in the network protocol to make sure servers and clients are compatible.
Data versions, which are used in chunks and in other files for the DataVersion tag, so that data can be upgraded between different versions.

While neither of these things are useful for the average player, they're useful for developers. Protocol versions are currently documented on wiki.vg (n.b. the overlap between content here and on wiki.vg is another thing which I've been meaning to post about for around a year but haven't gotten to yet, but let's just not worry about that for now). However, data versions are undocumented on either wiki. I've generated a list of them using Burger, though.

Where should these be put on this wiki? For sure it would be useful to have them on {{Version nav}}, but I'm thinking it'd also be useful to have them (or at least data versions) on another table somewhere so that it's easy to look up the version(s) corresponding to each number.

I'd be willing to handle adding the information to whatever articles need it (I may want to script the process though since it'd be adding information to all the versions). I just don't know where. --Pokechu22 (talk) 00:03, 17 December 2017 (UTC)

Are there any arguments or reasons not to add "Data versions" and "Protocol versions" articles (or maybe "version history", to match our other version history pages)? If not, I think that'd be the natural choice. 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 00:51, 17 December 2017 (UTC)

The only issue I have with that is that it feels awkward to create articles for each. Maybe a combined "Version numbers" article would be better. (Also, there is PE; I have no clue how or if PE numbers its protocol) --Pokechu22 (talk) 02:47, 17 December 2017 (UTC)

If the mentioned subjects are about the internals of the game engine, so technical that it requires reverse engineering to figure out, then it's probably not intended for the scope of this wiki. The source code is not meant for the public, it is obfuscated for a reason. So I don't even think doing this is legal. I'm not sure though, I just glanced over these subjects and I'm not certain what it's all about. But that's my two cents. – Jack McKalling [

] 20:11, 17 December 2017 (UTC)

Data versions are stored in several parts of NBT. We document the NBT format even though that's internal. Also, MCP is (partially) maintained by mojang devs (Searge in particular) -- in particular the SRG deobfuscation mappings -- and the EULA doesn't prohibit reverse engineering (only redistribution) unlike that for most games.

Whether or not it is in scope is a valid question, though. wiki.vg hosts the majority of the technical documentation (except for some classic stuff and other things, but again I'm not ready to hold the discussion about the overlap yet); it would be entirely possible to put the documentation for data versions there (PVNs are already there). --Pokechu22 (talk) 20:20, 17 December 2017 (UTC)

I see reason to be cautious about this. This very technical data will have to be obtained, maintained, and explained by experts well versed in the subject matter. Will the data be verifiable by means of automation and be noncontroversial as to its meaning and interpretation? Probably both, but if there's room for differing opinions we could get ourselves stuck between two camps of experts with no way to vet any statements they make nor participate with them in the consensus building process. In a normal wiki you'd have a professional community to fall back on, but you won't have that in this case. – Auldrick (talk · contribs) 23:45, 17 December 2017 (UTC)

Very good point. I would consider this one of the reasons for it being out of scope. All editors should have equal viable access to the source of information, like in-game observations, twitter posts and the website, but internal source code which would require expert analysis does not belong to that. It would at least require (Java) programming knowledge and trusted deobfuscation technologies. I wouldn't classify the NBT format to be internal source code however, as it is a portable format used to communicate with the source code. It's more of a data container similar to json files, used to e.g. enhance in-game command abilities. So NBT does fall under the scope of this wiki and is open to be used and interpreted by the public. – Jack McKalling [

] 00:10, 18 December 2017 (UTC)

Burger, which I mentioned before, automatically extracts this data. Here's sample data for 17w50a (well, that's actually burger + burger vitrine; burger itself gives json data).

There's other internal data we have on the wiki. For instance, numeric entity IDs are not displayed anywhere in game, but are cataloged on here (and on wiki.vg). Hardness is also an arbitrary, non-observable value (break times are, but individual hardness isn't), and we catalogue it; we also catalogue blast resistances. --Pokechu22 (talk) 00:22, 18 December 2017 (UTC)

Also worth noting that data version numbers are observable via just launching each version, loading a world, and observing the information in level.dat. However, protocol version numbers aren't observable that way, so it's either burger or capturing the handshake packet for each version. --Pokechu22 (talk) 00:28, 18 December 2017 (UTC)

I have no problem with us documenting NBT data, data/damage values, IDs, or any other internal data as long as it's verifiable and noncontroversial, which was the point of my comment. I'm reassured by these replies. – Auldrick (talk · contribs) 00:50, 18 December 2017 (UTC)

I've learned (by complete happenstance and on two separate occasions) that:

The German wiki currently has data versions, listed both on their version history page (which has multiple versions on it) and an incomplete list on their data values page. (I don't speak German). What's more, they also mention that you can use /testfor @p {DataVersion:<ID>} to check data versions and branch with command blocks -- but this probably also means that it's visible through /entitydata. So that's a way to verify these ingame, without even using an NBT editor.
The Dutch wiki has added protocol version numbers to their version pages (as mentioned in the Gamepedia slack). They actually did this in a way that didn't require bulk edits to all of the pages; instead, they changed their version nav template to automatically add the version:
```
{{#if: {{{geen_protocol|}}} | |
{{infobox row|[[Protocolversie]]nummer|<samp>{{#if: {{{protocolversie_handmatig|}}} | {{{protocolversie_handmatig}}} | {{protocolversie| {{{title}}} }} }}</samp> }}
}}
```
which we'd probably change to something like:
```
{{#if: {{{no_protocol|}}} | |
{{infobox row|[[Data versions#Protocol|Protocol version number]]|{{#if: {{{protocol_manual|}}} | {{{protocol_manual}}} | {{Protocol version| {{{title}}} }} }} }}
}}
```
They did this by creating a template that gets the version number given a version's name, using this module and this data. It looks like since then, they've also done the same for data versions.
The template can also generate a table, but the keys aren't sorted right now so that's a bit of a mess -- something for someone who knows lua better to handle.

I think that we should probably take the same approach as the dutch wiki, with the template to add the information automatically. While the template does mean you need to edit a different page to add info to the article, you'd still need to manually edit it to add it to a table that would be on data values; the template can do both and it would also mean that we wouldn't need to edit all the old articles.

The one thing that may be difficult for us is that we use our version nav template for all editions of the game, while they only cover Java Edition. So while they only have a few versions that would have no protocol info, we have a ton of them. (PE does actually appear to have a protocol version of some sort, but I don't know if the values for it are documented and I don't work with PE). A similar issue is present for data versions, as only versions after 1.9 have them; we wouldn't want to include info about those on versions they don't apply to.

In case it wasn't clear, I also thing it makes sense to put both of these numbers in the data values page; IMO there isn't a need for a separate article.

Anyways, those are my rambling thoughts. --Pokechu22 (talk) 01:43, 8 January 2018 (UTC)

Bump, sort of. I've edited the links in the text above to link to the correct modules, as I've renamed the modules while updating them (for hopefully a while, not counting releases). They still do the same thing, though. Thanks to pokechu22 tables are now generated correctly (see here) and we now only have to edit one module instead of two to get the version data in, which is good. --DarkShadowTNT NL Admin (t ♦ c) 15:56, 27 January 2018 (UTC)

Wiki inconsistencies

As I was looking through this wiki, I noticed a few inconsistencies that need to be addressed.

About a year ago at Talk:Diamond#Diamond obtaining? it was said that diamonds being obtainable by mining a nether reactor core is for the history section only, and is not to be included under Diamond#Obtaining,(as per mcw:UPTODATE). However, at Iron Ingot#Obtaining it clearly lists that mining a nether reactor core drops iron ingots. This goes against what was said on the diamond talk page before. Something needs to be done: either remove Iron Ingot#Mining from the Iron Ingot page, or add nether reactor core info to the Diamonds page.
At 1.3.1#Commands, it says that the /kill command was added in 1.3.1. However, at Commands#History it says that the /kill command was added in 1.2.6. Which is correct?

This last one is less of a concern but I'd figure I bring it up anyway:

Concerning the Spawning section in mob articles and what information is allowed there. At Talk:Chicken#Chicken Jockey? it mentions that the fact the Chickens being able to spawn as Chicken Jockeys does not exist under Chicken#Spawning because the Chicken Jockey's spawning is "handled when a baby zombie spawns". However, at Skeleton#Spawning the fact that skeletons can spawn as a Spider Jockey and as a part of a skeleton horse trap are documented there. Using the above logic, neither of those should be there, because the skeleton doesn't handle the spawning for either (the spider/skeleton horse trap does). You could even take it one step further and say the same on other articles, (e.g.: Witch#Spawning wouldn't say that witches spawn from villagers struck by lightning, because the spawning is handled by the lightning and not the witch). The point is, I vote to add that chickens can spawn as chicken jockies under Chicken#Spawning because that would make it consistent with every other mob article on this wiki.

-EatingSilencerforBreakfast (talk) 01:58, 17 December 2017 (UTC)

Regarding /kill: The command does not exist in the release 1.2.5 server, but does exist in the release 1.3.1 server. However, the comment about alpha 1.2.6 was added at the time that version was released. So probably, the command was removed somewhere in the middle. Unfortunately we don't have servers for those versions, so it's not possible to check when it was removed :/

Regarding chicken spawning: Support adding it there (making it clear that it is the zombie that does the spawning, though, because the spawn conditions vary) --Pokechu22 (talk) 03:03, 17 December 2017 (UTC)

Regarding the /kill part, during Alpha 1.2.6, it was only for SMP (Survival Multiplayer). It was added to single player on release 1.3.1 Skylord wars (talk) 09:17, 17 December 2017 (UTC)

I've removed the nether reactor bit from the iron ingot page, as I believe it's uncontroversial in being out of date - please challenge me if I'm wrong.

I support mentioning chicken jockey spawning, as Pokechu describes. – Sealbudsman ^talk/_contr 05:44, 18 December 2017 (UTC)

I added the chicken jockey information at Chicken#Spawning. -EatingSilencerforBreakfast (talk) 01:12, 27 December 2017 (UTC)

I noticed something similar. On the Beta 1.9 Prerelease 2 page it says that "Milk is now drinkable, resetting all potion effects currently afflicted upon the player." However, the milk page says that milk was made drinkable in Beta 1.8 but wasn't able to cure status effects until Beta 1.9 Prerelease 2, and on the 1.0.0 page, it mentions absolutely nothing about milk. --Madminecrafter12 (talk) 02:35, 4 January 2018 (UTC)

Mod Screenshot Licensing

How should files of screenshots that show mods in Minecraft be licensed? I know it's showing the game Minecraft, which would usually be Mojang, but because it shows mods that are not supported by Minecraft, shouldn't it use a separate license? --Madminecrafter12 (talk) 20:58, 1 January 2018 (UTC)

Correct. -Xbony2 (GRASP) (FTB Wiki Admin) (talk) 22:16, 1 January 2018 (UTC)

Internal error with history for "Tutorials/Creating a challenge map"

When I click on the "history" tab for the page Tutorials/Creating a challenge map, it has a giant box in red saying,
"[7ae048a3990d5e9ae0099026] /index.php?title=Tutorials/Creating_a_challenge_map&action=history Wikimedia\Assert\ParameterAssertionException from line 63 of /var/app/current/vendor/wikimedia/assert/src/Assert.php: Bad value for parameter $dbkey: invalid DB key 'Brenn_'",
and then it keeps going. The name of the page says it is "internal error". See https://minecraft.gamepedia.com/index.php?title=Tutorials/Creating_a_challenge_map&action=history, and you'll see what I mean. Does anyone know why this is and how to fix it?--Madminecrafter12 (talk) 01:33, 13 January 2018 (UTC)

Comment: you need to set your displayed changes limit to 250 or higher to get this error. A limit of 100 will not produce this error.

This seems to be caused by an invalid username in history. This is not the first time such an error occurs, and like the previous time, it should be reported to Curse. --AttemptToCallNil (report bug, view backtrace) 06:47, 13 January 2018 (UTC)

These are the first and last diffs that cause the issue. -- Orthotope^talk 07:05, 13 January 2018 (UTC)

I had this problem for another page too, but it's fixed now. – Jack McKalling [

] 10:39, 13 January 2018 (UTC)

Fixed by Gamepedia staff. --AttemptToCallNil (report bug, view backtrace) 15:22, 13 January 2018 (UTC)

Great, thanks! --Madminecrafter12 (talk) 19:27, 13 January 2018 (UTC)

~~Also, the maximum number of changes I have is 200, which is not 250 or higher, so I don't know why the error happened.~~ --Madminecrafter12 (talk) 19:28, 13 January 2018 (UTC)

Never mind, I previously didn't read Orthotope's comment thoroughly--Madminecrafter12 (talk) 19:29, 13 January 2018 (UTC)

Archive this page

Someone? It's already 2018. – ITechieGamer^tce 14:45, 18 January 2018 (UTC)

I've moved all the 2017-reply-only topics to Archive 21. – Nixinova 07:01, 21 April 2018 (UTC)

Plural case of redirects

I'm not exactly clear on when a plural redirect is acceptable. There have been many times when I have made a redirect to a page that's the plural case that the page got deleted, and other times where there was no request for deletion. I looked in the "Redirect Cleanup" project and it said that plural redirects should only be used when the singular case could not be linked to when writing the plural case (for example, [[Grass Block]]s would be possible). However, if this is true, than hundreds of the redirects on the Minecraft Wiki that have been existing for many years, would have to be deleted (Zombies, Sponges, Slabs, etc.). Could somebody please explain when a plural case can become a redirect, even if the singular case could be linked to when writing the plural case?--Madminecrafter12 ^{Talk • Contributions} 14:11, 11 February 2018 (UTC)

It's all about if the editor who cares about redirects saw the change in recent changes. As you can see, that project isn't really active, and while I'd go for the option #3 for redirect usefulness (no plurals at all, use pipe links instead) the consensus so far is keeping less regular plurals because they are actually useful for linking. Really, I think that this project could use some activity, I'm thinking about suggesting some categorization for redirects. Even a few templates keeping them in some nice categories like in WP:TMR would be useful, to be honest. --Hubry ^(talk) 16:48, 11 February 2018 (UTC)

Thanks for the info! For now I think I'm not going to make any plural links, but not mark existing ones for deletion, until it's more clear what the best option would be.--Madminecrafter12 ^{Talk • Contributions} 17:05, 11 February 2018 (UTC)

As far as I'm concerned, deleting these redirects is a waste of time; redirects are cheap, and there's no point to deleting redirects unless they're actually problematic (vandalism, preventing a pagemove, etc.) 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 10:39, 12 February 2018 (UTC)

...thanks for linking that, I think I am a bit deletion-happy in case of redirects and you are right. Though I still think the amount of redirects we have for some pages is slightly excessive, I will stop marking those for deletion. I think WP:CHEAP should probably be mentioned in the style guide. --Hubry ^(talk) 12:59, 12 February 2018 (UTC)

In my personal opinion, I see no big problem with having plural redirects, as like mentioned on WP:CHEAP, redirects take up very little space. Also, as a user, I've noticed that plural redirects seem to make searching easier - for example, the reason I created the redirect, Tutorials/Command blocks (it's now deleted), is because many times I would search for that, and I would have to take the time to search for the page Tutorials/Command block (which, admittedly, does not take much time, but I still think that a redirect here would be helpful here). On the Redirect Cleanup talk page, users have mentioned that part of the reason why plural redirects are unnecessary is because if somebody searched for a page of the plural case, the singular case is bound to come up first. But the thing is, the search system takes a second or so to register what is being typed, and that's after every letter, meaning that if a user searched in the search box at normal typing speed, the singular case page would not come up before they have fully typed the plural version of the page. However, if most of the community thinks that new plural redirects are unnecessary (which it currently seems like they do), I don't think it's necessarily worth it to have a huge discussion on it.--Madminecrafter12 ^{Talk • Contributions} 17:05, 11 February 2018 (UTC)

At minimum, I'd say redirects like Entities for Entity should be kept (as I'm not aware of a way to do [[Entit]]ies or something like that). I'd say though that more redirects for similar forms are useful though, for user use — e.g. I created ids a while back to redirect to the data values page because I didn't want to type the whole thing (mainly for entering right into the address bar, not searching, though it's useful for both). --Pokechu22 (talk) 16:21, 12 February 2018 (UTC)

Stripped Log

Something very strange is going on with the stripped log page. The whole toolbar is covering the page, and the history template is not working correctly. As for as I know, there is nothing I added that should cause this, so I'm not sure why this is happening.--Madminecrafter12^{Talk • Contributions} 23:48, 14 February 2018 (UTC)

There was a missing curly brace, so it wasn't transcluding the history footer. The resulting unclosed html tags cause major layout issues. -- Orthotope^talk 00:02, 15 February 2018 (UTC)

Great, thanks, I didn't even notice that was there.--

Madminecrafter12^{Talk • Contributions} 00:22, 15 February 2018 (UTC)

Sounds like this was a case for Minecraft Wiki:Projects/Cleanup open tags. However the unclosed tag was in a used template in this case as said above. If you check that project page, it'll give a thorough explanation on what happens and why, which may help you when you encounter a similar case in the future. The project should have covered all article pages already, but unfortunately the problem keeps happening if not everyone is aware of this. – Jack McKalling [

] 11:08, 19 February 2018 (UTC)

Complex turtle behavior?

In this article, Java edition developers mention some complex turtle behaviors that aren't already mentioned at Turtle#Behavior (such as turtles having a home beach). I'd add them to the turtle article but I'm not sure how some of them work. -EatingSilencerforBreakfast (talk) 21:56, 17 February 2018 (UTC)

I think it would be safe to mention that on the page, as it seems pretty clear that this is a fact. Many times it seems like Minecraft developers say something that is not a fact just to further describe the fact, but in the article it seems like it's written like it's true fact.--

Madminecrafter12^{Talk • Contributions} 14:15, 18 February 2018 (UTC)

I've added it to the article.--

Madminecrafter12^{Talk • Contributions} 14:39, 18 February 2018 (UTC)

Another wiki inconsistency

I found another wiki inconsistency and decided to post it here before I make any changes:

On some animal articles (specifically Horse, Pig, Sheep, Llama, and Rabbit), information about breeding is stored in their 'Behavior' section. However, in other animal articles, its stored under 'Spawning' (specifically Cow, Mooshroom, Chicken, and Ocelot). Wolf and Villager are different in that breeding is kept in a separate section of its own. For consistency, I say that breeding should be documented in a singular section across the entire wiki (all Breeding sections be under Behavior, for example).

-EatingSilencerforBreakfast (talk) 00:28, 27 February 2018 (UTC)

I would go with either a separate section or put it under Behavior. However, I would be fine with putting it under "Spawning," but I do agree that there needs to be one thing throughout. The style guide for features does not say anything about breeding, so once we come to a decision, we should make sure to put it in the style guide.--

Madminecrafter12^{Talk • Contributions} 00:47, 27 February 2018 (UTC)

I don't think the style guide prohibits you doing it one way or the other, and I'm not sure it fits better in Spawning or Behavior or on its own. I don't so much care which one we choose, I just agree it's good to pick one and be consistent. – Sealbudsman ^talk/_contr 03:02, 28 February 2018 (UTC)

Here is my proposal: how about we put the Breeding section under Behavior (because it's an animal behavior), but make a reference to it under Spawning (since new animals are spawned via Breeding). For example, in the Chicken article, information about Breeding would be under Chicken#Behavior, but under Chicken#Spawning we can put a sentence like: "Chickens can be spawned via breeding(links to breeding section under Behavior)." -EatingSilencerforBreakfast (talk) 23:19, 2 March 2018 (UTC)

Support. I like that idea.--

Madminecrafter12^{Talk • Contributions} 00:51, 3 March 2018 (UTC)

Support I like it. – Sealbudsman ^talk/_contr 03:46, 3 March 2018 (UTC)

Markus Persson/editcopy

I'm bringing up a topic that was discussed and archived at /Archive 16. I really think adding an editcopy for the Markus Persson page is necessary. If you look at the talk page, you'll notice that there are many edit requests from a long time ago that have not been implemented nor received any kind of response. Creating an editcopy would allow normal users to improve the article greatly, even if updating may not be necessary due to the fact that he's retired.-- Madminecrafter12^{T • C} 01:26, 8 March 2018 (UTC)

Alternatively, all of the article's protections can simply be removed (which I personally prefer). It doesn't seem to be a very tempting vandal magnet anymore. MarcelTheHippie (talk • contribs • logs • block log) 🐷🥕☮️ 01:48, 8 March 2018 (UTC)

It is true that this page was fully protected in early 2011, and the protection wasn't brought down at all since, so it may make sense to try semi-protection and see how it goes. However, I personally don't have any strong opinion on the protection, but I do think that if the protection stays so that only administrators can edit it, there should definitely be an editcopy.--

Madminecrafter12^{T • C} 01:52, 8 March 2018 (UTC)

Did these versions actually exist?

Following the recent rediscovery of Alpha 1.0.2 I've been in the process of adding evidence of existence of various versions from Alpha which are no longer available in the launcher. There is currently one remaining version which I am yet to find any proof for:

Alpha 1.0.14_01

I can't seem to find any particularly solid ground on this version's case. I've searched through various YouTube videos, but it appears to be elusive, and I'm not being too successful with finding sources on Notch's blog either. General googling also provides no relevant results, photographic or otherwise.

There's also a few versions that can be presumed to exist due to later patches, but don't have pages, and I have also had no success verifying:

Can anyone help provide proof (video, screenshot, blog post or otherwise) that any of these four versions existed? - MinecraftPhotos4U (talk) 14:35, 21 March 2018 (UTC)

I can provide some history from the wiki~~, which seems to show that it doesn't exist~~: a1.0.15 was added to version history in revision 13802 and included the changes given to a1.0.14_01. But it was put before multiplayer instead of after, so there were two a1.0.15 versions listed, and this was also an after-the-fact revision (dated 25 August 2010). (n.b. I bypassed the broken username in version history by just manually editing the date)

This was later converted into a table in revision 15910, and that changed the second a1.0.15 to a1.0.14 (probably by accident), so that there were two a1.0.14's listed; ~~this is also when it was given a release date of August 03 2010~~. This duplicate entry continues on for years, until the articles are split off in revision 212986. The alpha history was put here. And, it was eventually the unique _01 name in revision 370385 when Fenhl refactored the links in the article.

As one more point of evidence, check the history of Patch history. There is only Seecret Friday 7 (with the last edit on 31 July 2010) and Seecret Friday 8 on 20 August 2010. No a1.0.14_01. And, finally, it just doesn't make sense; the changes for a1.0.14_01 include "Can enter the IP for a server other than Mojang's server", yet a1.0.15 is supposed to be the version that introduced support for multiplayer.

~~Basically, it is pretty clear to me that this version doesn't actually exist, and all of the changes listed for it are actually part of a1.0.15~~. No comment for the other versions yet. --Pokechu22 (talk) 18:18, 21 March 2018 (UTC)

Alpha 1.0.14_01 doesn't exist, the only blog post that would be fitting belongs to Alpha 1.0.15. The post is mislabeled as Alpha 1.0.14 though, but comparing the dates of the jars and the timestamps of various blog posts it becomes clear that this one is indeed for Alpha 1.0.15. – Fuzs 19:26, 21 March 2018 (UTC)

On a similar topic, it seems as though the versions 0.30_01, 0.30_02 and 0.30_03, as listed in Version history/Classic, are all misnomers/conjectural; these were all called 0.30 in the page's initial revision, and looking at the corresponding blog posts on Word of Notch showed that they also shared the 0.30 title ingame. The situation with the 0.24 versions is identical. Does this affect any other versions? - MinecraftPhotos4U (talk) 18:58, 22 March 2018 (UTC)

I appear to have found the proof that Alpha 1.0.17_01 does indeed exist, as per here: https://i.imgur.com/SAkZp.png sourced from here: https://www.reddit.com/r/Minecraft/comments/d3fmt/double_tree_what_does_this_mean/ 44trent2 (talk) 08:14, 25 April 2018 (UTC)

added! There's one that can be crossed off of the list.

Now that we're also keeping track of Classic versions now, here's an updated list of conjectural versions:

And the "no-proof-so-they-might-as-well-be-fakes":

Classic 0.0.13a_02
Classic 0.0.13a_04
Classic 0.0.14a_01
Classic 0.0.16a
Alpha 1.0.17

Would this be better split off into its own project? - MinecraftPhotos4U (talk) 10:30, 25 April 2018 (UTC)

Probably, yes. – Nixinova

05:51, 26 April 2018 (UTC)

I'll get around to setting it up at somewhere along the lines of Minecraft Wiki:Projects/Proving missing versions sooner or later. - MinecraftPhotos4U (talk) 15:22, 5 May 2018 (UTC)

Image requests

These following images should be added:

An isometric (or dimetric, whatever) picture of Shipwrecks and Underwater ruins
An isometric render of Blue ice block

193.210.230.1 09:53, 31 March 2018 (UTC)

I have requested this on the community portal page.--

Madminecrafter12^{T • C} 16:36, 31 March 2018 (UTC)

Thanks! 193.210.230.1 16:55, 31 March 2018 (UTC)

Got it, comin' right up (maybe?) Twh minecrafter (talk) 00:09, 1 April 2018 (UTC)Twh_Minecrafter

Nope, just stupid commentary videos. (Maybe post those on the 1.13 page.) Twh minecrafter (talk) 00:12, 1 April 2018 (UTC)Twh_Minecrafter

Experimental gameplay or full implementation in Bedrock history

When a new feature is added to the Bedrock Edition in experimental gameplay, should we add it to history saying that that's when it first was implemented, or wait till full implementation and then do the same?-- Madminecrafter12^{Talk to me} 12:30, 5 April 2018 (UTC)

Well, I believe when the 1st build for 1.3 came out, they do just move the new features from Experimental Features. So, I guess the History section should note when it was first implemented. Skylord wars (talk) 12:42, 5 April 2018 (UTC)

Fish bucket article

I have attempted to create an article for fish buckets, here. -EatingSilencerforBreakfast (talk) 22:50, 5 April 2018 (UTC)

Support. Originally I had created that as a section of the fish (mob) article, for the purpose of being consistent with the water article, but I hold no objections at all to making it into a separate article, especially now that we have a lot more information.-- Madminecrafter12^{Talk to me} 23:02, 5 April 2018 (UTC)

Support – Sealbudsman ^talk/_contr 02:08, 6 April 2018 (UTC)

Best Homemade TNT Cannons

The TNT Cannons page is already long and flourished with random nerdology about them, but a real shortage of buildables at the bottom. I think if we all put in a little, we could help a lot of readers. Specifically, PVP Factions players (here you go, server owners.), redstone lovers, and, yes, griefers. (There you also go, server owners.) But not intentionally. I hate griefers just as much as you do. Enough about them.

They cannot be ideas from Youtubers unless you cite them. (SethBling, Mumbo Jumbo, etc.) Try to make your own super boss idea if you can. And don't feel discouraged if it's simple! The simpler, the easier it is for someone else it is to build. Just make it your best work! If you suck at all things redstone, or you don't want your idea here, then you might want to stay out. All cannon types excepted! So bring your T-Guns! Bring your shotguns of explosion-related death! And of course bring your trolly little sand cannons you launch at your little brother's house! And if you still want to help, though, then make a layer by layer blueprint like the ones in Structure Blueprints for the submitters. Here are the rules:

They have to launch TNT in a cannon-like fashion. No random placements and hope it flies somewhere. Also, don't be that one edit vandal to make yours show up first. I will find an admin, and I WILL make sure something bad happens to you in a Wiki-related way. It can shoot anything that can be shot from a cannon. (Arrows, players, good old pixelated TNT, and, heck, snowballs if you can find a way to. It won't matter to the future builder. (I'd build anything that can shoot snowballs! 😃) If you already have one, great, just edit it in to an appropriate place. Same with other submitters.

Twh minecrafter (talk) 23:48, 5 April 2018 (UTC)Twh_minecrafter

Individual articles for Classic versions

Should Version history/Classic be split up into individual pages for each version, similarly to what was done with Alpha? - MinecraftPhotos4U (talk) 21:33, 8 April 2018 (UTC)

I've put up an example at Classic 0.0.11a. - MinecraftPhotos4U (talk) 15:55, 9 April 2018 (UTC)

I'd say just go ahead. Some pages will be quite empty, but that's the same for Alpha already. Don't forget about Indev and Infdev, there's a lot wrong, but we can move the pages later. And see how you'll do Survival Test 0.24 and 0.26. I'd leave the dates in as previews from Notch, but it should be clear when an actual version was released and when not. – Fuzs 16:32, 9 April 2018 (UTC)

Support. I do think we should do the same with Indev and Infdev for consistency. I don't think we necessarily have to do this for Pre-classic though.-- Madminecrafter12^{Talk to me} 16:39, 9 April 2018 (UTC)

Reorganization of versions

This was mentioned a year ago at Minecraft Wiki talk:Style guide/Versions#Reorder sections, one person responded to it, and then it just kind of got abandoned for a year, despite the fact that it was mentioned as a RfC on the community portal page, until I responded to it. To make the discussion actually get somewhere instead of just get abandoned, it would be greatly appreciated if you could put in your opinion, regardless of what it is - either here or on the versions style guide talk page. Basically, we had kind of decided that it may be better if we put the blocks, items, mobs, and world gen higher on the page, and general at the bottom. More information can be found at Minecraft Wiki talk:Style guide/Versions#Reorder sections.-- Madminecrafter12^{Talk to me} 15:38, 9 April 2018 (UTC)

I Support moving those parts higher on the page.-EatingSilencerforBreakfast (talk) 16:59, 9 April 2018 (UTC)

So far there have only been supports and no opposes. Shall I add this to the style guide and start reorganizing?-- Madminecrafter12^{Talk to me} 17:05, 9 April 2018 (UTC)

It seem like a very reasonable comment period has been given. My instinct is that you are clear to do it. – Sealbudsman ^talk/_contr 18:01, 9 April 2018 (UTC)

I've added it to the style guide and am currently reorganizing the articles.-- Madminecrafter12^{Talk to me} 18:18, 9 April 2018 (UTC)

Brewing Overhaul

(More details here.) I've put together a new way of showing all the brewing recipes, in which all the information about one potion effect is on the same line, instead of scattered through two or three sections. Example (mixed potions):

Potion	Reagent, Base	Extended	Enhanced	Effects
Potion of the Turtle Master (1:00) ‌^{[upcoming: Lua error in Module:Version_link at line 112: attempt to concatenate local 'text' (a nil value).]}	Template:Grid/Brewing Stand	Potion of the Turtle Master (3:00) ‌^{[upcoming: Lua error in Module:Version_link at line 112: attempt to concatenate local 'text' (a nil value).]}	Potion of the Turtle Master (1:00) ‌^{[upcoming: Lua error in Module:Version_link at line 112: attempt to concatenate local 'text' (a nil value).]}	Slowness IV and Resistance IV (enhanced: Level VI effects)

I also have base potions, positive effect potions and negative effect potions ready to go (negative can be viewed at the brewing talk page), but due to the drastic departure from the current article, I would like to know if there is support for this before I make the change. - Princess Nightmoon (Talk Contributions) 17:14, 9 April 2018 (UTC)

I like this idea. Though the enhanced effects seem to be smooshed in there. I might suggest:

Potion	Reagent, Base	Effects	Extended	Enhanced
Potion of the Turtle Master (1:00) ‌^{[upcoming: Lua error in Module:Version_link at line 112: attempt to concatenate local 'text' (a nil value).]}	Template:Grid/Brewing Stand	Slowness IV Resistance IV Slows the player to 40% speed, incoming damage reduced to 20%.	Potion of the Turtle Master (3:00) ‌^{[upcoming: Lua error in Module:Version_link at line 112: attempt to concatenate local 'text' (a nil value).]}	Potion of the Turtle Master (1:00) ‌^{[upcoming: Lua error in Module:Version_link at line 112: attempt to concatenate local 'text' (a nil value).]}	Slowness VI Resistance VI Slows the player to 10% speed, all incoming damage fully reduced.
Potion of Poison ( 0:45)	Template:Grid/Brewing Stand	Poison 1 every 2.5 seconds.	Potion of Poison ( 2:00)	Potion of Poison ( 0:21)	Poison II 1 every 1.2 seconds.
Potion of Weakness ( 1:30)	Template:Grid/Brewing Stand	Weakness Reduces player's melee attacks by 4.	Potion of Weakness ( 4:00)	-	-
Potion of Harming	Template:Grid/Brewing Stand	Instant Damage Inflicts 6 of damage.	-	Potion of Harming	Instant Damage II Inflicts 12 × 6 of damage.

– Sealbudsman ^talk/_contr 18:35, 9 April 2018 (UTC)

Awesome. I like this, Princess Nightmoon's version is already so much better than the way it currently is, but I agree about the effects being better split between regular and extended version, so it can be spelt out fully. I especially like the addition of the duration, as it fits so snugly, and I like the place to mention the upcoming template. – Jack McKalling [

] 18:42, 9 April 2018 (UTC)

I can definitely work with that. While I do see your point, having two columns for effects instead of just one does make the text a bit more cramped (or, when there is no enhanced effect, wasted blank space). How about something like this instead:

Potion	Reagent, Base	Extended	Enhanced	Effects
Potion of the Turtle Master (1:00) ‌^{[upcoming: Lua error in Module:Version_link at line 112: attempt to concatenate local 'text' (a nil value).]}	Template:Grid/Brewing Stand	Potion of the Turtle Master (3:00) ‌^{[upcoming: Lua error in Module:Version_link at line 112: attempt to concatenate local 'text' (a nil value).]}	Potion of the Turtle Master (1:00) ‌^{[upcoming: Lua error in Module:Version_link at line 112: attempt to concatenate local 'text' (a nil value).]}	Slowness IV, Resistance IV Slows the player to 40% speed, incoming damage reduced to 20%. Enhanced: Slowness VI, Resistance VI Slows the player to 10% speed, all incoming damage fully reduced.

- Princess Nightmoon (Talk Contributions) 19:23, 9 April 2018 (UTC)

Ooh, good eye! – Sealbudsman ^talk/_contr 20:24, 9 April 2018 (UTC)

Easier to read I think. With the added bonus of being able to quickly compare the effect descriptions vertically, which is easier with the eye than horizontally. – Jack McKalling [

] 19:36, 9 April 2018 (UTC)

Applied overhauled system to article. - Princess Nightmoon (Talk Contributions) 23:37, 9 April 2018 (UTC)

Mob sounds

I noticed that there appears to be a weird inconsistency between mob sounds on this wiki. A lot of the mobs don't have the sounds they make in-game in their infobox, while others do.

This table is now at Minecraft Wiki:Projects/Upload Missing Wiki Sounds.

Would it be possible to obtain sound effects and put them on the wiki any of the above mobs that don't already have it?-EatingSilencerforBreakfast (talk) 21:27, 10 April 2018 (UTC)

I have already extracted all the 1.13 sound effects but they are currently in parts, i.e. idle1, idle2, idle3, ect.. it will probably take some time to sort through them all. I will keep a list here of the mobs i've added sounds for and update it as i add more.

jjlr (talk) 00:39, 11 April 2018 (UTC)

Can someone possibly make a project page for this please, i would myself but i'm really not that good at writing and struggled just trying to start the first paragraph describing the projects goals. If someone can just start it i can add most of the technical details, thank you in advance for anyone who helps. jjlr (talk) 10:43, 12 April 2018 (UTC)

Info I made a project page for this in a sandbox here, if i could get some opinions before i move to an actually project page it would be very helpful. jjlr (talk) 03:53, 17 April 2018 (UTC)

Looks good. It could go with a more in-depth explanation as to exactly what steps to make in the wikitext of an article, so even participants who just joined the wiki or otherwise just don't know, can also do it. When you move it to a subpage of Minecraft Wiki:Projects, and add a link to it with description there, others will probably help you edit the project page as well. Good project. – Jack McKalling [

] 07:38, 17 April 2018 (UTC)

Info I finished moving the project page for this and it is now at Minecraft Wiki:Projects/Upload Missing Wiki Sounds. jjlr (talk) 08:10, 17 April 2018 (UTC)

How to have sandbox moved to a new page

I have made a page for bedrock editions 1.2.20.1 and feel it can now be moved to a page, it still needs some changes but most i believe are minor and can be done after it is moved. jjlr (talk) 23:08, 10 April 2018 (UTC)

You can add {{Move}} to a page to suggest a rename. 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 00:07, 11 April 2018 (UTC)

Sorry i should have said, i found the move button and already moved it to it's own page. But thank you for your reply. jjlr (talk) 00:11, 11 April 2018 (UTC)

Dolphin

Is anyone currently working on a page for the dolphin? I was going to start one in a sandbox but if someone else already has then there is no need for me to make another. jjlr (talk) 00:19, 11 April 2018 (UTC)

bedrock beta 1.2.20.1

The navigation box for bedrock still needs to have 1.2.20.1 added, and the main page needs to be updated to reflect its release. jjlr (talk) 01:46, 11 April 2018 (UTC)

Jjlrjjlr It's a build, not a version, so it wouldn't need to be updated on the main page. It would be needed in the navigation box, but I honestly do not know what build 1.2.20.1 is or what version it's for. I asked on Slack, and was told that it was build 8, but I don't even know what version it's for (I asked).-- Madminecrafter12^{Talk to me} 01:53, 11 April 2018 (UTC)

Madminecrafter12 sorry the way bedrock versions are categorized makes very little sense to me, i exclusively play java edition so really have no experience with how they are released, but i trust that everything will eventually be worked out and thank you for the reply. jjlr (talk) 01:58, 11 April 2018 (UTC)

No need to apologize at all, and sorry if my reply seemed a little harsh. Honestly, the Bedrock Edition versions categorization makes very little sense to me too. Right now I'm honestly just waiting and seeing if any official Bedrock developers post anything that's helpful, or waiting on another user who knows stuff about the weird way Bedrock Edition builds are organized. Best regards, -- Madminecrafter12^{Talk to me} 02:06, 11 April 2018 (UTC)

Yo, I play Bedrock Edition, so ask me anything and I'll try to keep up to date on the latest builds. Twh minecrafter (talk) 12:58, 12 April 2018 (UTC)Twh_minecrafter

Row-sorting buttons on a new line

I've been asked by A20001017 to consider putting table sort buttons into a separate row, in Module:LootChest. For reference, see Help:Sorting#In_a_narrow_space:_sorting_buttons_in_a_separate_row. Do people have any opinions either way? – Sealbudsman talk | contribs 16:01, 11 April 2018 (UTC)

Question I'm not a fan of the empty cells. Would it be practical to infer the viewport width and only do this when necessary? If not, I'd still support doing it because I think usability should trump aesthetics. – Auldrick (talk · contribs) 16:21, 11 April 2018 (UTC)

Yes you can easily use styling to move the arrow (background-position:center bottom 6px; padding-bottom:2.2ex; padding-right:0.4em[1]), but basing it on the viewport width doesn't necessarily work, as when you want to move the arrow is more dependent on the width of the table, not the viewport. If the table is not very wide, it's not necessary to move the arrow until the viewport is quite small, whereas if the table is very wide, you might just always want the arrow below. To have it work generally for any table of any size, you'd need JS. –Majr ᐸ Talk
Contribs 03:04, 12 April 2018 (UTC)

Thanks. These help. a20001017^Talk 09:21, 13 April 2018 (UTC)

Entity sprite creation

Can anyone please explain to me how the entity sprites are created, i was going to create the sprite for the dolphin but can't seem to figure out how they are made. jjlr (talk) 06:19, 12 April 2018 (UTC)

I think what people are doing is taking the mob's skin and starting from there.

P.S. If you are using the Java edition, go into .minecraft/versions/18w15a, you will see the jar file. Unzip / extract that. Then go into assets/resource packs/ and there is probably a skins folder, an entity folder, then a dolphin folder. – Sealbudsman talk | contribs 11:57, 12 April 2018 (UTC)

Dolphin texture exactly is in assets/minecraft/textures/entity/Dolphin.png : ) Oakar567 (talk) 12:04, 12 April 2018 (UTC)

Question regarding the Entities template

I'm an editor on the Hungarian Wiki and I'd like to ask where does the Entities template take the small pictures for each entity from? david92003 (talk) 18:53, 12 April 2018 (UTC)

David92003, it uses the {{EntityLink}} template, which data is stored at Module:EntitySprite, using Module:Sprite.-- Madminecrafter12^{Talk to me} 19:20, 12 April 2018 (UTC)

OK, thanks! david92003 (talk) 09:55, 13 April 2018 (UTC)

Inventory Slot Aliases

I've noticed that the potions section in Module:Inventory_slot/Aliases, where the effect text is added to the info overlay when you hover over the item is technically very lacking in content, despite its length. There are 30 entries (potions/arrows with no effect, decay and night vision + its extended variants), with 170 missing (all other effects) - less if we ignore certain variants that aren't really displayed on the wiki. However, since it's such a massive amount, I was wondering if they should be moved to a secondary alias module specifically for potions, or just get added to the existing module? - Princess Nightmoon (Talk Contributions) 23:47, 12 April 2018 (UTC)

Definitely excited to see someone's interested in finishing that. And, no reason it can't be all in one module. There are much bigger modules. – Sealbudsman talk | contribs 00:56, 13 April 2018 (UTC)

Texture update

Since there doesn't appear to be a page for the "Texture update", would anyone have any objections to me starting one? jjlr (talk) 00:13, 13 April 2018 (UTC)

There currently is Planned versions § Texture Update, but it's very sparse. I'm not completely sure whether it should be a separate page, but I don't object to it. --Pokechu22 (talk) 00:22, 13 April 2018 (UTC)

@Pokechu22: i know about the section in planned versions but i was thinking of moving it to it's own page, and also having more of a list with all the changed texture and a render of them to make it easier to see the differences between the new and current textures. jjlr (talk) 00:28, 13 April 2018 (UTC)

Jjlrjjlr, ooh, that's actually a good idea. It seems like as soon as it is revealed what content will be added in an update, a separate page is created for that update, and considering we know exactly what will be changed in the Texture Update, it seems like a separate page would be helpful and necessary. I Support this, but I personally recommend waiting for maybe 1 or 2 more users to see this and reply to it, and then create it.-- Madminecrafter12^{Talk to me} 00:48, 13 April 2018 (UTC)

@Madminecrafter12: I started the page in a sandbox so i have it ready but i do plan on waiting for a few more people, and thank you for the support. jjlr (talk) 00:50, 13 April 2018 (UTC)

Support! – Sealbudsman talk | contribs 00:53, 13 April 2018 (UTC)

Support, the update is coming closer, we better get started.--Skylord wars (talk) 01:48, 13 April 2018 (UTC)

I'm already working on block renders and have started a page in a sandbox but if anyone can start on the items and mobs i would really appreciate it. jjlr (talk) 01:52, 13 April 2018 (UTC)

Jjlrjjlr, why don't you just go ahead and move it to the title, "Texture Update," add {{WipNeedHelp}} to the top of the page, and editors (such as me) will be happy to finish the content.-- Madminecrafter12^{Talk to me} 02:02, 13 April 2018 (UTC)

Madminecrafter12 Just one problem, because of the redirect i don't have permission to move the page to "Texture Update". jjlr (talk) 02:22, 13 April 2018 (UTC)

Oh, yep you're right, I didn't even think of that - yeah, that's definitely going to be a pain :(... I'll ask an administrator to delete the page.-- Madminecrafter12^{Talk to me} 02:26, 13 April 2018 (UTC)

Madminecrafter12 Let me know when it gets deleted and i'll move the page, until then i'll finish the block renders (up to 68 finished now) and begin uploading them. jjlr (talk) 02:31, 13 April 2018 (UTC)

Jjlrjjlr, I'm gonna be away from the computer for the rest of the night, but you can check recent changes, which will show the deletion log, so once you see that the texture update page has been deleted, you can move your sandbox page to that title.

Incase anyone is interested i still need renders done for all the mobs that had their textures changed. jjlr (talk) 10:31, 13 April 2018 (UTC)

Update Videos

Hi there! I'm here to propose a small addition to the Minecraft updates changelogs. I've did this with a few, but it got retired because I didn't talked about it with you here. So what I'm thinking about is that we could add a "Video" section to the changelogs, featuring slicedlime's videos, which features every snapshots with the smallest details. To implement that, we could add a category named "Update_videos" that itself got the already existing Video Category. Then, on each changelog we could add a subpage named "/Update_video" which feature the corresponding video made by slicedlime, categorized "Update_videos". Then, back to the changelog, we could add the "Video" section with only {{/Update_video}}. And yeah that's all I wanted to ask you, do you think it's a good idea or not and why? Hugman 76 (talk) 08:16, 14 April 2018 (UTC)

To clarify: currently, the video policy only allows for using videos uploaded by Curse, which is problematic given there are several official or developer channels which would be useful (and, unless I'm mistaken, there are already cases of videos from some of these channels being used - e.g. all the MineCon videos are uploaded on Mojang's account). The proposal is to expand the video policy to allow for using videos from these sources as well (videos themselves would be added via /video subpages, as has always been done with Curse videos, though I have no problem with the proposed categorization). One of the things we need before we can implement this (in addition to community support, which I'd be very surprised not to have), though, is a list of known channels and, potentially, some detail on what videos are appropriate to use in which circumstances. (Lastly, I might as well explicitly state I support this proposal, given I'm commenting on it like this.) 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 08:37, 14 April 2018 (UTC)

@Dinoguy1000: would it be useful if i made a short list of channels along with what content they post? jjlr (talk) 08:42, 14 April 2018 (UTC)

The policy should definitely allow for relevant informational videos uploaded by Mojang staff to be included in applicable articles, in my opinion. Slicedlime's update videos in particular would be very useful on the update version articles. - Princess Nightmoon (Talk Contributions) 08:52, 14 April 2018 (UTC)

I'm going to work on a sandbox at the moment to show you how it can render. Hugman_76 [

] 13:54, 14 April 2018 (UTC)

I've done it! Check it here. Hugman_76 [

] 15:24, 18 April 2018 (UTC)

I think we should petition Curse for this. Dinoguy, you said there are many useful channels. I argue that it would make the Wiki much more useful if we add videos in from more sources. If everyone is diligent with citations, it shouldn't be an issue. Plus, common page patrollers would do a good job making sure videos are cited correctly. I agree with everyone about updating the policy somehow. Twh minecrafter (talk) 15:48, 14 April 2018 (UTC)Twh_minecrafter

Having a list of channels would be a great starting point, yes. For personal channels of developers/staff, it would also be useful to show what sort of content they generally upload. 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 12:25, 15 April 2018 (UTC)

Older item images

Would anyone mind if i uploaded new versions of some of the item images, i have been noticing that alot of them are cropped and it's making it difficult to display them next to the new textures on the Texture Update page. jjlr (talk) 02:49, 15 April 2018 (UTC)

That cropping has always bothered me, I support it. – Sealbudsman talk | contribs 05:33, 15 April 2018 (UTC)

Support - Hugman_76 [

] 08:18, 15 April 2018 (UTC)

Beginners Guide Rewrite Notice

Hello there, everybody! I just checked the members of the Minecraft Wiki:Projects/BGR, and most of them have not been active for years, so I would like to send a notice to everyone out there about possibly joining! If you want to join a project, then there are opportunities here. The project has been moving at crawl speed for about 2 years. There are still some pages that could use some work. Anyone can join! Just edit your name in on the list at the link I put earlier. Twh minecrafter (talk) 00:32, 17 April 2018 (UTC)

Remember that a proper tutorial for beginners is possibly the MOST important tutorial on this wiki. Don't be afraid to add your name and start editing the tutorial pages. If you have questions, ask. Just don't do nothing!

-SuperDyl19 (talk) 03:42, 17 April 2018 (UTC)

links in msgbox

~~Does anyone know how to use external links in a msgbox? i have tried everything and it keeps showing up as plain text or showing the url.~~ jjlr (talk) 03:46, 17 April 2018 (UTC)

Nevermind i finally got it working. jjlr (talk) 04:18, 17 April 2018 (UTC)

Creating empty/contentless pages

Please stop creating new pages that are functionally empty (e.g. they only contain maintenance tags such as {{Stub}} or text such as "Foobar is a block.") Such pages are useless to readers; because links to these pages become blue, readers are misled into thinking there is useful content on these pages. This practice is especially useless if you create a page in this manner and then immediately turn around and edit the page with useful content. If this continues, lI'm going to start handing out blocks over it. 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 14:26, 18 April 2018 (UTC)

Yes! Several chemistry-related pages were created in this way, which was bothersome. Others (the 4 utility blocks) were created with useful text, except it was copied directly from the education edition website, which is also not wanted. - Princess Nightmoon (Talk Contributions) 15:17, 18 April 2018 (UTC)

I've also noticed this for snapshot pages. For example, there will be a tweet that "a snapshot may come out later today," and somebody will create that as soon as the tweet is posted, with the only content being "Dinnerbone tweeted that a snapshot will come out today." I understand that it's exciting when this happens, but there really is no reason to rush. I have complete trust that editors will create the snapshot page within 5 seconds of its release (I mean, literately).-- Madminecrafter12^{Talk to me} 15:22, 18 April 2018 (UTC)

Yeah, this is a problem I've noticed happening for a while. The creation of contentless stubs for the various Classic versions is what finally spurred me to comment on it, though. 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 15:24, 18 April 2018 (UTC)

I'd say there are two cases here. One would be creating the articles, and marking them all as {{In use}} so that two people don't work on making it at the same time. In my opinion, that's fine (though the template should probably be used for that case). Another would be just creating an article where the subject doesn't even exist yet (e.g. future snapshots) and the article couldn't be written. That's a case where I would say it's a problem. --Pokechu22 (talk) 16:16, 18 April 2018 (UTC)

If someone wants to work on an article like that, they need to do it in their userspace and then move it to the mainspace when it's ready to go. Trying to prevent duplication of effort is not a valid reason to create empty/contentless pages. 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 23:26, 18 April 2018 (UTC)

MinecraftPhotos4U, please read this section, and note that in the future, reverting edits that change empty/contentless pages to redirects will result in a block. 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 23:26, 18 April 2018 (UTC)

After checking those edits, I was mistaken about what you did. However, in the future if you properly create a page from an edit revert, please replace or delete the edit summary before saving so your edit isn't listed as a revert in the page history. 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 23:32, 18 April 2018 (UTC)

Play dashtm, please read this section. 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 22:31, 23 April 2018 (UTC)

So, what is the community consensus here? Should we not create snapshot pages until they have been released unless there is significant coverage over the features that will be added in a source? Jjlrjjlr created 18w19a before it was released, and MinecraftPhotos4U created 18w19b, as it's expected to be released tomorrow (both of these users did it out of good faith). Whatever decision we make should probably be mentioned in the style guide. I personally like the idea of not creating any unreleased snapshot pages unless several of their features are mentioned in a source (kind of like how it currently is with version releases), but I'm open to anything. What do the rest of you think?-- Madminecrafter12^{Talk to me} 00:45, 9 May 2018 (UTC)

Redirects to all versions

As an example, the Java Edition has 1.2.1, while the Bedrock has 1.2 instead. But the page 1.2 redirects you to the 1.2.1 instead of the Bedrock 1.2. Should redirect pages like this be redirected to the correct one? Skylord wars (talk) 14:46, 18 April 2018 (UTC)

I think partial version notation pages like that are too ambiguous for a redirect. Maybe turn them in disambiguation pages so the reader can choose what they intended to look for, and then link to the correct version from articles instead of to these pages. So in this case 1.2 could disambiguate between Bedrock Edition 1.2 and 1.2.1. Using a redirect is so confusing here, whereas it is just 2 characters more to spell out in a link if you're trying to point to 1.2.1. – Jack McKalling [

] 14:54, 18 April 2018 (UTC)

At the very least, the targets of ambiguous redirects should have a {{Redirect}} hatnote pointing to the other page(s) a reader might have been trying to reach by following the redirect. The hatnote would be the preferred method for cases where there's only a couple such pages (the target and one other page, that is); for more, I agree with Jack in recommending a dabpage instead (though the hatnote should still be fine even for cases of three or four pages). 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 15:05, 18 April 2018 (UTC)

Is this what you're thinking?-- Madminecrafter12^{Talk to me} 15:11, 18 April 2018 (UTC)

Yep, good to see I'm still able to get my point across mid-ramble. =D 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 15:21, 18 April 2018 (UTC)

This is better since some players would just type 1.2 to search for 1.2.1. Skylord wars (talk) 15:23, 18 April 2018 (UTC)

The infobox automatically shows links to other editions with the same version number for exactly this reason, so I don't think we need the redirect template duplicating this. I think disambiguating would be better, and provides further reason to move all the unprefixed version pages to have the Java Edition prefix. –Majr ᐸ Talk
Contribs 10:35, 19 April 2018 (UTC)

The infobox for Bedrock Edition have links to Pocket Edition release. As an example, if you go to Bedrock Edition 1.2, there will be links to Pocket Edition 1.2, which redirects you to the same page. I currently can't think of anyway to fix it. Can anyone help? Skylord wars (talk) 11:18, 19 April 2018 (UTC)

It just checks if the page exists, it doesn't know if it's a redirect or not, nor is there a way to check without moving the check to lua. It can instead be written manually, but this obviously isn't a solution if all of them are doing it. Probably just remove the check for Pocket Edition pages on Bedrock pages, and once we've moved all the old Pocket Edition pages, the check can go entirely. –Majr ᐸ Talk
Contribs 06:47, 21 April 2018 (UTC)

Yeah, the best way to fix it is to remove the checks for Pocket Edition on Bedrock Edition pages. Skylord wars (talk) 06:53, 21 April 2018 (UTC)

I have a question.

How do I change the user name of the mcwiki? Beans1512 (talk) 05:18, 21 April 2018 (UTC)

This question is rather frequently asked. See User talk:Dinoguy1000/Archive 5#Changing username for an example of an answer. I think it still holds. --AttemptToCallNil (report bug, view backtrace) 05:27, 21 April 2018 (UTC)

Thank you very mush :) --Beans1512 (talk) 05:29, 21 April 2018 (UTC)

Fill in the form at https://gamepedia.zendesk.com/hc/en-us/requests/new?ticket_form_id=235968 using the email address associated with your account. (gphelp:Rename account) –Majr ᐸ Talk
Contribs 06:29, 21 April 2018 (UTC)

Removed wip

{{Wip}} instructs that no users edit the page until the work-in-progress state is finished. What are the guidelines as to when this can be removed? I assume it can be removed on pages such as Tutorials/Morse code, in which the author of the page hasn't edited in 7 years and the person who added the template hasn't edited in 5 years.-- Madminecrafter12^{Talk to me} 14:52, 21 April 2018 (UTC)

wikipedia:Template:Under construction, which serves a similar purpose, says to remove it if the page has not been edited in several days. Its more short term equivalent, wikipedia:Template:In use, says to remove the template if the page has not been edited in several hours. I'd say seven years without major edits is more than a definite sign the page is not a "work in progress". --AttemptToCallNil (report bug, view backtrace) 14:59, 21 April 2018 (UTC)

Work in progress notices should always be taken to mean work is actively being done; anything tagged with no activity for more than maybe a week or so should be untagged. If the tagger returns and wants to resume work, there is nothing stopping them, regardless of whether they readd the tag (though if someone repeatedly readds a wip tag without ever actually editing the page's content, they should have the tag's intended purpose explained to them). 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 15:17, 21 April 2018 (UTC)

Update Videos (up)

Are you guys still ok with this? Hugman_76 [ ] 14:39, 22 April 2018 (UTC)

I personally am fine with it, and it seems like many other users are too. Dinoguy1000, Orthotope? Would you be okay with doing this?-- Madminecrafter12^{Talk to me} 14:51, 22 April 2018 (UTC)

I'm fine with whatever the community consensus is. (Personally, I'd rather read a well-written article than watch a video, but that's mostly because I can read a lot faster than most people talk.) However, as Dinoguy repeatedly mentioned, we need a list of Mojang/developer channels to add to the video policy before this can be implemented. -- Orthotope^talk 16:43, 22 April 2018 (UTC)

Currently, there are only Help:Official sources#Video hosting services.~~The only YouTube channel there is TeamMojang. We should start making a section about official YouTube accounts other than Mojang's.~~--Skylord wars (talk) 01:06, 23 April 2018 (UTC)

I've saw that slicelime was added, could we start now? Or do we need another seperate page Orthotope? Hugman_76 [

] 18:54, 23 April 2018 (UTC)

The help page is probably the ideal location for the list to go, and the video policy should be updated to point to it instead of maintaining a separate list. 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 22:03, 23 April 2018 (UTC)

Alright, can we start now Dinoguy1000, Orthotope, Skylord wars, Madminecrafter12? Hugman_76 [

] 15:10, 30 April 2018 (UTC)

Works for me, especially because it's now been added to the Help:Official sources page. However, should we update the video policy page as well before we do this?-- Madminecrafter12^{Talk to me} 15:22, 30 April 2018 (UTC)

The Minecraft Wiki:Wiki rules/Video policy can be easily changed, as it's copied from Terraria wiki. Minecraft Wiki can set up their own rules. The video policy should be updated. Skylord wars (talk) 15:33, 30 April 2018 (UTC)

I don't know how to do it, can someone do it? Hugman_76 [

] 21:38, 1 May 2018 (UTC)

Only admins can edit the page, and none of the admins you've pinged have replied yet. I guess we can wait a week or so, and then I'll try contacting one of the active admins directly.-- Madminecrafter12^{Talk to me} 21:43, 1 May 2018 (UTC)

I've made the change, though I welcome suggestions for improvements to the text there (not just my text, but any of the text on the page, most of which I didn't look very closely at while editing). 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 07:35, 2 May 2018 (UTC)

So, may we start adding update videos by slicedlime? Dinoguy1000?-- Madminecrafter12^{Talk to me} 02:39, 6 May 2018 (UTC)

I think so, I'm going to start, a template is available here. Hugman_76 [

] 17:22, 9 May 2018 (UTC)

Question So to clarify, it is ok to start adding slicedlime videos to update pages now? jjlr (talk) 05:49, 10 May 2018 (UTC)

Yes! Make sure to all follow the same template (which can be found on 'Category:Update_videos' too) to not be confused. Hugman_76 [

] 08:38, 10 May 2018 (UTC)

You can't use subpage transclusion as the snapshot pages are transcluded on the development versions subpages, which points the video transclusion to a subpage of that page, which obviously doesn't exist. –Majr ᐸ Talk
Contribs 10:17, 10 May 2018 (UTC)

{{/Update_Video}}

doesn't work, but

{{:{{subst:PAGENAME}}/Update_Video}}

fixes the issue. Applied fix to existing pages and altered the instructions on the category page. - Princess Nightmoon (Talk Contributions) 12:58, 10 May 2018 (UTC)

Template to link to feedback.minecraft.net

Currently, there is {{Article}}. Well, I know this template can be used to link you to feedback.minecraft.net. But, can we make one for feedback.minecraft.net, or maybe use the same template.--Skylord wars (talk) 14:32, 24 April 2018 (UTC)

~~Working on it now~~.-- Madminecrafter12^{Talk to me} 14:59, 24 April 2018 (UTC)

Wait, never mind, it's already incorporated into Template:Article. Use the ext= parameter to go to a URL that is not minecraft.net.-- Madminecrafter12^{Talk to me} 15:02, 24 April 2018 (UTC)

Version release dates

I've noticed some confusion over the exact release date of various versions; in particular, whether certain versions were actually released the previous or next day from what's listed. It seems to me a lot of this confusion is likely to stem from time zones; Sweden is UTC+2, whereas many readers and editors are in the US, which is UTC-5 through UTC-10. In addition, it's not unusual for timestamps to be stored in UTC and adjusted for the viewer's local time zone on the fly, which means e.g. when viewing timestamps in text files, they won't be adjusted. This should definitely be kept in mind in the future wen considering what day a version was released on, since e.g. it may have been released after midnight Swedish time, but before midnight UTC, which would result in various sources and/or interpretations assigning two different release dates. 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 17:03, 25 April 2018 (UTC)

Most wiki use the following way. Times should be according to the main place. Such as Minecon 2016 should be based on California's time zone. There are currently two ways. These examples are random times. Either: 21:00 British Summer Time (UTC+1) on 27 July 2018/
8 p.m. Eastern Standard Time on January 15, 2001 (01:00 UTC, January 16)

On the Alpha versions, since Notch released them at midnight Sweden time (according to version_manifest.json), I've been using the UTC time with an explanatory footnote. – Nixinova

07:15, 28 April 2018 (UTC)

The wiki's style guide currently does not include a time zone guide. This should be added. Skylord wars (talk) 07:11, 28 April 2018 (UTC)

Yep, the .jar files has clearly written the time for it.--Skylord wars (talk) 07:24, 28 April 2018 (UTC)

PD licensing templates

Is there any practical difference between the CC0 and the Public Domain license? Just asking, because I'm implementing them on the Hungarian wiki... david92003 (talk) 17:42, 25 April 2018 (UTC)

CC0 should only be used for files that are explicitly licensed as CC0; PD can be used for any public-domain files, including ones licensed as CC0 (though I'd recommend using the more specific template whenever possible). 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 18:11, 25 April 2018 (UTC)

Thank you! david92003 (talk) 10:27, 26 April 2018 (UTC)

The Classic is a mess right now

The version history, classic pages, and everything related is really a mess right now and I can't figure out how to fix it. First of all, on the Java Edition version history page, it says that there is a version called 0.26 SURVIVAL TEST that was released on October 25, 2009. However, on the Classic 0.26 SURVIVAL TEST page itself, it says it was released on October 20? Furthermore, there are a ton of double redirects that redirect to versions that are not listed on the version history page, and some of these versions show up on the Classic 0.26 page, but are not listed anywhere else. And the 0.26 SURVIVAL TEST page does not have anything to do with any of the updates listed on the 0.26 page. Does anybody have any ideas of how this can be fixed?-- Madminecrafter12^{Talk to me} 15:20, 26 April 2018 (UTC)

The versions on the Classic 0.26 page weren't released to the public, 0.26 SURVIVAL TEST was. - MinecraftPhotos4U (talk) 15:59, 26 April 2018 (UTC)

Bedrock Beta versions

So, ever since the 1.2.13 betas, the version numbers have gotten pretty weird, and at the top of the weirdness is the recent Beta 1.5.0.0, the ninth beta version leading up to full version 1.4. Attempted breakdown as follows (numbers in brackets are full version numbers):

Full Version	Beta Builds	Update Aquatic
1.2.13 (1.2.13.54)	1.2.13.5	N/A
	1.2.13.6	N/A
	1.2.13.8	Build 1
	1.2.13.10	Build 2
	1.2.13.11	Build 3
	1.2.13.12	Build 4
1.2.14 (iOS)	1.2.14.2	Build 5
1.2.14 (iOS)	1.2.14.3	Build 6
1.2.15 (iOS) (1.2.15.01)	N/A	N/A
1.2.16 (iOS) (1.2.16.3) Non-iOS: 1.2.13.60	N/A	N/A
Future Versions	1.2.20.1	Build 7
	1.2.20.2	Build 8
	1.5.0.0	Build 9

Now, the article for Beta 1.5.0.0 is currently called "1.4 build 10", which is false, since it's the 9th build for 1.4 (Update Aquatic). And unlike previous numbers, it doesn't make sense for it to be "1.5 build 1", since it's not a build for 1.5. So, should it just be called "Beta 1.5.0.0"? Should the naming system be changed for the beta versions? I'm not really sure what to do here. - Princess Nightmoon (Talk Contributions) 21:05, 26 April 2018 (UTC)

To be honest I have no idea what to do, I've been wondering the same thing! For 1.2.14, builds for it added update Aquatic features, but then the iOS release of it only had bug fixes. Also, the order of the builds doesn't make sense at all, and it seems like some of the Wiki, such as the bedrock Edition version template, regards all of the builds as "1.4." Anybody else have any ideas?-- Madminecrafter12^{Talk to me} 21:14, 26 April 2018 (UTC)

Yeah, out of the beta versions listed, only 1.2.13.5-6 have actually been related to the version number. 1.2.13.8 and later have all been Update Aquatic betas, with no correlation to the full versions 1.2.13 or 1.2.14 despite sharing version numbers. As briefly touched upon, naming them "Beta [number]" could be a potential solution for the 9 builds in question, but it would need consensus. - Princess Nightmoon (Talk Contributions) 21:33, 26 April 2018 (UTC)

Looks like it's better if we named the version articles like "Beta [version number]". I'd consider "Update Aquatic Build [N]", but build numbers seem unreliable, judging by the 9/10 confusion, and this naming method will fail if the builds for the next major update become similarly confusingly versioned before the update's name is announced. If things get worse, we may have to resort to version release dates... but then again, nothing prevents the developers from "accidentally" releasing two or more updates on the same day in an ambiguous order. --AttemptToCallNil (report bug, view backtrace) 10:33, 27 April 2018 (UTC)

My suggestion is "Bedrock Edition Beta 1.2.6" for Bedrock Edition 1.2.6 build 1. Using this way will prevent confusion and make it a lot easier. We don't need to version numbers and update names. This is to keep consistent with Java Edition's snapshots articles. The name does not have the update name. Plus, builds are names used by Android betas only, Mojang uses the term Beta instead of builds.--Skylord wars (talk) 11:33, 27 April 2018 (UTC)

This is going to be confusing with the way we've historically treated the terms alpha/beta: as being an entire set of versions that come prior to the initial 1.0 release (just look at how {{history}} is organised). You might expect that BE Alpha 1.0 precedes BE Beta 1.1, but there's actually release versions in between. If we do this, we're going to have to make sure the infobox clearly differentiates between pre-release alpha versions, and mid-release beta versions. –Majr ᐸ Talk
Contribs 11:49, 27 April 2018 (UTC)

Well, that only applies to Java. While it might be confusing, it is accurate; Bedrock Edition uses Beta versions as their equivalent of Java snapshots (as of Beta 1.2.13.8), introducing experimental features which may or may not be included in the full version. Display methods in templates could be as follows:

Infobox (Beta 1.5.0.0)
"Type" indicates that it's a beta (snapshot) version, "Beta version for" indicates which version it's a beta for.

History (dolphin)
For this one, "beta [version number]" is used in the same way as snapshots, being listed under the upcoming version they are a beta for.

release
November 18, 2017		Dolphins were shown in a video clip during MineCon Earth
upcoming
1.13 {{Extension DPL}}<ul><li>[[:Category:Plants\|Category:Plants]]<br/>All pages covering blocks of such things as tall grass and flowers. [[Category:Blocks]] [[Category:Items]] [[cs:Kategorie:Rostliny]] [[es:Categoría:Plantas]] [[fr:Catégorie:Plante]] [[hu:Kategória:Növények]] [[it:Categoria:Piante]] [[ja:カテゴリ:植物]] [[ko:분류:식물]] [[nl:Categorie:Planten]] [[pl:Kategoria:Rośliny]] [[pt:Categoria:Plantas]] [[ru:Категория:Растения]] [[th:หมวดหมู่:พืช]] [[zh:Category:植物]]</li><li>[[Raw Cod\|Raw Cod]]<br/>{{about\|the item\|the mob\|Cod}} {{redirect\|Raw Fish\|raw salmon\|Raw Salmon\|pufferfish\|Pufferfish (item)\|tropical fish/clownfish\|Tropical fish (item)}} {{Item \| image = Raw Cod.png \| renewable = Yes \| heals = {{hunger\|2}} \| stackable = Yes (64) }} '''Raw cod''' is a [[food]] item that can be eaten by the player or cooked to make [[cooked cod]]. == Obtaining == === Mob loot === ==== Cod ==== [[Cod]] always drops 1 raw cod when killed, unaffected by Looting.<ref>{{bug\|MC-212795\|\|Salmon & Fish mobs are not affected by Looting}}</ref> If it is killed while on [[fire]], it drops 1 [[cooked cod]] instead. ==== Dolphins ==== When killed, [[Dolphin\|dolphins]] drop 0–1 raw cod. The maximum amount is increased by 1 per level of [[Looting]], for a maximum of 0-4 with Looting III. If killed while on fire, they drop cooked cod instead. ==== Guardians and elder guardians ==== [[Guardian]]s and [[elder guardian]]s have a 40% and 50% chance, respectively, to drop raw cod when killed. {{IN\|java}}, cooked cod is dropped if a guardian is on fire when killed. Guardians and elder guardians also have a 2.5% chance to drop a random fish, with 60% of them being raw cod, which drops as cooked if the guardian was on fire. The chance of getting the fish drop is increased by 1% per level with [[Looting]] (for a maximum of 5.5% with Looting III), but the type of fish is not affected. ==== Polar bears ==== [[Polar bear]]s have a 75% chance of dropping 0–2 raw cod when killed. The maximum amount can be increased by 1 per level of Looting, for a maximum of 0-5 with Looting III. If killed while on fire, they drop cooked cod instead. === Fishing === {{main\|Fishing}} Raw cod can be obtained from fishing. The wait time of one being caught is decreased with the [[Lure]] enchantment and the chance of one being caught is slightly decreased with the [[Luck of the Sea]] enchantment (named as such because it increases treasure, not fish). Catching cod awards 1-6 experience. === Natural generation === {{el\|java}}{{LootChestItem\|raw-cod}} === Villager gifts === {{in\|java}}, fisherman [[villager]]<nowiki/>s throw raw cod at [[player]]s under the [[Hero of the Village]] effect. == Usage == === Smelting ingredient === {{smelting \|Raw Cod \|Cooked Cod \|0.35 }} === Food === Raw cod restores {{hunger\|2}} [[hunger]] and 0.4 [[Hunger#Mechanics\|saturation]]. === Cats === Raw cod can be used to tame [[cat]]s with {{frac\|1\|3}} chance of success, get cats off of [[chest]]s, and [[bed]]s, [[breed]] cats, and make baby cats grow up faster by 10% of the remaining time. Additionally, raw cod can be used to heal cats by {{hp\|2\|mob=1}}. Raw cod can be used to gain [[ocelot]] trust, breed ocelots, and make baby ocelots grow up by 10%. === Dolphins === [[Dolphin]]s can be fed raw cod. Doing this improves their trust and interaction with the player. However, unlike most animals, feeding dolphins does not allow them to breed. When a player feeds raw cod to a dolphin, it swims toward the nearest chest in an [[underwater ruins]] or [[shipwreck]]. If the chest in the nearest structure is broken, they swim to the next nearest structure that has a chest. ===Trading=== Fisherman villagers have 50% chance to sell 6 cooked cod for 6 raw cod and 1 [[emerald]] as part of their first tier trade. Apprentice-level fisherman villagers have a {{frac\|2\|3}} chance to buy 15 raw cod for an emerald in Java Edition, and always offer the same trade in Bedrock Edition. === Wolves === {{IN\|bedrock}}, raw cod can be used to feed [[wolves]], to heal them by {{hp\|2\|mob=1}}. However, unlike other meat items, raw cod cannot be used to speed up the growth of baby wolves nor used to breed them, thus making it only feedable when wolves are not at full health. ==Sounds== {{Sound table/Entity/Food}} == Data values == === ID === {{edition\|java}}: {{ID table \|edition=java \|showitemtags=y \|showforms=y \|generatetranslationkeys=y \|displayname=Raw Cod \|spritetype=item \|nameid=cod \|itemtags=fishes \|form=item \|foot=1}} {{edition\|bedrock}}: {{ID table \|edition=bedrock \|shownumericids=y \|showforms=y \|showaliasids=y \|notshowbeitemforms=y \|generatetranslationkeys=y \|displayname=Raw Cod \|spritetype=item \|nameid=cod \|aliasid=fish \|id=264 \|form=item \|translationkey=item.fish.name \|foot=1}} == Achievements == {{load achievements\|Delicious Fish;Lion Tamer;Echolocation}} == Advancements == {{load advancements\|Husbandry;A Balanced Diet;Fishy Business;A Complete Catalogue}} == History == {{History\|java alpha}} {{History\|\|v1.2.0\|snap=<nowiki>?\|slink=:Category:Information needed requiring unarchived version\|[[File:Raw Cod JE1 BE1.png\|32px]] Added raw fish, which restores {{hp\|2}}.}} {{History\|java beta}} {{History\|\|1.5\|Cooking raw fish now gives the '''Delicious Fish''' [[achievement]].}} {{History\|\|1.8\|snap=Pre-release\|Raw fish is now stackable to 64 and fills {{hunger\|2}} instead of {{hp\|2}}.}} {{History\|java}} {{History\|\|1.2.1\|snap=12w04a\|Raw fish can now be fed to [[ocelot]]s to tame them into cats.}} {{History\|\|1.8\|snap=14w02a\|Fisherman [[villager]]s now [[trading\|sell]] 6 cooked fish for 1 [[emerald]] plus 6 raw fish.}} {{History\|\|\|snap=14w25a\|Raw fish is now obtainable as a rare [[drops\|drop]] from [[guardian]]s and [[elder guardian]]s.}} {{History\|\|1.10\|snap=16w20a\|Raw fish is now dropped from [[polar bear]]s.}} {{History\|\|1.13\|snap=17w47a\|The different data values for the <code>fish</code> and <code>cooked_fish</code> IDs have been split up into their own IDs. \|"Raw Fish" has been renamed to "Raw Cod". \|Prior to [[1.13/Flattening\|''The Flattening'']], this [[item]]'s numeral ID was 349.}} {{History\|\|\|snap=18w07a\|Raw cod is now used to breed [[turtle]]s.}} {{History\|\|\|snap=18w07b\|Raw cod is no longer used to [[breeding\|breed]] turtles. [[Seagrass]] is used instead.}} {{History\|\|\|snap=18w08b\|Cod, and other [[fish]], have been added as [[mob]]s, which drop their (raw) item form when killed. \|[[File:Raw Cod JE2 BE2.png\|32px]] The texture of raw cod has been changed.}} {{History\|\|\|snap=18w15a\|Raw cod can now be used to feed [[dolphin]]s. \|Raw cod can now be obtained as a [[drops\|drop]] from [[dolphin]]s.}} {{History\|\|1.14\|snap=18w43a\|[[File:Raw Cod JE3.png\|32px]] The texture of raw cod has been changed.}} {{History\|\|\|snap=18w47b\|[[File:Raw Cod JE4 BE2.png\|32px]] The previous texture change to raw cod has been reverted.}} {{History\|\|\|snap=18w48a\|Raw cod can now be found in chests in [[village]] fisher cottages.}} {{History\|\|\|snap=19w11a\|Fisherman [[villager]]s now [[trading\|buy]] raw cod.}} {{History\|\|\|snap=19w13a\|Fisherman villagers now give raw cod to players under the [[Hero of the Village]] effect.}} {{History\|pocket alpha}} {{History\|\|v0.11.0\|snap=build 1\|[[File:Raw Cod JE1 BE1.png\|32px]] Added raw fish.}} {{History\|\|v0.12.1\|snap=build 1\|Raw fish now restore [[hunger]] instead of [[health]]. \|Raw fish can now be used to feed [[ocelot]]s to tame them into [[cat]]s.}} {{History\|\|v0.16.0\|snap=build 1\|Raw fish is now [[drops\|dropped]] by [[guardian]]s and [[elder guardian]]s.}} {{History\|pocket}} {{History\|\|1.0.0\|snap=alpha 0.17.0.1\|Added [[polar bear]]s, which [[drops\|drop]] raw fish.}} {{History\|\|1.0.4\|snap=alpha 1.0.4.0\|Fisherman [[villager]]s now [[trading\|sell]] 6 cooked fish for 1 [[emerald]] plus 6 raw fish.}} {{History\|bedrock}} {{History\|\|1.4.0\|snap=beta 1.2.14.2\|[[Cod]] and other [[fish]] have been added as [[mob]]s, which [[drops\|drop]] their (raw) [[item]] form when killed. \|[[File:Raw Cod JE4 BE2.png\|32px]] The texture of raw cod has been changed.}} {{History\|\|\|snap=beta 1.2.20.2\|Raw cod is now [[drops\|dropped]] by [[dolphin]]s and can be used to feed them.}} {{History\|\|1.5.0\|snap=beta 1.5.0.0\|Giving raw cod to [[dolphin]]s lead the [[player]] to the nearest [[underwater ruins]] or [[shipwreck]].}} {{History\|\|1.7.0\|snap=beta 1.7.0.2\|"Raw Fish" has been renamed to "Raw Cod".}} {{History\|\|1.8.0\|snap=beta 1.8.0.8\|Raw cod can no longer can be used to tame [[ocelot]]s. \|Raw cod can now be used to [[breeding\|breed]] ocelots and increase baby ocelot growth speed. \|Added [[stray cat]]s, which can be tamed using raw cod.}} {{History\|\|1.11.0\|snap=beta 1.11.0.4\|Raw cod can be [[trading\|sold]] to fisherman [[villager]]s. \|Fisherman villagers now have 50% chance to [[trading\|sell]] 6 cooked cod for 6 raw cod and an [[emerald]] as part of their first tier [[trading\|trade]].}} {{History\|console}} {{History\|\|xbox=TU1\|xbone=CU1\|ps=1.0\|wiiu=Patch 1\|switch=1.0.1\|[[File:Raw Cod JE1 BE1.png\|32px]] Added raw fish.}} {{History\|\|xbox=TU5\|Raw fish is now stackable to 64. \|Raw fish now fills [[hunger]] instead of [[health]].}} {{History\|\|xbox=TU12\|Raw fish can now be fed to [[ocelot]]s to tame them into [[cat]]s.}} {{History\|\|xbox=TU13\|ps=1.0\|Raw fish is no longer removed from the [[player]]'s [[inventory]] when trying to tame an [[ocelot]] in [[creative]] mode.}} {{History\|\|xbox=TU69\|xbone=none\|ps=1.76\|wiiu=Patch 38\|switch=none\|"Raw Fish" has been renamed to "Raw Cod". \|[[File:Raw Cod JE4 BE2.png\|32px]] The texture of raw cod has been changed.}} {{History\|new 3ds}} {{History\|\|0.1.0\|[[File:Raw Cod JE1 BE1.png\|32px]] Added raw fish.}} {{History\|foot}} == Issues == {{issue list}} == Trivia == [[File:Steve wearing Raw Cod.png\|75px]] [[File:Alex wearing Raw Cod.png\|75px]] * While a raw cod cannot be equipped in the head slot in Survival mode, equipping it using the {{cmd\|item}} command causes it to appear at the side of the player's head. == See also == * [[Fishing]] == References == {{reflist}} {{items}} [[de:Roher Kabeljau]] [[es:Bacalao crudo]] [[ja:生鱈]] [[ko:생대구]] [[pt:Bacalhau cru]] [[ru:Сырая треска]] [[zh:生鳕鱼]] [[Category:Food]] [[Category:Renewable resources]]</li></ul></nowiki>	18w15a	Added dolphins.
Upcoming Bedrock Edition
1.4 {{Extension DPL}}<ul><li>[[Explorer Map\|Explorer Map]]<br/>{{about\|the map used to find rare structures\|the craftable map\|Map\|others\|Map (disambiguation)}}{{Needs updating\|Add info on the new jungle, swamp, and village maps in Java 1.20.2 Pre-Release 1}}{{Item \| image = <gallery> Ocean Explorer Map.png \| Ocean Woodland Explorer Map.png \| Woodland Buried Treasure Map.png \| Buried Treasure </gallery> \|image2 = <gallery> Ocean Explorer Map BE.png \| Ocean (BE) Woodland Explorer Map BE.png \| Woodland (BE) Buried Treasure Map BE.png \| Buried in Treasure (BE) </gallery> \| renewable = * '''Buried Treasure''': No * '''Woodland and Ocean''': Yes \| stackable = Yes (64) }} An '''explorer map''' is a special [[map]] used to aid in finding rare [[generated structures]], including [[woodland mansion]]s, [[ocean monument]]s, and [[buried treasure]]s. == Obtaining == === Trading === Apprentice-level [[cartographer]] villagers sell ocean explorer maps for 13 emeralds and a compass. Journeyman-level cartographer villagers sell woodland explorer maps for 14 emeralds and a compass. {{IN\|java}}, if the cartographer is in [[the Nether]] or [[the End]], either spawned or transported, the trades for the map do not unlock. However, {{in\|bedrock}}, the cartographer trades for the map are unlocked, but the purchased map shows the same layout as in the corresponding dimension and shows no destination structure, but if cartographer trades are unlocked in an old world type (prior-1.11.0), the game stops ticking. In ''Java Edition'', each cartographer sells its own unique explorer map that points to a different location than other cartographers. Purchasing another explorer map from the same cartographer results in the same explorer map. In Bedrock Edition, a cartographer sells an explorer map that points to the nearest location, regardless of whether it is explored or previously mapped by another cartographer.<!-- start to glitched out--> === Chest loot === Treasure maps, in contrast to explorer maps, generate in underwater ruins or in shipwrecks. {{LootChestItem\|buried-treasure-map}} == Usage == [[File:Explorer Map Comparison.gif\|thumb\|217px\|Unexplored and partially explored maps.]] {{See also\|Map#Mapping\|Map#Map content}} === Locating structures === There are three types of explorer maps: woodland, [[ocean]], and buried treasure. The maps differ from a normal map, in that it shows the area's land-water outline, with an orange striated (striped) texture for water<ref>Specifically, biomes in the "water_on_map_outlines" [[Tag#Biomes\|biome tag]].</ref>, and the blank map texture for land. The maps show a section of land that contains a [[woodland mansion]], [[monument]] or [[buried treasure]] respectively. This may not be the nearest such [[structure]] to the [[player]]. The structures are displayed as a small icon. If the player icon is smaller than it would be on a normal map, that means the player is a great distance away. When the player is less than 1027 blocks away from the map border, the icon returns to the proper size. When the player reaches the map's area of land (512×512), the [[map]] fills in like a normal map. The basic functions of a buried treasure explorer map are similar to that of the other two. However, instead of showing the structure icon on the map, it shows a red X instead. The [[buried treasure]] structure is located on the same X and Z coordinates as the middle of the X (the player marker may need to be aligned with the bottom of the middle 2×2 pixel square of the X). To locate the [[chest]] spot, hold the treasure map with both hands, not in the offhand slot. === Cloning === {{Crafting \|showdescription=1 \|shapeless=1 \|name=[[Explorer Map]]<br>(cloned) \|;;;Empty Map;Empty Map;Empty Map;Empty Map;Empty Map \|;;;;Empty Map;Empty Map;Empty Map;Empty Map \|;;;;;Empty Map;Empty Map;Empty Map \|Ocean Explorer Map; Woodland Explorer Map; Buried Treasure Map; Ocean Explorer Map; Woodland Explorer Map; Buried Treasure Map; Ocean Explorer Map; Woodland Explorer Map \|Empty Map \|;;;;;;Empty Map;Empty Map \|;Empty Map;Empty Map;Empty Map;Empty Map;Empty Map;Empty Map;Empty Map \|;;Empty Map;Empty Map;Empty Map;Empty Map;Empty Map;Empty Map \|;;;;;;;Empty Map \|Output= Ocean Explorer Map,2; Woodland Explorer Map,3; Buried Treasure Map,4; Ocean Explorer Map,5; Woodland Explorer Map,6; Buried Treasure Map,7; Ocean Explorer Map,8; Woodland Explorer Map,9 \|type= Miscellaneous \|description=The output has the same map center as the input map, and the same [[monument]], [[woodland mansion]] or [[buried treasure]] marker. Cloned maps are stackable. }} The parts of the world that have already been explored and mapped are copied, and newly explored areas appear on both instances. In Creative mode, cloned explorer maps can be obtained by pick blocking on the explorer map displayed on [[item frames]] (the map needs to be out of the [[player]]'s inventory when using pick block, or else that map moves into the active hotbar slot). == Sounds == {{edition\|java}}: {{Sound table \|sound=Drawmap1.ogg \|sound2=Drawmap2.ogg \|sound3=Drawmap3.ogg \|subtitle=Map drawn \|source=block \|description=When an explorer map is edited using a cartography table \|id=ui.cartography_table.take_result \|translationkey=subtitles.ui.cartography_table.take_result \|volume=1.0 \|pitch=1.0 \|distance=16 \|foot=1}} {{edition\|bedrock}}: ''None'' == Data values == === ID === {{edition\|java}}: {{ID table \|edition=java \|showforms=y \|generatetranslationkeys=y \|displayname=Map \|spritetype=item \|nameid=filled_map \|form=item \|translationkey=filled_map.mansion,filled_map.ocean,filled_map.buried_treasure \|foot=1}} {{edition\|bedrock}}: {{ID table \|edition=bedrock \|showaliasids=y \|shownumericids=y \|showforms=y \|notshowbeitemforms=y \|generatetranslationkeys=y \|displayname=Map \|spritetype=item \|nameid=filled_map \|aliasid=map \|id=358 \|form=item \|translationkey=item.map.exploration.monument.name,item.map.exploration.mansion.name,item.map.exploration.treasure.name \|foot=1}} === Metadata === {{see also\|Bedrock Edition data values}} {{IN\|bedrock}}, the item [[Data value]] distinguishes explorer maps from one another: {{:Map/DV}} === Item data === An explorer map differs from a map in that its <code>display</code> tag is set, which includes a <code>Mapcolor</code> and a <code>LocName</code>; also its <code>Decorations</code> list includes an entry for its target monument, mansion or buried treasure. Its [[Map item format#map_<#>.dat format\|map item entry]] is identical to that of a normal map, except that by the time the player sees it, its <code>colors</code> byte array is pre-filled with explorer maps' characteristic land-water boundary lines and water shading. <div class="treeview"> It should be noted that this additional data is stored in the Cartographer's NBT data and in the inventory item's NBT data, and not in the map file (e.g. <samp>map_0.dat</samp>). If the [[player]] were to use the {{cmd\|give}} command to give themselves a map with the same map ID as an existing explorer map, it would still have the Ocean Monument or the Woodland Mansion icon on the map, but it would simply be named "Map" instead of, for example, "Ocean Explorer Map". * {{nbt\|compound}} Item data {{nbt\|compound\|tag}}: * {{nbt\|compound\|display}}: How the map looks in an item slot. See also [[Player.dat_format#Display Properties]]. ** {{nbt\|string\|Name}}: The name the map is given. In this case, they are localized strings: either <code>{"translate":"filled_map.monument"}</code>,<code>{"translate":"filled_map.mansion"}</code> or <code>{"translate":"filled_map.buried_treasure"}</code>. {{nbt\|int\|MapColor}}: Color codes are calculated from the Red, Green and Blue components using this formula:<br>'''<span style="color:red">Red</span>[[wikipedia:Logical shift\|<<]]16 + <span style="color:green">Green</span><<8 + <span style="color:blue">Blue</span>'''.<ref group=note>For positive values larger than 0x00FFFFFF, the top byte is ignored. All negative values produce white.</ref> Monument maps use 3830373, which is {{color swatch\|58\|114\|101}}. Mansion maps use 5393476, which is {{color swatch\|82\|76\|68}}. Buried treasure explorer maps do not use a color code. * {{nbt\|list\|Decorations}}: ** {{nbt\|compound}}: One of these for each icon on the map. Explorer maps always have at least one representing their target. * {{nbt\|string\|id}}: An arbitrary unique string identifying the decoration. For explorer map target structures, this is "+". * {{nbt\|double\|rot}}: The rotation of the icon. For explorer map target structures, this is always 180. * {{nbt\|byte\|type}}: The ID of the [[Map#Map icons\|map icon]]: 8 for a mansion map, 9 for a monument map, 26 for a treasure map. * {{nbt\|double\|x}}: The world x-coordinate of the target structure icon. *** {{nbt\|double\|z}}: The world z-coordinate of the target structure icon. </div> ; Notes {{notelist}} == Achievements == {{load achievements\|Treasure Hunter}} == History == {{History\|java}} {{History\|\|1.11\|snap=16w39a\|[[File:Woodland Explorer Map JE1 BE1.png\|32px]] [[File:Ocean Explorer Map JE1 BE1.png\|32px]] Added woodland and ocean explorer maps.}} {{History\|\|\|snap=16w41a\|Explorer maps can now no longer be zoomed out.}} {{History\|\|1.13\|snap=18w10a\|[[File:Map (item) JE1 BE1.png\|32px]] Added buried treasure explorer maps.}} {{History\|\|\|snap=18w11a\|Buried treasure explorer maps now generate in the [[chest]]s of [[shipwreck]]s.}} {{History\|\|1.14\|snap=18w43a\|[[File:Woodland Explorer Map JE2 BE2.png\|32px]] [[File:Ocean Explorer Map JE2 BE2.png\|32px]] [[File:Map (item) JE2 BE2.png\|32px]] The textures for explorer maps have now been changed.}} {{History\|\|1.20.2\|snap=1.20.2 Pre-release 1\|Updated structure icons on explorer maps sold by cartographers.}} {{History\|\|Villager Trade Rebalance<br>(Experimental)\|link=Java Edition 1.20.2\|snap=1.20.2 Pre-release 1\|Added seven new maps which cartographers can sell.}} {{History\|pocket}} {{History\|\|1.1.0\|snap=alpha 1.1.0.0\|[[File:Woodland Explorer Map JE1 BE1.png\|32px]] [[File:Ocean Explorer Map JE1 BE1.png\|32px]] Added explorer maps.<ref>{{Mcnet\|discovery-update-pocket-and-win-10-soon\|The Discovery Update: on Pocket and Win 10 soon\|March 29, 2017}}</ref> \|Explorer maps are not yet obtainable in [[survival]] mode.}} {{History\|\|\|snap=alpha 1.1.0.3\|Explorer maps are now obtainable as [[trading\|trades]] from [[cartographer]] [[villager]]s.}} {{History\|bedrock}} {{History\|\|1.4.0\|snap=beta 1.2.14.2\|[[File:Map (item) JE1 BE1.png\|32px]] Added buried treasure explorer maps.}} {{History\|\|\|snap=beta 1.2.20.1\|Treasure maps now generate in [[underwater ruins]] [[chest]]s.}} {{History\|\|1.10.0\|snap=beta 1.10.0.3\|[[File:Woodland Explorer Map JE2 BE2.png\|32px]] [[File:Ocean Explorer Map JE2 BE2.png\|32px]] [[File:Map (item) JE2 BE2.png\|32px]] The textures for explorer maps have now been changed.}} {{History\|\|1.11.0\|snap=beta 1.11.0.4\|[[Trading]] has now been changed, woodland and ocean explorer maps now cost a [[compass]] and 12 [[emerald]]s. \|Journeyman-level [[cartographer]] [[villager]]s no longer [[trading\|sell]] 2 type of explorer map as they now have {{frac\|1\|3}} chance to sell woodland explorer maps, {{frac\|1\|3}} chance to sell ocean explorer maps, or {{frac\|1\|3}} chance to sell other [[item]]s<!-- empty locator map--> as part of their [[trading\|trades]]. \|Woodland explorer maps can now be [[trading\|bought]] from fletcher [[villager]]s.}} {{History\|\|1.12.0\|snap=beta 1.12.0.3\|Journeyman-level fletcher villagers no longer [[trading\|sell]] woodland explorer maps.}} {{History\|\|1.13.0\|snap=beta 1.13.0.1\|[[File:Woodland Explorer Map BE3.png\|32px]] [[File:Ocean Explorer Map BE3.png\|32px]] [[File:Buried Treasure Map BE3.png\|32px]] The textures of explorer maps have now been changed.}} {{History\|\|1.16.100\|snap=beta 1.16.100.56\|The ID of maps has been changed from <code>map</code> to <code>filled_map</code>.}} {{History\|console}} {{History\|\|xbox=TU54\|xbone=CU44\|ps=1.52\|wiiu=Patch 24\|switch=1.0.4\|[[File:Woodland Explorer Map JE1 BE1.png\|32px]] [[File:Ocean Explorer Map JE1 BE1.png\|32px]] Added explorer maps.}} {{History\|PS4}} {{History\|\|1.90\|[[File:Woodland Explorer Map JE2 BE2.png\|32px]] [[File:Ocean Explorer Map JE2 BE2.png\|32px]] The textures for explorer maps have now been changed.}} {{History\|new3ds}} {{History\|\|1.9.19\|[[File:Woodland Explorer Map JE1 BE1.png\|32px]] [[File:Ocean Explorer Map JE1 BE1.png\|32px]] Added explorer maps.}} {{History\|foot}} == Issues == {{Issue list}} == Trivia == * When a [[cartographer]] generates the trade offers for the explorer maps, it chooses the location of one of the nearest structures of the respective type ([[monument]] or [[woodland mansion]]). * For the reason above, explorer maps obtained from one cartographer are always the same. Also, if two cartographers unlock the explorer map trades approximately at the same place and at the same time, the map locations are usually identical. This sometimes also happens when finding multiple treasure maps from [[ocean ruins]]. * Explorer maps fill as the [[chunk]]s are generated, rather than when the [[player]] holds them while in the area; leaving an explorer map while exploring the area still fills the map. * Buried treasure explorer maps are named ''Buried Treasure Map'' {{in\|java}} while {{in\|bedrock}}, they are named ''Treasure Map''. * It is possible for a cartographer to give a monument or woodland mansion explorer map for areas where the [[generated structures\|structures]] would have spawned in the world, but were unable to as a result of terrain generation. As a result, explorer maps, unfortunately, don't always guarantee that a structure exists at the purported location. This is most common with woodland mansion explorer maps, due to its generation algorithm. * On [[Bedrock Edition]], inventory editors and add-ons can be used to create Explorer Maps that lead to any structure. == Gallery == <gallery> File:Explorer Maps.png\|An ocean explorer map in the [[off-hand]], a woodland explorer map in the main hand, and a [[cartographer]] [[villager]] in between them. File:Partial Explorer Map.png\|A partially-explored explorer map. File:ExplorerToNormal Map Comparison.png\|Two fully-explored maps of the same place, one of which is a woodland explorer map. File:Buried Treasure Explorer Map.png\|An [[item frame]] holding a buried treasure explorer map. The player can see the red X on the left side of the map. File:Purchase.png\|Purchasing explorer maps from a cartographer. </gallery> == See also == * [[Map]] * [[Woodland Mansion]] * [[Ocean Monument]] * [[Shipwreck]] * [[Buried treasure]] == References == {{reflist}} == External Links == *[https://www.minecraft.net/en-us/article/taking-inventory--explorer-map Taking Inventory: Explorer Map] – Minecraft.net on November 13, 2019 {{Items}} [[de:Schatzkarte]] [[es:Mapa (localización de estructura)]] [[fr:Carte d'exploration]] [[ja:探検家の地図]] [[ko:탐험 지도]] [[pl:Mapa eksploracyjna]] [[pt:Mapa de exploração]] [[ru:Карта сокровищ]] [[zh:探险家地图]]</li><li>[[:Category:Joke items\|Category:Joke items]]<br/>[[Category:Joke features\|Items]] [[Category:Items]]</li></ul>	Beta 1.2.20.1	Added dolphins.
	Beta 1.2.20.2	Dolphin model has been updated.
	Beta 1.2.20.2	Dolphins now have sounds.
	Beta 1.5.0.0	Now lead players to shipwrecks and underwater ruins.

- Princess Nightmoon (Talk Contributions) 13:19, 27 April 2018 (UTC)

A better way is to write the version just like in-game. We don't need beta prefixes. Beta 1.5.0.0 will be just called 1.5.0.0. This can prevent confusion. Skylord wars (talk) 06:57, 28 April 2018 (UTC)

An example.

Infobox (1.5.0.0)
"Type" indicates that it's a beta (snapshot) version, "Beta for" indicates which version it's a beta for.

I'm sure most readers can determine this is a Beta version page.Skylord wars (talk) 07:01, 28 April 2018 (UTC)

Are we going to start a renaming project?--Skylord wars (talk) 01:32, 2 May 2018 (UTC)

I don't think a renaming project would be necessary - I certainly wouldn't mind moving all of the builds to their beta titles and fixing the article's information. I would like the opinions of other editors before doing this though, as I'm not sure if we've come to a consensus yet. This will be a pretty drastic change to the wiki, so we need to make sure that the community overall is OK with doing this, so that we can avoid a mass page-move revert. Another thing to keep in mind is all of the templates and links that will need to be updated after we've done this.-- Madminecrafter12^{Talk to me} 01:36, 2 May 2018 (UTC)

I guess we don't need to move all of it, but only updates after 1.0. Because the in-game version started using this format after 1.0. Before 1.0, Pocket Edition still uses build numbers in-game. This is the same with Beta 1.9 Prerelease and 1.9-pre1, we need to follow the in-game number. I have created a page User:Skylord wars/Bedrock Beta.--Skylord wars (talk) 01:46, 3 May 2018 (UTC)

I'm all for using in-game names as much as possible. Making up our own terms isn't helpful to reducing confusion. –Majr ᐸ Talk
Contribs 05:28, 5 May 2018 (UTC)

How about fitting the Japanese page that separates the template before and after the 1.2 release that became Bedrock Edition?--Mikanzukituyu02 (talk) 15:08, 6 May 2018 (UTC)

If you use Changelog in game as information source, 1.2.20.1 is build 8, 1.2.20.2 is build 9, 1.5.0.0 is build 10, 1.5.0.1 is build 11.--Mikanzukituyu02 (talk) 15:20, 6 May 2018 (UTC)

Can confirm the above as I’ve seen a screenshot of it that said “Build 11” on it. So referring to these as builds 9, 10, 11, etc. is fine. --Marioprotvi (talk) 13:10, 9 May 2018 (UTC)

Auto-importing pages?

Is there any way to automatically transfer a page's content onto a page on an other wiki. More specifically, I'd like the Module:Version/Numbers page to be transferred into its equivalent on the Hungarian wiki, Modul:Version/Numbers. Is that possible? david92003 (talk) 17:11, 27 April 2018 (UTC)

You can export pages with their full history by using Special:Export (make sure to uncheck "Include only the current revision, not the full history"), and then import them using Special:Import (though note that you have to be an administrator to import pages). 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 19:57, 27 April 2018 (UTC)

Version nav template

I've recently edited a page about a version on the Hungarian wiki and realized that the Version nav template is completely unused. I tried to use it, copied all the content from the templates on this wiki over there, and it mostly works. The only problem is that the template is in the middle of the page. Example: 1.12 - the source code for this is exactly the same as the one on the English wiki. What can I do to fix it? david92003 (talk) 15:12, 28 April 2018 (UTC)

You need the infobox-related styles from MediaWiki:Common.css as well. 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 16:32, 28 April 2018 (UTC)

Deletion requests for mod pages

Several IPs (I'm pretty sure they're the same person though, as their IPs are very similar and always have a similar edit summary) are going to mod pages for mods that only work in outdated versions, and requesting that they be deleted. I'm not familiar with mods and how they should be incorporated into the wiki, which is why I'm asking this question to the community. If a mod does not work in the current version, should it be deleted? Like I said, I'm not too familiar with the subject, so I haven't been adding any deletion templates myself, but if the answer is "No, just because the mod doesn't work in the current version doesn't mean the mod page should be deleted," then I will start reverting the edits from the IP(s) adding {{delete}}.-- Madminecrafter12^{Talk to me} 14:18, 4 May 2018 (UTC)

Trivially, this is not enough reasoning. No mod would work with the ultra-new, two-hour-old JE release, and this is not valid basis to nuke every mod page there is.

However, mod pages in general seem to be largely abandoned. Some of them are almost contentless. I think we should change the topic of the conversation to the more general one of mod article policy on this wiki. --AttemptToCallNil (report bug, view backtrace) 14:27, 4 May 2018 (UTC)

I do agree that we should discuss the mod policy on the wiki. However, for short term purposes, should I let the IP(s) add deletion templates to every single mod page there is that does not work in the current version (which is pretty much what they're doing now), or revert the edits?-- Madminecrafter12^{Talk to me} 14:52, 4 May 2018 (UTC)

I'm not the final authority, but I'd just check, and if both the mod is available for download, and the required MC version is listed in the official launcher, I'd revert; if not, I'd replace the deletion reason with "no longer available/usable". --AttemptToCallNil (report bug, view backtrace) 15:47, 4 May 2018 (UTC)

We also need to make the same decision about custom servers.

I'm totally happy to get rid of all the mods and move them to ftb:. It's better set up to work with mods, whereas ours are just tacked on the side with vanilla taking the main space. I think it's a lot simpler to have this wiki focus on vanilla, and FTB and individual wikis focus on mods.

@Xbony2: What's FTB's policy on abandoned mods and ones for outdated versions of Minecraft, such as what's currently inhabiting Category:Pending deletion? –Majr ᐸ Talk
Contribs 05:20, 5 May 2018 (UTC)

I believe the question of mods has come up on Slack in the past, though I couldn't say what (if any) result came of it; personally I'd be in favor of Majr's suggestion to move all mod content to FTB and/or individual wikis. Doing this would also let us simplify several templates that have for years had to include support for mods (IIRC it would mostly be the inventory-related templates that are affected).

I added a comma to your comment to clarify your meaning, Majr, feel free to remove it if I got it wrong or you don't want it there.

「ディノ奴千？！」^{? · ☎ Dinoguy1000} 08:12, 5 May 2018 (UTC)

What would you have other language wikis do with their mod articles? The Russian wiki has a substantial portion of users contributing mainly to mod articles. --AttemptToCallNil (report bug, view backtrace) 09:23, 5 May 2018 (UTC)

That would be up to each wiki to decide for themselves; the English wiki shouldn't presume to dictate how the other-language wikis have to operate. If any of them want to go the suggested route here, though, the obvious option would be checking if there's an FTB/individual wiki in that language, and if not, seeing about having one set up (assuming the FTB/individual wiki isn't currently operated as a multilingual wiki). 「ディノ奴千？！」^{? · ☎ Dinoguy1000} 09:32, 5 May 2018 (UTC)

En's mod articles being mostly garbage and unmaintained doesn't affect other languages, so I don't see how us getting rid of them entirely does either. –Majr ᐸ Talk
Contribs 09:58, 5 May 2018 (UTC)

English wiki deletes mod articles.
English wiki removes mod support from templates/modules.
A non-English wiki (Wiki X) decided to keep their mod articles and use the original template/module versions.
Affected templates/modules are updated on the English wiki in order to introduce functionality needed on all language wikis. The update requires nontrivial adaptation (i. e. beyond copying and string translation) in order to make it work with the original, mod-supporting templates/modules. As a result, a major portion of mod templates/modules on Wiki X now requires substantially more effort to update.

I don't think this is an improbable scenario. --AttemptToCallNil (report bug, view backtrace) 10:11, 5 May 2018 (UTC)

That's fair, in which case I would use separate templates for mods. If we were keeping mods, that's what I'd want to do anyway, as supporting mods makes some things difficult to do (like getting rid of the legacy grid images). –Majr ᐸ Talk
Contribs 12:05, 5 May 2018 (UTC)

I'm not exactly sure what "separate templates for mods" means. Something like a Slot which only supports vanilla and ModSlot which also supports mods? And then Crafting for vanilla recipes, and ModCrafting for recipes from mods, plus similarly separated template pairs for all other interfaces? --AttemptToCallNil (report bug, view backtrace) 13:04, 5 May 2018 (UTC)

If the features mods need diverges from the features vanilla needs enough, it would be easier yes. If possible, it should be designed so that the mod version can just implement the extra features and hook in to the vanilla version for output. But if it's simple to include, we don't necessarily need to remove mod support entirely. –Majr ᐸ Talk
Contribs 13:34, 5 May 2018 (UTC)

Vanilla supports mod content via namespaces (vanilla uses minecraft:, other mods are assigned other namespaces). This behavior should probably be in all of the templates, especially if Mojang does end up introducing content in other namespaces. I don't know enough about how the templates work to actually say how feasible this is though. (I've been adding namespaces to things when I see it, though a lot of pages still are missing them) --Pokechu22 (talk) 16:26, 5 May 2018 (UTC)

Create redirects

I guess yet again, I have to discuss with the community about the creation of these redirects per MinecraftPhoto4U's move summary. The redirects I want to create are Version history/Infdev, Version history/Indev, Version history/Classic, and Version history/Pre-classic. The reason is, A a ton of pages link to these that have not been fixed, B they are all very likely search terms, and C no other versions have development stages with these titles, so there's no reason not to have these redirects. Also, I'm not sure why MinecraftPhotos4U moved them to Java Edition Version history/[Development stages], as no pages would link to them and would never need to, AND it's useless for searching, as the first letter of any word is not case-sensitive in the search box.

Also, please don't think I'm trying to be rude or anything, but MinecraftPhotos4U, I'm really not a fan of how you're moving a ton of pages without leaving a redirect, breaking a lot of links, removing search options, AND all of the moves are without discussion, could be controversial, and many times (such as this time), just really don't make any sense - and then you say that we must discuss before recreating the redirects. I'm fine with you doing this if the community agrees with this, but for me it kind of seems annoying. I really hope you don't take any offense to this - you're a great editor and you've done some great things on the Minecraft Wiki. We're all just trying to make the Minecraft Wiki a better place, and I just thought I would bring this up. Once again, please don't take this as rude or offensive, as I do not mean for it to be taken that way at all.-- Madminecrafter12^{Talk to me} 22:39, 5 May 2018 (UTC)

About the redirects, most of them are fixes. See Pre-classic, Classic, Indev, and Infdev. Most search engines have fixed their links. Plus, it seems strange to let Alpha and Beta be in "Java Edition version history", while others are in "Version history". Thus, I don't see a reason to make these redirects--Skylord wars (talk) 06:40, 6 May 2018 (UTC)

It is useful to have these and they existed for ages and are still linked to by a lot of pages. What's wrong with having them? – Nixinova

06:53, 6 May 2018 (UTC)

You don't because there's no reason to be moving these redirects in the first place. Additional redirects can be created where needed, and unused and worthless redirects can be deleted, but moving them usually doesn't make sense. Since they were warned to stop moving pages, but continued, they've been blocked for a few days. –Majr ᐸ Talk
Contribs 07:28, 6 May 2018 (UTC)

Hostile Mobs not spawning in singleplayer survival.

I've started a singleplayer survival world, but I've had this problem that hostile mobs rarely spawn, only spwaners work, traps that include them spawning randomly in low light platforms seem to not be working. I've tried everything;

lighting up caves (which are almost empty, no mobs in there, as if I was in peaceful mode)
afk 24+ blocks away for longer than 1 hour (only 2 creepers spawned, figured that when I found 4 gunpowder transported in the chest by hoppers at the bottom of the trap)

If there's anything I can do please let me know. I've seen other vanilla players in youtube, they get massive quantities of spawns, but I don't get any. Screenshots included.–Preceding unsigned comment was added by EternalAssassin (talk • contribs) at 19:00, May 6, 2018 (UTC). Please sign your posts with ~~~~

You may need to post in in the forum. Try turn your render distance to a higher level, it may work.--Skylord wars (talk) 11:19, 6 May 2018 (UTC)

Texture Update

So when the texture update is released, will these old textures in the {{InvSprite}} stay? Or are they going to be replaced with the new ones? I propose to move the old sprite to a separate template where it will eventually be used in the history section. – ItsPlantseed ⟨₰|₢⟩ 06:16, 9 May 2018 (UTC)

@ItsPlantseed: So something like moving InvSprite to InvSpriteOld or InvSpritePre(release date here), then updating InvSprite with the new textures? jjlr (talk) 06:20, 9 May 2018 (UTC)

Yes, but I'm not sure if that's necessary though. The file has reached 1MB and I don't know if it will affect performance issues. – ItsPlantseed ⟨₰|₢⟩ 06:50, 9 May 2018 (UTC)

Performance isn't really a concern with sprites, they're meant to have lots of images in (I'd actually be more worried about the size of the documentation page). However in this case, since it's changing pretty much everything I think it would be good to split off now, just to make editing easier (smaller page/image to upload reduces edit time), and also we should probably do this for blocks and items too. Then we just need to decide if we want to make it totally historical stuff (so whenever a texture changes we move the old image to the historical invsprite), or if it should contain all textures beginning from the texture update.

I'll create the base for the modules now so anyone can start getting the new textures uploaded. –Majr ᐸ Talk
Contribs 07:56, 10 May 2018 (UTC)

Nice, I'll start adding texture for the items now. Also I have a question, are those "TextureUpdate" suffix temporary? We seem somewhat familiar with the current sprite title. – ItsPlantseed ⟨₰|₢⟩ 10:36, 10 May 2018 (UTC)

Of course, the current templates/modules will be moved elsewhere once the update comes out (the name of which we need to decide on), then the new ones moved over the redirects.

Also I noticed you mentioned having an issue with using find in the browser creating duplicates? Did you mean you used some sort of find/replace thing to change names rather than editing them manualy? If that's the case then I think I can fix that. –Majr ᐸ Talk
Contribs 10:47, 10 May 2018 (UTC)

About that, I didn't use CTRL + F to replace (well since I can't), I used the key to find the name instead of scrolling. When I search E.g 'blue', the highlighted word will be considered as a duplicate, so I can't save it until I change all the misinterpreted words into something different. It seems like it only occurs on Edge, but I'm not sure for other browser. – ItsPlantseed ⟨₰|₢⟩ 11:23, 10 May 2018 (UTC)

Ah that wasn't the bug I was thinking of then. The issue is that edge sends a blur event to elements when it moves the find highlight off of them, regardless of if it was focused (and it doesn't send a focus event on the element which it moved the highlight to), which causes the script to think the original value is undefined (because there was no focus event to set the original name), which causes the script to "change" the current name to exactly the same as it already was making it think it's a duplicate. Was easily fixed though. –Majr ᐸ Talk
Contribs 12:10, 10 May 2018 (UTC)

Reference template with archive support

What is everyones opinion on a reference template that allows you to specify both the original link to a page but also an archive.org link for it? Something similar to wikipedia's archiveurl option for it's citation template. jjlr (talk) 11:05, 9 May 2018 (UTC)

Could be useful, but I don't think we want to specify archive links for absolutely every reference. --AttemptToCallNil (report bug, view backtrace) 11:24, 9 May 2018 (UTC)

I know that, it would be optional, so if you don't specify an archive link it will treat it as a normal reference. jjlr (talk) 11:27, 9 May 2018 (UTC)

Support--Skylord wars (talk) 12:46, 9 May 2018 (UTC)

Question Where on the page would this template be used? Would it also have deadurl= and archivedate= parameters? – Auldrick (talk · contribs) 17:33, 9 May 2018 (UTC)

Answer I was thinking it could be used in place of the ref tag, so it would be used anywhere the ref tag could be used. Also it could have archivedate and maybe a urldead parameter that accepts a binary value (0 for false;1 for true), when true it could maybe state in the reflist that the original link is dead and to use the archive link, or maybe it could automatically redirect the reference to the archive link, otherwise when false it would just do nothing. This is currently more a concept than a working idea, and i would need some help getting a working prototype. jjlr (talk) 00:24, 10 May 2018 (UTC)

I've added an |archive-url= parameter to {{link}} (which only shows if |dead-url= is set). – Nixinova

04:18, 10 May 2018 (UTC)

Sounds parameter in BlockTileEntity template

When trying to add the new audio for the conduit and beacon to their relative infoboxes i noticed the BlockTileEntity template didn't have a sound parameter, would it be possible to add one since there are quite a few tile entities that produce sound. jjlr (talk) 05:44, 10 May 2018 (UTC)