Minecraft Wiki
Register
Advertisement

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

Fire TV Edition & Education Edition proposed changes

(EDIT: Incorrect information crossed out. Sorry about that. :S)

So this was a bit unexpected, but there is now a Fire TV Edition, which costs the same as the Apple TV Edition and is essentially replacing Pocket Edition for Fire OS. and Pocket Edition for Fire OS is no longer supported on the Fire TV.

https://www.amazon.com/dp/B01NCJDPER

Fire OS Pocket Edition will NO LONGER BE UPDATED. If you own Fire OS Pocket Edition, you can get the Fire TV Edition for free. To quote the product page:

"If you have purchased Pocket Edition on Fire TV prior to 12/19 and want to get the 1.0 The Ender update, you need to install the new separate 'Minecraft: Fire TV Edition' app. You are entitled to get this for free, simply search and download. If you have trouble, please contact Amazon Customer Support."

There is already a page for the Fire TV Edition (http://minecraft.gamepedia.com/Fire_TV_Edition), but it is currently not listed on the homepage in the list of latest versions for each MCPE/Pocket edition. The Fire OS version of Pocket Edition is currently there... but does it still belong there? Now that Fire OS Pocket Edition has had its support dropped, shouldn't it be removed & replaced with the Fire TV Edition? (Basically just swap the logos from this: https://hydra-media.cursecdn.com/minecraft.gamepedia.com/thumb/d/db/Fire_OS.png/45px-Fire_OS.png to this: https://hydra-media.cursecdn.com/minecraft.gamepedia.com/thumb/d/d5/FireTV.png/40px-FireTV.png

The Pi Edition, which was discontinued long ago, and its logo is no longer shown on the homepage. Should the Fire OS logo be removed? Or should it stay for now and the Fire TV logo be added alongside it? There also seems to be a couple places where Fire OS Pocket Edition & Fire TV Edition are not distinguished from each other properly, and both are called Fire OS Edition... Fire OS Pocket Edition will not be updated from 1.0.0, and the Pocket Edition page and other references to the Fire OS Pocket Edition should reflect that.


Also, the Education Edition is currently shown as a "computer edition" in the "Minecraft by Mojang AB, 4J Studios and Telltale Games" template.

It is NOT based off of the Java/computer/PC Edition, and is actually based off of Pocket/MCPE, like Windows 10 Edition, Apple TV Edition, Gear VR Edition, etc. It is the most different of all the MCPE versions, but it is still based off of the same codebase and is definitely more related to Pocket than it is to the Computer/Java Edition. And Pi Edition (at this point even further divergent from Pocket) is listed under "Pocket", so Education Edition should be too. It is also important to not confuse Education Edition with the older MinecraftEdu (see http://minecraft.gamepedia.com/Mods/MinecraftEdu), which was a modded version of the Java Edition and is NOT technically related to Education Edition at all, though it has been essentially replaced by it, since Education Edition has exclusive features that match those added by the MinecraftEdu mod.

(Minecraft 4k also doesn't really belong there, but then again it doesn't really fit anywhere. It really fits its own category entirely. So maybe a misc category should be made, too, for the sake of accuracy.)

SuperGeniusZeb (talk) 20:16, 26 December 2016 (UTC)

 Oppose change to Fire TV. The disclaimer basically says that if you bought Pocket Edition on Fire TV prior to December 19, then the Fire TV Edition needs to be installed. The "Fire OS Pocket Edition" has already updated to 1.0, and will very likely continue to be updated.
 Support moving Education Edition to Pocket Edition, which I've taken care of already.
-BDJP (t|c) 21:10, 26 December 2016 (UTC)
Argh, I rechecked my information sources... and it turns out the Fire OS Pocket Edition, as you said, is NOT being discontinued. It is only dropping Fire TV support, so the Fire OS Pocket Edition will no longer be updated on Fire TVs. Sorry about the misinformation!
Still, I think that Fire TV Edition should be added to the homepage & any other lists of MCPE editions that it isn't already in, since it is still a separate edition from Pocket Edition, and perhaps some notes on the Pocket Edition page should be made to note that Pocket Edition used to be available on Fire TVs, but that functionality has been superseded by the Fire TV Edition.
SuperGeniusZeb (talk) 04:12, 27 December 2016 (UTC)
Already took care of that on the editcopy. Just waiting for an admin to move it over. -BDJP (t|c) 04:49, 27 December 2016 (UTC)
It seems to me that the "Fire TV Edition" is literally just the same thing, but they renamed the app? In which case it should simply replace the original FireOS icon. MajrTalk
Contribs
23:21, 29 December 2016 (UTC)
Fire TV Edition is the same thing, but it's a completely new adaptation of PE for the Fire TV. The FireOS version of PE was originally compatible with the Fire TV, but as of December 19, 2016, a separate "Fire TV Edition" became available. Basically,  No, I don't believe the FireOS icon should be replaced. -BDJP (t|c) 01:26, 30 December 2016 (UTC)
Also the version sold on the Amazon store for the Kindle is still branded as Pocket Edition. – Sealbudsman talk/contr 03:54, 30 December 2016 (UTC)
Yeah, I figured that out after initially posting the main post. But doesn't that mean that the Fire TV logo should be added to the homepage ALONGSIDE the Fire OS icon? Since they're separate editions, they should both be listed separately there, shouldn't they? (I'm talking about the "Play it!" section on the homepage with the icons for each of the MCPE editions and their current versions.)
SuperGeniusZeb (talk) 17:09, 30 December 2016 (UTC)
I see, so PE is still being supported on other FireOS devices, it's just the Fire TV which has been split into its own edition? MajrTalk
Contribs
06:35, 31 December 2016 (UTC)
Exactly.
SuperGeniusZeb (talk) 02:24, 1 January 2017 (UTC)
Same as what BDJP007301 said. I wouldn't be so sure that PE is discontinued from FireOS entirely. I haven't purchased it on my Kindle (my only Amazon device), but I can confirm that Pocket Edition 1.0 is still being sold in my Kindle's Amazon store without notice of any kind. – Sealbudsman talk/contr 21:16, 26 December 2016 (UTC)
See my above response to BDJP007301. :S
SuperGeniusZeb (talk) 04:12, 27 December 2016 (UTC)
Well, until we work out a solution, I have moved Pi Edition to the Computer section after the PC Gamer Demo label. See Template:Minecraft for precisely what changed. Thanks, Maethoredhel (tcLogs) 22:51, 26 December 2016 (UTC)
Pi Edition is based on Pocket, though, see references on the Pi Edition page. When SuperGeniusZeb mentioned Pi, he was saying that since that is PE, then Education Edition should be as well -- but BDJP007301 already did make that happen. I think everything raised is handled, so far, except for the Minecraft 4k. – Sealbudsman talk/contr 23:08, 26 December 2016 (UTC)
That's fine by me. I will leave your reverted edits in place, as I think I misread some sections at that time. Thanks for clearing it up for me. Maethoredhel (tcLogs) 15:07, 3 January 2017 (UTC)

My vote is that Minecraft 4K should be moved to the PC section--SamGamgee55 (talk) 18:46, 27 December 2016 (UTC)SamGamgee55

The PC section in what template(s) / page(s)? I see it's already among the PC versions in {{Minecraft}} and in {{Computer versions}}, is there anywhere else? – Sealbudsman talk/contr 19:17, 27 December 2016 (UTC)
Now that I think about it... is Minecraft 4K even a Minecraft edition at all? It's really more of a standalone quick coding project based off of Minecraft. It never has had any updates, it never has been called an edition, and I feel like it belongs in the category of spin-off games or something. (Like Minecraft: Story Mode, perhaps?)
The Computer, Pocket, & Console editions are all working towards the same general game. And the Pi & Education Editions are both essentially modified (heavily in the case of Pi) versions of Pocket. Minecraft 4K was never intended to be a full game or an "edition" of Minecraft", just like Minecraft: Story Mode ISN'T a "story mode" for Minecraft. Neither of the 2 games are Minecraft, in my opinion. They're just a Minecraft-inspired coding challenge entry & a point-&-click spin-off game. So I think Minecraft 4K should either be moved to the "Other" category where Story Mode is, or both it & Story Mode should be moved to a "Spin-Offs/Related Games" category or something like that. SuperGeniusZeb (talk) 16:38, 2 January 2017 (UTC)
 Agree with SuperGenusZeb.--SamGamgee55 (talk) 00:06, 3 January 2017 (UTC)SamGamgee55
 Agree also. – Sealbudsman talk/contr 01:00, 3 January 2017 (UTC)
 Done. -BDJP (t|c) 02:50, 3 January 2017 (UTC)

Is there a standard for displaying radially symmetric schematics?

I ask because I've got an automatic omnidirectional TNT cannon design that fires every 4 ticks that I'd like to share, but I'm not sure how to best do that, especially with only having the PS3 edition.

On another note, would D#x# be an acceptable standard for describing the dimensions of vertical cylindrical spaces? Because the tower's designed to fit within a cylinder. The D stands for diameter. (I imagine #xD# would indicate a horizontal cylindrical space, but I don't have an example of why that'd be useful.)

LordTeague (talk) 22:31, 26 December 2016 (UTC)

As for using notation in symbols, such as 'D#x#', to describe a blueprint, I don't believe that's something the wiki does, correct me if I'm wrong. There are {{BlockGrid}} and {{Layered blueprint}}, which are templates to display blueprints of structures, and are used in a few places. If you check out the Structure Blueprints Project, there are some pages in there that have good examples of how {{Layered blueprint}} is used.
I know you are asking about radial symmetry, but typically when using these particular templates, the layers are spelled out in full, rather than just showing some angular section. Perhaps this isn't the type of answer you're looking for, but please clarify if not. – Sealbudsman talk/contr 23:21, 26 December 2016 (UTC)
Oh wait. I see on your sandbox page, you're using {{schematic}} templates, is that right? If so, are you proposing a new way to use that template? – Sealbudsman talk/contr 23:24, 26 December 2016 (UTC)
Yeah, C marks the center of the schematic on that page and the idea is you'd reference a single part of the schematic to build the 'edge' of the design, with data (white wool) blocks showing where the two parts join together. It's a redundancy (and load times) vs coherency issue as far as I see it.
Sometimes it might be useful to specify whether a circuit is designed to fit in a cylindrical space though, and it's typically easy to extrapolate to other dimensions. D21x4 can also mean 21x21x4, but not the other way around. Diameter is used rather than radius to avoid half block values. – LordTeague (talk) 12:52, 27 December 2016 (UTC)
Are you using the "Show Preview" button, and keeping an eye on the "Parser profiling data" section? It seems that, for instance, User:LordTeague/sandbox#R-D-M-L Diagonal Right Reverser is using an appreciable amount of computing, but nowhere approaching a limit, at least for what's there. If you find your schematic ends up being too costly, I'm sure your solution of describing section-by-section and using notation like D#x# is just fine, as long as you describe clearly what you're doing. – Sealbudsman talk/contr 19:14, 27 December 2016 (UTC)

Interwiki prefix codes

We have a number of interwiki prefix codes in use on our site, such as wordofnotch:, jebtweet:, wikipedia:, wikia:, and so on -- plus the language ones, like de:, es:, and so on. Are these listed out anywhere, for reference? It would be so nice. – Sealbudsman talk/contr 20:31, 27 December 2016 (UTC)

Special:Interwiki. --AttemptToCallNil, previously known as GreenStone (report bug, view backtrace) 20:34, 27 December 2016 (UTC)
Thanks! – Sealbudsman talk/contr 20:38, 27 December 2016 (UTC)

Texture pack dlc

This page is Console Edition only as the main page is Texture pack, which is only available in Console. But then, Pocket Edition also has texture pack dlc, but doesn't have an actual texture pack like Console, in Pocket Edition it was resource pack instead of texture pack. This makes me a little confused, cause where does the texture pack dlc page belong for Pocket Edition? - ItsPlantseed ItsPlantseed | Book and Quill 07:17, 31 December 2016 (UTC)

2017

File:1.11.2update.png

Happy (three days late) New Year! Maethoredhel (tcLogs) 20:30, 3 January 2017 (UTC)

File:Grid Dragon Head.png! The BlobsPaper 21:32, 3 January 2017 (UTC)

Enchanting disambiguation page

There are many enchantment names that could refer to something else. Examples include:

  • "Fire Protection" could be confused with the status effect Fire Resistance
  • "Mending" could refer to item repair or anvils

There are enough of these that it would lead to too many uses of {{redirect}}. Instead, we would have a page with a title like "Enchanting/Disambiguation", which includes these potential confusions. On the enchanting page, there would be a dablink with a link to the disambiguation page. Should we have this page? The BlobsPaper 00:34, 5 January 2017 (UTC)

 Support: The proposed page would help readers differentiate between the multiple uses you have stated. Maethoredhel (tcLogs) 00:58, 5 January 2017 (UTC)
 In progress I created a page in my userspace. If we get more agreement and the page is finished, I will move it to the mainspace. The BlobsPaper 19:30, 6 January 2017 (UTC)
How would the dablink on the enchanting page read? – Sealbudsman talk/contr 18:29, 10 February 2017 (UTC)

Widgets

Could we have a page in the Minecraft wiki namespace that documents all widgets? The BlobsPaper 15:15, 14 January 2017 (UTC)
I remember a page like that, but I forgot what it was called--SamGamgee55 (talk) 22:49, 16 January 2017 (UTC)SamGamgee55

Majr created the widgets, so he/she would know if such a page exists. The BlobsPaper 01:03, 19 January 2017 (UTC)

Not in Pocket Edition

There are quite a number of mainspace articles that describe features, game mechanics, etc. that don't currently exist in Pocket Edition. I think it would be helpful if we had a hatnote and category for this. Or is there one and I just didn't find it? – Auldrick (talk) 20:25, 16 January 2017 (UTC)

Found a project addressing this, but it hasn't been active for over 3 years. It was probably too much for the single user who proposed it. I'm looking at something smaller, just tagging those pages that PE users can ignore for now. – Auldrick (talk) 20:49, 16 January 2017 (UTC)
The issue is not no one has come up with the idea, the issue is users putting in the effort to highlight the specific information. I would start with proposing a specific way to handle the information (I would personally advise a version containing the feature system rather than listing ones that don't) and get some approval. You might want to look at some of the older topics for ideas as well. KnightMiner · (t) 21:46, 16 January 2017 (UTC)
#Version ID in items (above) talks about the same thing. Also Template_talk:Desktop.
Knightminer is right in that no one's made it their priority. I think it's been discussed to death though...
People mostly like the idea of using the {{only}} tag in the article lead. They like the idea of using a line in the infobox a little less, and they like the idea of using those {{pocket}} and {{console}} tags and a new one for the Java edition least of all.
If you want to spearhead this, then using the {{only}} tag everywhere seems to have people's support, or at least hasn't raised objections yet. – Sealbudsman talk/contr 22:23, 16 January 2017 (UTC)
Would it be possible to add a {{not}} template in addition to the {{only}} template, which clearly denotes that this feature is not present in that version? As an avid MCPE player I'm likely to start adding either template to related sections/features when passing by. Holroy (talk) 19:06, 13 April 2017 (UTC)

Potatoes

(old discussion for reference) Given that we have merged raw and cooked fish, I would like to propose a merge between raw and cooked potatoes. This is different from merging other raw and cooked food because of Majr's point that it is all or nothing; we would merge Poisonous Potato as well. The BlobsPaper 21:01, 18 January 2017 (UTC)

Is there a compelling reason they should be merged? – Sealbudsman talk/contr 22:50, 18 January 2017 (UTC)
My thinking is that since we have done a merge between raw and cooked food for Fish, readers might be excpecting other raw and cooked food to be merged. The reason I am mentioning potatoes separately from the other discussion is that merging in Baked Potato would mean merging in Poisonous Potato. The BlobsPaper 00:55, 19 January 2017 (UTC)
I could create an example page. The BlobsPaper 04:11, 24 January 2017 (UTC)
It would be good to see the example page, yes. – Sealbudsman talk/contr 18:20, 10 February 2017 (UTC)
 Done I created User:Blobs2/Anvil/Potato. The BlobsPaper 22:23, 10 February 2017 (UTC)
 Support, reduces the amount of content overlap. GoandgooTalk
Contribs
13:12, 29 April 2017 (UTC)

Add CraftMaster to Programs and Editors pages

CraftMaster is a new Minecraft PC Edition companion app that runs on Windows and macOS. It was recently released to open beta - users can join the beta program at www.craftmastersoftware.com. Is it possible to get CraftMaster listed on the Programs and Editors pages of the Minecraft wiki? If so, how would we go about doing that?

Some background...CraftMaster offers a range of capabilities, including: 1) Contoured 2D/overhead maps of Minecraft worlds; 2) The ability to import 3D models, convert them to Minecraft structures, and place them (as well as any other schematic or structure) into Minecraft worlds using Structure Blocks; and 3) The ability to extract structures from Minecraft worlds and share them as 3D models on Sketchfab and, from there, on social media sites such as Facebook, Twitter, and Tumblr.

As a result, CraftMaster spans to multiple Programs and Editors categories, including Mappers, Map Editors, and 3D Exporters.

We can provide content for the wiki pages and/or edit the pages directly...whatever is most convenient.

--CraftMasterAndy (talk) 19:21, 24 January 2017 (UTC)

 Support You could create the page. If an abuse filter prevents you from doing so, you can try again when you are autoconfirmed. The BlobsPaper 20:09, 24 January 2017 (UTC)

Links to client/server jar/json in Version article info boxes

In all the version articles, in the info box, we've been putting links to download the servers, clients and json files from s3.amazonaws.com. However today, Dinnerbone reminded us on Twitter: "Custom launcher & tool devs: please ensure you're not using old http://s3.amazonaws.com/Minecraft.Download/ … anywhere. Moved to https://launchermeta.mojang.com/mc/game/version_manifest.json … last year" [1]

It appears, now everything is to be stored in hashed directories, for instance, https://launchermeta.mojang.com/mc/game/d74a4b45e8877084e1bcc8121012845f28def238/1.8.json. We won't be able to use the "simple" pattern, https://s3.amazonaws.com/Minecraft.Download/versions/<version>/<version>.jar, in use until now.

Once they drop the amazon hosting, old snapshots will just be unavailable. I'm thinking at this point, why even link to these locations, if they're not going to be stable; it'll just be an unnecessary maintenance hassle to keep up with broken links.

What do people think? Let's just not have a download link. – Sealbudsman talk/contr 17:32, 7 February 2017 (UTC)

 Support The content is also rather technical; most readers would ignore the link. The BlobsPaper 17:36, 7 February 2017 (UTC)
I have found the old snapshot jars very useful in the past, actually. They are good for when a historical question needs to be resolved, for clarifying or filling out a history section. They are good for on the bug tracker, getting insight on when a bug first started and how it's evolved. It's technical nature isn't so much what's at issue as its maintainability or stability going forward.
So on the other hand, as a counterpoint to what I initially said, perhaps the URLs going forward will be stable. Perhaps they won't dump older snapshots. Perhaps we just update our links and see what happens. – Sealbudsman talk/contr 18:15, 7 February 2017 (UTC)
 Oppose removal IMO getting rid of them entirely is a bad idea (it's technical information that has little use to most people, but I've found it useful occasionally, especially for snapshots).  However it is worth noting that old snapshot JARs are available on the new site, just via hashed locations. Only the JSONs seem to be unavailable. For instance, https://s3.amazonaws.com/Minecraft.Download/versions/14w02a/14w02a.json points to jars on the new location:
    "downloads": {
        "client": {
            "sha1": "16fd472f9634bf49d051e4d84676fe4a5498cd14",
            "size": 5286446,
            "url": "https://launcher.mojang.com/mc/game/14w02a/client/16fd472f9634bf49d051e4d84676fe4a5498cd14/client.jar"
        },
        "server": {
            "sha1": "b908214fb99891c4f1e77c21b1fcbe4f7cafdd58",
            "size": 9221694,
            "url": "https://launcher.mojang.com/mc/game/14w02a/server/b908214fb99891c4f1e77c21b1fcbe4f7cafdd58/server.jar"
        },
        "windows_server": {
            "sha1": "6071c89c09e3b8172f09c71bcc36465c1863e800",
            "size": 9617470,
            "url": "https://launcher.mojang.com/mc/game/14w02a/windows_server/6071c89c09e3b8172f09c71bcc36465c1863e800/windows_server.exe"
        }
    },
However, version JSONs themselves are not currently present on launchermeta. The pattern does seem to be guessable, though: take the 1.8 version JSON:
    "downloads": {
        "client": {
            "sha1": "d722504db9de2b47f46cc592b8528446272ae648",
            "size": 7746841,
            "url": "https://launcher.mojang.com/mc/game/1.8/client/d722504db9de2b47f46cc592b8528446272ae648/client.jar"
        },
        "server": {
            "sha1": "a028f00e678ee5c6aef0e29656dca091b5df11c7",
            "size": 10375504,
            "url": "https://launcher.mojang.com/mc/game/1.8/server/a028f00e678ee5c6aef0e29656dca091b5df11c7/server.jar"
        },
        "windows_server": {
            "sha1": "73e0862463b91a6a5aea29da58f85ef1e7915c83",
            "size": 10769744,
            "url": "https://launcher.mojang.com/mc/game/1.8/windows_server/73e0862463b91a6a5aea29da58f85ef1e7915c83/windows_server.exe"
        }
    },
Specifically, note that the client SHA is d722504db9de2b47f46cc592b8528446272ae648 Then, also note that the directory name for the 1.8 version JSON is also d722504db9de2b47f46cc592b8528446272ae648 (the hash of the file itself is something different). So version JSON paths will be guessable with the client SHA. (FYI: I'm 99% sure mojang avoids changing the client file itself, so that SHA should remain mostly constant forever. They do change the version JSON, though, when they need to change things (such as updating the realms library)).
As such, I propose that the template is changed to take SHAs of the client, server, and windows server in addition to a version name, and then generate the links from that. Since currently version JSONs are unavailable for snapshots, the s3 JSON should still be linked for the moment; if snapshot JSONs get put back on launchermeta that should be easily changeable. Downloads of the actual jars should be changed to use launcher.mojang.com, and the s3 links for the jars should no longer be generated. How does that sound? --Pokechu22 (talk) 19:18, 7 February 2017 (UTC)
Pokechu22, would you be willing to compile this list of versions and their hashes, for whatever ones we still have access to? I support your idea. – Sealbudsman talk/contr 22:36, 7 February 2017 (UTC)
 Working on it Sure, I can do that (probably by using the S3 JSONs). It'll take a little while to do so though. --Pokechu22 (talk) 22:46, 7 February 2017 (UTC)
Turns out I made a mistake. The version JSON hashes are not the same as the client hashes (it's just a coincidence that the first 2 digits and last digit of 1.8 match). Which means that 1) probably the other JSONs still exist on launchermeta, but 2) there's no way to find them until we can figure out what those hashes are of (or an index of snapshots is added). On the other hand, I did find that multimc has been keeping an an archive of the older manifests, which is useful data in that it shows that the hash for a version JSON doesn't change when the JSON itself is updated. I'll keep trying to figure out what the hash is, though. (I have archived the client/server hashes and links, which do still follow a pattern; it's only the JSONs that need to be figured out) --Pokechu22 (talk) 01:01, 8 February 2017 (UTC)
Thanks for keeping us updated, and for your interest and work on this. – Sealbudsman talk/contr 16:05, 8 February 2017 (UTC)
2017-02-08 01:54:07	pokechu22	Does anyone know what the key on version JSONs is (such as '12f260fc1976f6dd688a211f1a906f956344abdd' in https://launchermeta.mojang.com/mc/game/12f260fc1976f6dd688a211f1a906f956344abdd/1.11.2.json)?  It looks like a SHA1 hash, but it's not a hash of the file contents (neither the original or latest versions) and I can't figure out what it actually is.
2017-02-08 09:50:30	+Dinnerbone	pokechu22: something to make the url static between modifications of files, but unique so that it's unguessable
(source: #mcdevs log 110) - got some additional information about it. Basically I'm interpreting this to mean that we could store the identifier for the JSON and link with that, but can't manually calculate it other ways. So my proposal is mostly the same as before, except we'd also need to add the JSON hash, which won't be too hard for versions where it is known or archived (which includes the april first snapshots, the most interesting of the snapshots to archive); if a more complete list for older snapshots is created then we can add those versions. I'll work on building a list of all of the hashes for versions where they are known. --Pokechu22 (talk) 06:18, 10 February 2017 (UTC)

Slicedlime

Does anybody know his (her??) name, and have a source on that? I created a slicedlime page, and it's a little awkward to not have a name. – Sealbudsman talk/contr 21:35, 10 February 2017 (UTC)

The name "Mikael Hedberg" given by this editor appears to check out. The twitter profile @slicedlime mentions "Ex-DICE: Lead Programmer, Scripter on Battlefield", and the Google+ profile for Mikael Hedberg / slicedlime indicates these same things, and living in Stockholm. There is also a github page for Mikael Hedberg / slicedlime indicating many of the same contact details as on the Google+ profile, and same profile pic as on Twitter. Either there is a giant multi-year hoax being perpetrated or this is the guy. Sealbudsman talk/contr 20:37, 16 February 2017 (UTC)
Found a citable source (rather than a maze of inferences): in the info section below this video, https://www.youtube.com/watch?v=CdCsXuKeOn4, he introduces himself by name and as slicedlime, and corroborating that, he uses the first person to suggest we follow him on twitch, and links us to the same twitch that is linked on @slicedlime twitter. – Sealbudsman talk/contr 20:53, 16 February 2017 (UTC)

List of mobs & Platform availability

Mob's page's List of mobs and Platform availability should I add Education Edition's Mob (NPC and Learn to Code Mascot)?--User:Beans1512/Sign 08:40, 19 March 2017 (UTC)

They should be added, under an "Education Edition only" section.
Also, please use "Add topic", and do not use templates in signatures (use {{SUBST:User:Beans1512/Sign}}). The BlobsPaper 00:07, 20 March 2017 (UTC)
Personally, I think that it is better to add [Education Edition only] to the Passive mobs clause and add it. For now, I will add it to Platform availability.--User:Beans1512/Sign 01:54, 20 March 2017 (UTC)
Also, let's talk about the signature here.--User:Beans1512/Sign 05:21, 20 March 2017 (UTC)

Links in version pages

It seems that there is disagreement in the 1.12 page on whether "Parrot" should be linked. I would not support such links because people will follow the link expecting to get more information, and they are redirected to the page they were on. The BlobsPaper 00:56, 25 March 2017 (UTC)

 Agree My judgment at that time was wrong.--User:Beans1512/Sign 01:07, 25 March 2017 (UTC)
The problem is having links which redirect back to the page the links are on. There is no problem with just having a redlink when we're going to be creating an article there anyways; Wikipedia, for example, explicitly encourages redlinks to be added to articles in this case. ディノ千?!? · ☎ Dinoguy1000 01:45, 25 March 2017 (UTC)
First of all, I think that it is better to display it like "Parrot" without linking.--User:Beans1512/Sign 01:50, 25 March 2017 (UTC)
 Support The BlobsPaper 04:00, 25 March 2017 (UTC)
Why? If it's getting an article anyways, there's no reason not to have the link beyond personal preference. ディノ千?!? · ☎ Dinoguy1000 09:37, 26 March 2017 (UTC)
I think that it is better to create the page of "Parrot" since it was implemented. Also, as there is little information now, there is no need for a page.--User:Beans1512/Sign 10:03, 26 March 2017 (UTC)
That has no bearing on whether we should allow redlinks. As for the page, it has information and it will be expanded as more information becomes available, so there is no reason to delete it. ディノ千?!? · ☎ Dinoguy1000 10:06, 26 March 2017 (UTC)
It has something to do with the story after the decision to make it bluelink. Bluelink does not have meaning of the page as described above. On the contrary, it looks bad with redlink. Therefore, I think that it is best not to attach a link.--User:Beans1512/Sign 10:20, 26 March 2017 (UTC)

Console Edition versions

I think that there is a version page in Computer Edition, Pocket Edition, but it is strange that there is no version page in Console Edition. Therefore, I think that it is better to enrich the version page, but what do you think?--User:Beans1512/Sign 07:42, 6 April 2017 (UTC)

There is a different console edition for each type of console, so it would be impractical to have individual version pages.
Again, please use "Add discussion" rather than editing a section. The BlobsPaper 13:59, 6 April 2017 (UTC)
impractical: There are also versions of Pocket Edition that have different release dates? (TU, CU, Patch are different.)
Add discussion: Where is "Add discussion"? (Sorry if that was what you were telling me before.)--User:Beans1512/Sign 22:31, 6 April 2017 (UTC)
A picture of the mobile talk page can be found here. The BlobsPaper 23:20, 6 April 2017 (UTC)
It is also seen on the user talk page. But, I do not know how to get there.--User:Beans1512/Sign 03:43, 7 April 2017 (UTC)
On user pages, the link is at the top of the page rather than the bottom. The BlobsPaper 03:47, 7 April 2017 (UTC)
I know that.--User:Beans1512/Sign 03:49, 7 April 2017 (UTC)

Pages from the German wiki

I just made a list of articles in the German wiki that could be translated and added in the English wiki as well. I wanted to ask whether the English editors are interested in those pages, as well as if somebody further than me would spend some time translating them. Iwer Sonsch (talk) 12:32, 10 April 2017 (UTC)

To varying degrees they do look interesting, I'll definitely glance over it at lunch today and make further comment (as well as your comments on Talk:Transportation and Talk:Health). Thanks! – Sealbudsman talk/contr 14:42, 10 April 2017 (UTC)
Account looks interesting, and I'm pretty sure we are missing that kind of page, or at least it's not where a person would look.
We do have a Tutorials/Falling blocks, a Breeding page and a Tutorials/Village mechanics page, as well as a whole suite of agriculture articles at Tutorials/Crop farming. It would be good to make a study of each and see what can be gained: information as well as organization. If you have any input on your how yours are organized versus ours, that would be good to hear.
I must be totally missing the point of your Tutorials/Stacking page -- what is its point, just stacking blocks, entities and whatever on top of one another? And methods for doing so? What is the motivation for why someone would want to do this?
As for Healing, we do have a Damage page which currently has healing information on it, though I don't see why we couldn't do a full Healing page, if it proves to be full of diverse information in its own right.
Menu subpages and biome subpages: I personally don't see the value in splitting it apart as far as the German wiki does, maybe you have some comment on that.
Myths: I don't think this will fly, because it documents community-generated and/or speculative content, both of which we simply don't do. We do have an uneditable Herobrine page, but I think that is our one exception, or something like that.
Fog, I am definitely in favor of making: we have no such page.
Redstone signal: it sounds like a valuable tutorial page, or if made strictly enough, a full feature page. I don't see its match in our Basic Redstone tutorial section, though I'd want to be sure; we might have a page like that buried somewhere, not categorized well. – Sealbudsman talk/contr 15:47, 10 April 2017 (UTC)
Looks like Account is going to be one of our next projects.
I totally overlooked the Tutorials/Village mechanics page, it says pretty much everything mentioned in the German article.
The Tutorials/Falling blocks page, on the other hand, says absolutely nothing about the falling blocks themselves. That information is 100% spread out over the articles about Gravel, Sand, and Anvils.
 Yes Breeding only describes the mechanics of breeding, and not how to use them. This is why the German wiki has two articles, Viehzucht and de:Anleitungen/Viehzucht, to cover both of the topics.
The German article about Agriculture contains information about a huge lot of different crops to farm, and it looks like the English articles about those farms are just very spread out, but seem to contain anything but the flower farm and the chorus fruit farm. What could be done, though, would be another disambiguation that displays only the various crop farms.
Agreed, an article about Stacking really isn't the most important topic in the Wiki. It wasn't even there until this month.
Healing is the largest page I've created so far, and I'm proud to offer it to the English wiki as well.
I agree that menu subpages and especially commands subpages are a matter of choice, but the pages about the biomes are what I really miss in the English wiki. At least the main biomes are so full of information that it doesn't anywhere close to fit in those little paragraphs - and so the German wiki is (and should not be) the only one to provide some important details that the English editors just can't seem to fit in.
I don't really get the point why this page wouldn't fit into the English wiki. Since the English wiki already contains an article about the non-existant Herobrine, it should be possible to include another imaginary-themed page with the same disclamer.
Okay, let's start working on the page about Fog.
So we are going to triple-check whether this page actually doesn't exist and if so, we are going to add it.
-- Iwer Sonsch (talk) 17:28, 10 April 2017 (UTC)
I do like the way the German biome sub-pages are nicely divided out into a relatively small number of biomes, avoiding the mayhem of having a page for every single one. It seems well-arranged. I'm not totally convinced on the menu sub-pages though.. I see the menu as pretty self-explanatory, though perhaps if I translate and read the German on that I'll be surprised? You mention command sub-pages (maybe you meant to mention it before?) -- I really don't think we have a space problem with the commands page, since we recently moved away from using a table, which was the real thing constraining it. I wouldn't favor splitting it; I feel it's more useful as a single (if lengthy) list.
You are right in your criticism of our falling blocks page, I think. Because it is nothing more than a description, and simply a how-to, that is probably why it was fated to remain merely a Tutorial page.
I read Myths, and I revise my opinion. The great majority of items on that page (I think all except Herobrine) are basically corrections to misconceptions, it looks to me. Not necessarily "community content" as I thought. Another way to handle that kind of information is to include it on appropriate Block, Item or otherwise feature pages. I often add such content: someone on reddit expresses some kind of misconception, and I discover that the wiki was not able to correct that person -- so I will sometimes try to word things more precisely or more elaborately. Anyway those are my comments on that.
Can you just make the pages in your userspace for now, and link here, so we can see and feedback and help and comment?
Though I can't imagine anyone complaining about a Fog or Healing or Account or Redstone Signal page, let's get more feedback on this, too, I don't speak for everyone. – Sealbudsman talk/contr 19:50, 10 April 2017 (UTC)
I already agreed on the ommision of adding menu and command subpages. I only meant to say that both the English and German wiki are right at that point because in these cases, both options are about equally good.
I am glad that we now seem to agree on the Biome subpages, though, and I'm surprised about how many of the pages that I would have consideres less important like Fog or Myths (I only defended it because your argument didn't convince me) we are actually planning to include by now.
For translating the pages into my userspace, that's what I thought of as well. I think I have in theory 10 pages available at once, but I don't know if that's 10 in total or seperated per language. I think I won't need to find out either though.
Maybe tomorrow. It's almost night in Germany. Iwer Sonsch (talk) 20:31, 10 April 2017 (UTC)
Healing is translated completely, as well as the disambiguation, though, somebody will have to check over the templates.
In addition to that, the German wiki recently finished the (needed?) page on Burning. I might want to translate that as well if somebody supports that. Iwer Sonsch (talk) 17:34, 13 April 2017 (UTC)
I like it, and the Burning page as well. I hope you don't mind but I cleaned up a few more things on the Healing page. – Sealbudsman talk/contr 17:57, 13 April 2017 (UTC)
On the contrate. I totally mind that somebody cares about changing understandable English into good English whenever a page is meant to make its way into the Article Name Room (ANR). Iwer Sonsch (talk) 20:11, 13 April 2017 (UTC)

Request for baby villagers renders

I realised that baby villagers is just rescaled model of their parents...so why don't we just use the normal villagers pngs for babies in the infobox? Oakar567 (talk) 15:43, 17 April 2017 (UTC)

The PE village babies have larger heads, I think that's why it was requested. – Sealbudsman talk/contr 15:56, 17 April 2017 (UTC)

Resizing the witch and villager images

Beans1512 why do you request to change the image size of the villager and witch files, I am not sure i understand – Sealbudsman talk/contr 05:08, 23 April 2017 (UTC)

It is because I thought "It is better to unify the size of mobs resembling villagers and villagers to the size of illagers."--Beans1512Talk/Contribs 05:17, 23 April 2017 (UTC)

Fixes in development versions

Goandgoo suggested that on development versions pages, the "Fixes section should be divided to distinguish between bugs from other development versions and bugs from normal versions. I would support doing this, but we need to decide on what to name the sections. My idea is to have one called "From previous versions" and another called "From previous development versions". The BlobsPaper 14:00, 30 April 2017 (UTC)

In places where we use the {{fixes}} template, which is mainly PC snapshot pages, it's set up to do exactly that, for exactly the purpose Goandgoo is describing. Sections used on snapshot pages are: "from released versions before 1.x", "from 1.x development versions", and "from the previous development version". The first two section names could be used. I don't know that I care what named are used, as long as there is consistency – Sealbudsman talk/contr 15:32, 30 April 2017 (UTC)
Maybe we can use the template on version pages besides PC. The BlobsPaper 16:46, 30 April 2017 (UTC)
We could, in cases where the Fixes section is composed of links to the bug tracker. In this case though, HelenAngel is putting together lists of bug fixes that don't necessarily have those links. The template wouldn't be an exact fit in this case. – Sealbudsman talk/contr 00:01, 1 May 2017 (UTC)
Yes, the only reason I brought that up is that unlike the PC where all the fixes are linked to the tracker and thus it is easy to distinguish what the fixes relate to, for the Pocket Edition the developers are releasing huge changelogs with hundreds of changes without being linked to the tracker or with any reference as to which versions they fix. GoandgooTalk
Contribs
13:45, 1 May 2017 (UTC)

Minecraf EDU

Hey All,

I'm new to Minecraft and i'm getting ready to start using it in the classroom. My students have their logins and have been doing "free play" for the last week to get accustomed and excited. I'm wondering if I can create multiple worlds that run at the same time. I teach middle school so I have 3 classes of 36 students. I want to put the kids into small groups in a separate world. Is this possible?

Thanks –Preceding unsigned comment was added by 207.157.136.112 (talk) at 19:31, 08 May 2017 (UTC). Please sign your posts with ~~~~

You want to review the Education Edition FAQs and knowledge base, or visit the forums for that edition.
This page is a general discussion board for/about the wiki itself. And, due to Education Edition licensing, I would be surprised if anyone here were familiar enough with that edition to know the answers to that. Good luck! – Sealbudsman talk/contr 22:33, 8 May 2017 (UTC)
Why would the education edition require special licenses? The BlobsPaper 00:52, 9 May 2017 (UTC)
I guess maybe it's because they're keeping the Education product separate from their other Minecraft game products? For what ultimate reason I'm not sure. – Sealbudsman talk/contr 03:06, 9 May 2017 (UTC)
I think I remember seeing that EE licensing involves a per-student fee. That would require a separate license, since there's nothing equivalent in the PE license. – Auldrick (talk · contribs) 07:48, 9 June 2017 (UTC)

Extend the breaking time chart in the Obtaining section of articles to take enchantments and Haste into consideration

Currently it only displays different tool tiers. It would feel a bit more complete if it were to be expanded into a table of some sort with survival-obtainable levels of Efficiency and Haste additionally listed (which could possibly be hidden by default). Any thoughts? - MinecraftPhotos4U (talk) 21:30, 25 May 2017 (UTC)

The breaking page already tells the percentages applied by enchantments and status effects. Putting them on block pages would make the table too complicated. The BlobsPaper 00:48, 26 May 2017 (UTC)
Is that much data actually useful? There are six possible levels of Efficiency, and three of Haste (including not having the effects), so this would expand the 1x6 table we have now into a 18x6 table. -- Orthotopetalk 03:43, 26 May 2017 (UTC)

Slovenian translation

I want to translate pages on this wiki to Slovenian language (I'm from Slovenia), but I don't know how to start. Can somebody tell me how to create translation of the pages? –Preceding unsigned comment was added by 89.233.116.58 (talk) at 17:36, 02 June 2017 (UTC). Please sign your posts with ~~~~

There are projects for other translations. Look at them for ideas on a Slovenian translation.
If you plan to make these edits, it would be recommended to create an account. The BlobsPaper 14:45, 3 June 2017 (UTC)

The terracotta mess

So, can someone explain what is happening with the Hardened Clay page?

Cam275yt, not only you moved the page to the project namespace, you made a triple redirect and made it impossible to just move that page back.

Nixinova, you tried to fix it.

And finaly Hubry (also known as me) - you tried to fix it as well and probably messed it up more. -- Hubry (talk) 20:09, 4 June 2017 (UTC)

Okay, I think I've fixed it. User:Cam275yt moved the page multiple times to some random page and left redirects everywhere. I dont even know – NixinovaGrid Book and Quill Grid Diamond Pickaxe Grid Map • 20:11, 4 June 2017 (UTC)

Hey it's me, Cam275yt. I tried to move to Terracotta as it is called that now, but there was an already-existing page for it. I completely screwed it up. :/ –Preceding unsigned comment was added by Cam275yt (talkcontribs) at 20:14, 04 June 2017 (UTC). Please sign your posts with ~~~~

@Cam275yt:: It's not yet called Terracotta - PC is updating Wednesday, that will be time of page moves. Also you moved it to a wrong namespace at the end. Also, please leave moving pages to people more experienced. To be honest I don't feel comfortable at all with all these moves I just did, and you have less than 20 edits... --Hubry (talk) 20:19, 4 June 2017 (UTC)
Okay, I think everything is back where it should be. I'll move it for real once 1.12 is released.
In the future, if a page move doesn't turn out the way you want it to, the best thing to do is move it back to where it originally was and ask more experienced editors to help. Most moves here will end up needing an admin anyway, since all the /video subpages are protected. -- Orthotopetalk 20:35, 4 June 2017 (UTC)

"Johnny" vindicators

The Vindicator and Name Tag articles both say that naming a vindicator "Johnny" causes it to become hostile to all mobs except other vindicators and evokers (but including vexes). Now that 1.12 has introduced the illusioner illager, I'm speculating that it is likewise exempt from Johnny attacks, but I don't have MCPC and the illusioner isn't in MCPE yet so I can't test it. Would somebody else please test it, for the sake of accuracy? – Auldrick (talk · contribs) 01:05, 8 June 2017 (UTC)

Illusioners are indeed not attacked by vindicators named "Johnny". --Pepijn (talk) 01:19, 8 June 2017 (UTC)
Thanks, I'll update the pages. – Auldrick (talk · contribs) 01:21, 8 June 2017 (UTC)

Minecraft, Java Edition, and the orientation of the wiki

So going forward, the edition you'll find on Xbox One, Nintendo Switch, mobile and VR will simply be known as 'Minecraft', a separate entity from 'Minecraft: Java Edition', which is the original PC game (that we'll continue to support, of course).

https://minecraft.net/en-us/article/all-news-e3

The MCPE game is the one being ported to consoles, and it's the one being touted, focused on, and branded and sold now as simply Minecraft.

Does this call for a major reorientation of the language of the wiki? Is this the time?

Right now we have it so Java Minecraft is the standard, normal Minecraft, and everything that's on the MCPE game we're just calling Pocket, and marking those as exceptions. To match what Mojang/Microsoft are doing, we should change the language, I think, so that the MCPE game is just the normal Minecraft, and treat Java Edition differences as the exceptions. Of course I'm not suggesting a whitewashing; Java's historic precedence would be preserved in things like History sections, or articles that talk about the history of the game like Minecraft itself.

Examples:

  1. Instead of saying "In Pocket Edition the sleeping animation will slowly lower the player into bed," we might instead say "The sleeping animation will slowly lower the player into bed. In Java Edition there is no sleeping animation".
  2. When using table headers PC, PE, CE, instead use: MC, PC, CE (or something like that, but in that order.)
  3. Using Java Edition only name on things like the Data Values section.
  4. Possibly renaming things that are prefixed as Pocket Edition (Like Pocket Edition data values) so they are named in a first-class way, and moving Java Edition things to pages prefixed as Java Edition.
  5. Rewording and renaming templates of all kinds: {{Minecraft}}, {{Computer versions}}, {{Pocket Edition versions}}

However we choose to respond to this naming thing, I would urge lots of foresight, planning, the creation of a new project to coordinate the effort – before any action is taken. – Sealbudsman talk/contr 00:48, 13 June 2017 (UTC)

 Support In fact, it's past time we started doing this. Pocket Edition sales overtook PC sales over a year ago, if I'm not mistaken, and giving PC priority of place makes the wiki look like yesterday's news. – Auldrick (talk · contribs) 01:20, 13 June 2017 (UTC)
 Support Not only is Pocket Edition more popular than the PC version, but it may s missing a lot less features than it once did. For example, two years ago, the Nether and the End were missing. The BlobsPaper 01:26, 13 June 2017 (UTC)
I've been keeping a list of feature differences between Java and PE. I don't pretend it's comprehensive, but at 32 entries it's an awful lot smaller than it used to be. – Auldrick (talk · contribs) 01:44, 13 June 2017 (UTC)
 Info We also need to stop calling it the PC [edit: or Computer] edition. It will confuse users of the Windows 10 Edition on PCs. – Auldrick (talk · contribs) 01:29, 13 June 2017 (UTC)
I agree to that. – Sealbudsman talk/contr 01:34, 13 June 2017 (UTC)
 Agree. I'd suggest something like JE, which very uncommon to be used in the meanwhile, same thing to the history section, for example, "Alpha" → "Java Edition Alpha", "Release" → "Java Edition", and "Pocket Edition Alpha" → "Alpha", I think maybe?; well, we do not know yet about the version number of switch and xbone afterwards. If they will continue the previous type of version, such as "Patch 21", and "CU12", that would cause lots of sections in the "Unified Minecraft" history. – ItsPlantseed|⟩ 03:55, 13 June 2017 (UTC)
I think if we introduce JE, and Mojang continues to use Java Edition, people will know exactly what it means, so I don't really worry about that.
If switch and Xbox one versions get the bedrock ports, I was assuming they'd get the same 1.2, 1.3 etc updates, instead of the title updates and patches. But that would be good to nail down and verify! EDIT: nice signature, by the way! Sealbudsman talk/contr 04:12, 13 June 2017 (UTC)
Something that just occurred to me is that out-of-date Video sections are going to become even more of a problem than they already have been. Many are already flagged as inaccurate with respect to Java, but I don't think anybody has been doing the same for PE. We might have to re-watch them all at some point. Is there a complete list of them somewhere? – Auldrick (talk · contribs) 02:01, 13 June 2017 (UTC)
Auldrick, all of them can be found here.
Out of order, I'd also like to say that I  Support the decision for a rewrite of basically the entire wiki. I  Agree with Seal that a project should be created for this, and then we can begin it from there. Starting it too quickly would cause some definitive confusion amongst readers. -BDJP (t|c) 02:59, 13 June 2017 (UTC)
CrsBenjamin, I'm sure you have your own relationship to MS and Mojang, but just pinging you to make you aware we are contemplating reorienting to reflect the name change, should that affect your Video production. – Sealbudsman talk/contr 04:03, 13 June 2017 (UTC)
I have created the project: MCW:Projects/RenamingNixinovaGrid Book and Quill Grid Diamond Pickaxe Grid Map • 04:44, 13 June 2017 (UTC)
From my personal point of view, I support the reorientation of the wiki. However, the amount of work required to ensure the wiki is reorientated would be many times larger than that of the Rewrite for Style project, and far beyond the five examples listed above (I'm sure there will be many more things we haven't yet considered which will become issues as the rewrite progresses). Features in articles would need to be meticulously cross-checked, as there are numerous examples of feature disparities between versions which may not be comprehensively documented on the wiki.
A significant issue is that the majority of features have been tested on the Java Edition, and while we may assume that they work the same way in the Bedrock Codebase this will ultimately not always be the case. The Bedrock Codebase being slightly behind the Java Edition in terms of features, and the lack of many advanced features will ultimately cause problems which need to be solved down the track.
Essentially, a change of this magnitude would require a rewrite of pretty much every article on the wiki (the quick reference page could provide a good starting point), however this would also provide the opportunity to rewrite further articles and ensure all articles are kept up to date. GoandgooTalk
Contribs
14:24, 13 June 2017 (UTC)
No illusions about the size of it, believe me. I urge a central place to discuss and plan, before doing anything, because this will touch so many things. Nixinova has initiated a page at MCW:Projects/Renaming. A feature checking phase could be one very useful prong of it, I agree. Please, put down your thoughts on that project page, as you think of them! – Sealbudsman talk/contr 14:33, 13 June 2017 (UTC)
I support the idea of re-orienting the wiki, but the wiki rewrite should wait until the rebranding has actually been accomplished by Microsoft/Mojang. Press releases are the equivalent of snapshot updates -- they may or may not reflect the actual future and this would be a large project. Until then, there is prepatory work that could be done (identifying articles with version differences) that would still be useful even if this rebranding become vaporware (I don't think it will, but it might). —munin · Grid Book and Quill Grid Stone Pickaxe · 15:35, 13 June 2017 (UTC)
Advertisement