Minecraft Wiki 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.

This page is for community discussion; generally, wiki issue reports should go to MCW:Admin noticeboard and discussions about a single page do not belong here.



Add item icons to infoboxes where the item has a different texture than the block
Should we add item textures to infoboxes where the blocks/items have different textures? Pages like string, crops, campfire, bell, etc. I would also like to do this for entities, like boats and armor stands. It seems there was support for doing this with crops in above talk sections, and I personally would doing this for all items.

The main argument against this that I'm predicting is that there's an invsprite in the infobox showing the item textures. While this is true, item-only pages, such as diamond, have both the large icon and the invsprite. -PancakeIdentity (talk) 00:28, 10 November 2019 (UTC)


 * FVbico (talk) 00:30, 10 November 2019 (UTC)
 * as the full-sized images are quite useful for people quickly wanting to download texture files.  Nixinova  T  C  06:20, 10 November 2019 (UTC)
 * - the only reason that items display large versions of their texture files in the infobox is because that's the image that describes the item the best and there's no better image. Having a massive item texture there alongside the existing 3D render would just clutter the page and add nothing of value. - User-12316399 (talk) 13:56, 10 November 2019 (UTC)
 * "Would just clutter the page and add nothing of value" – This has never seemed to stop you before.  Nixinova </b> T</b> </b> C</b> </b> 04:48, 12 December 2019 (UTC)
 * for both blocks and entities. --Capopanzone (talk | contribs) 10:21, 11 November 2019 (UTC)
 * – don't see why not, especially for String which has many uses unrelated to its block form. – Sonicwave talk  00:56, 18 August 2020 (UTC)

Articles on Mojang staff and related persons - do we really need them?
Except for perhaps the most notable people, do we really need articles that get almost no editor attention and rarely exceed a couple short sentences? I don't see how most of them are even relevant. Even spin-off titles like Story Mode or Dungeons are more relevant, I think. --AttemptToCallNil (report bug, view backtrace) 18:56, 23 November 2019 (UTC)


 * I feel like, at best, we should try to expand the articles as much as possible, much like how Wikipedia does it with their policy on biographies of living persons, making sure that information about them is backed up be reliable sources. I do recall mentioning back in 2015 that we could possibly use LinkedIn profiles as a source for reliable information, though discussion never went anywhere beyond that. -BDJP (t 21:30, 23 November 2019 (UTC)


 * We mention devs pretty often in history sections, and it might be useful to have these pages in those cases. Especially when they commonly go by nicknames (i.e. Jeb or Dinnerbone). Other than that, I don't know. I would like to see the general staff page updated though. -PancakeIdentity (talk) 04:41, 27 November 2019 (UTC)


 * Other than the obvious ones I think there should just be an "employees" page that lists mainly job-related info; this also avoids the BLP issues we've had in the past.  Nixinova</b> </b> T</b> </b> C</b> </b> 06:03, 27 November 2019 (UTC)


 * I would support having a Mojang employees page, consolidating the short pages there, and having a link from there (after a brief overview) to longer pages like for Jeb. &#8212; Memetics  talk &#124; edits 22:42, 10 April 2020 (UTC)

Remove separate employee pages
This wiki tries to create a page for every single Mojang employee, yet the vast majority are either redlinks or one-line stubs. This is hardly useful, and really the only information you need is name, date of employment, and job title, which can easily be done in just a table. It would be so much easier to maintain employee pages of they were all just in a table instead of spread out across hundreds of pages. Additionally, this leads to the wiki coming across BLP issues (eg: ez) and not having proper policy on how pages on people should be handled (we're not Wikipedia). These issues can be easily solved by migrating all employee information into e.g. Employees(yes, plural). Excepting, of course, very notable employees like Notch.  Nixinova </b>  T </b>  C </b>  05:50, 24 July 2020 (UTC)


 * I would support removing pages for employees that have hardly any information. There is currently a table at Mojang Studios, which could be split into a separate page and get additional columns for join date and other notable Minecraft-related info/trivia. (Also see the previous discussion on this topic.) – Sonicwave talk  17:40, 24 July 2020 (UTC)
 * I agree, like whats the point of making these tiny stub pages that almost no one goes to? Completely Agree The BumblebeeBee.png 18:55, 24 July 2020 (UTC)
 * Moved to previous section that I didn't see when creating this section Nixinova 01:08, 25 July 2020 (UTC)
 * . Just a note, I'd say Lena Raine and C418 should still have their own pages both as they are extremely well known (especially C418) in-community, and neither are Mojang employees. In general, though, we'd need to have a general guideline for who gets their own page. Things like a well-known nickname, notability in and out of community, and role in the company (ex: Jonas Martensson and Helen Chiang aren't too well known in the community, but hold important positions at Mojang, which may justify them have unique pages?). -PancakeIdentity (talk) 08:43, 27 July 2020 (UTC)

Make templates for common NBT practices.
NBT have several basic tags, and there are many common practices in Minecraft: Java Edition based on those tags. Mojang does use some functions to parse these practices accordingly, I showed three of them here using yarn's mappings:
 * Boolean-like TAG_Bytes: Parsed by . They are technically TAG_Bytes. They use   to represent , and all the other possible values to represent  . e.g.   tag for entities. I've made a possible template User:SPGoding/Sandbox/Nbt practice/boolean for them:
 * UUID: An TAG_Int_Array with four TAG_Ints which represents the bits of an UUID. I've made a possible template User:SPGoding/Sandbox/Nbt practice/uuid_longs for them:
 * Block state TAG_Compounds: Parsed by . A TAG_Compound with a TAG_String named   and a TAG_Compound named   with all the block properties stored. e.g.   tag for enderman entities.

Currently we have Template:Nbt inherit for inheriting NBTs from a parent, but we don't have similar things for those common practices, which leads to copy-pasting similar texts for many times. Thus, I propose to make templates for these practices. -- SPGoding [  Talk  ] 19:34, 21 December 2019 (UTC)


 * How they function may be similar, but this would result in complicating the NBT providing even more (it's already complicated for people unfamiliar with the wiki to provide or correct NBT info). Additionally, UUID tags are extremely invonsistent in java, it's one {l:,m:}, another time Least:,Most: and another time UUID:""; you cannot template that.
 * In short, it'd complicate the most complicated part of the wiki even more, needlessly. FVbico (talk) 20:17, 21 December 2019 (UTC)


 * Thanks for your quick reply. However, I don't think this template would complicate things too much, to the contrary, it would make changing similar stuff easier. For instance, the function Mojang used to get a  has been called for 5 times. Let's see how many times they have been changed on this Wiki:
 * Chunk_format/Vehicle
 * : Optional. The custom block in the minecart.
 * : The namespaced ID of the custom block.
 * : Optional. The block states of the custom block.
 * : The block state name and it's value.
 * Edit 1243175: First introduced.
 * Edit 1255212: Change the format of.
 * Edit 1379673: Change  to.
 * Chunk_format/Projectile
 * : Optional. The block the arrow is in.
 * : The namespaced ID of the block.
 * : Optional. The block states of the block.
 * : The block state name and its value.
 * Edit 1243162: First introduced.
 * Edit 1255211: Change the format of.
 * Edit 1379671: Change  to.
 * Edit 1379674: Change uppercased  to.
 * Piston/BE
 * : The moving block represented by this block entity.
 * : The namespaced ID of the block.
 * : Optional. The block states of the block.
 * : The block state name and its value.
 * Edit 1242720: First introduced.
 * Edit 1255215: Change the format of.
 * Edit 1379679: Change  to.
 * There are still two pages (Sand/BE and Enderman/ED) with the similar situation, but I believe there's no need to put them here anymore. I'm sure everyone can find where the problem is: people have to update the 5 pages individually if they want to improve the content of the BlockState structure. I believe this is much more complex than simply updating one universal template, and I believe you are more aware of this than anybody else because all these awesome changes are just made by you. Moreover, the function used to read boolean-like TAG_Bytes has been called 84 times, which means if anyone want to update the current description of it, they have to change tons of pages separately. However, if we had a template for those common cases, this would no longer be a problem.
 * Here is all my opinion, I really appreciate for your patience. Merry Christmas! -- SPGoding ( Talk ) 23:10, 21 December 2019 (UTC)
 * Edit 1379679: Change  to.
 * There are still two pages (Sand/BE and Enderman/ED) with the similar situation, but I believe there's no need to put them here anymore. I'm sure everyone can find where the problem is: people have to update the 5 pages individually if they want to improve the content of the BlockState structure. I believe this is much more complex than simply updating one universal template, and I believe you are more aware of this than anybody else because all these awesome changes are just made by you. Moreover, the function used to read boolean-like TAG_Bytes has been called 84 times, which means if anyone want to update the current description of it, they have to change tons of pages separately. However, if we had a template for those common cases, this would no longer be a problem.
 * Here is all my opinion, I really appreciate for your patience. Merry Christmas! -- SPGoding ( Talk ) 23:10, 21 December 2019 (UTC)


 * . I think it's the right idea, and if you can solve FVBico's objection to UUIDs where "you can't template that", then I feel it's got no major problems. Yes, doing the nbt templates is complicated, but I don't see this adding significantly to that, relative to the benefit. – Sealbudsman talk | contribs 15:47, 4 January 2020 (UTC)


 * Just wanted to say, the UUID issue is fixed in the 1.16 snapshots. -PancakeIdentity (talk) 06:04, 17 March 2020 (UTC)
 * I've updated the demo template. Thanks for telling me! SPGoding  ( Talk ) 01:51, 21 March 2020 (UTC)

Changes to the upcoming template (and similar)
From here on out, Bedrock and Java will match version numbers. I was thinking that to avoid spam and compress those ugly upcoming tags, we could just allow, for example, upcoming to be used. Individual versions could still be used for version exclusive features, of course. This would help compress those editor notes which can make pages look ugly and harder to read (See Log for example). I think this, along with the proposal above about modifying the in template, would help us greatly improve the readability of articles. -PancakeIdentity (talk) 04:50, 17 March 2020 (UTC)
 * We could have "1.16" redirect to Nether Update, to include both editions. The BlobsPaper.png 15:16, 17 March 2020 (UTC)
 * . --dr03ramos Piston.gif (talk) Admin wiki[pt] 21:03, 18 March 2020 (UTC)


 * A couple notes from a discussion on discord: INUpcoming and inUpcoming could say "In the Nether Update (1.16), ...". In the normal upcoming template, we could also say "Nether Update" as opposed to "1.16". Just a couple more ideas. Personally, I'm neutral on these specific suggestions. -PancakeIdentity (talk) 02:19, 19 March 2020 (UTC)
 * unless Mojang doesn't keep up this consistency. I'd be happy to update/create/fix templates like in etc if needed.  Nixinova</b> </b> <b style=color:white>T</b> </b><b style=background:#00a1ff;padding:2px> <b style=color:white>C</b> </b>


 * I tried implementing something like this, but I couldn't get it to work. I could get Nether Update, but not the other way around. If someone who has more template knowledge than me wants to give it a try, you can edit User:PancakeIdentity/UpcomingMockup. -PancakeIdentity (talk) 23:05, 10 April 2020 (UTC)


 * Yeah, I think it's too long to type "upcoming JE 1.16 & BE 1.16.1" a million times. I'll try to see if it works, your suggestion. 13:48, 25 April 2020 --106.201.186.23 08:18, 25 April 2020 (UTC)


 * These templates are functional in my userspace. User:PancakeIdentity/UpcomingMockup, User:PancakeIdentity/UntilMockup, User:PancakeIdentity/InUpcomingMockup, User:PancakeIdentity/InUntilMockup. They could be implemented, but they no longer accept a 2nd version argument so cleanup will need to be done. -PancakeIdentity (talk) 01:18, 22 April 2020 (UTC)

Should sprite files be interlaced?
Currently, sprites (like [[Media:InvSprite.png|InvSprite.png]]) are not interlaced, which means they will load downwards. If you have a slow connection (or enable slow network simulation in browser inspector), you can see content on the top show up first. So, in a normal page, those sprites coming in later versions will take a while until anything show up. After interlacing these pngs, we can expect the sprites to show up immediately blurred and then fully displayed after loaded, as the pixels are downloaded in a chessboard pattern. (check this for detail)

tl;dr: With interlacing, the sprites load up faster but will start blurred. Without interlacing, the sprites in the bottom will take a while to show up. Should we interlace the sprite files, or rearrange most-used sprites on the top?

-- CuervoTalk 06:27, 25 March 2020 (UTC)


 * I would support interlacing. Otherwise we would need to update the sprite positions, and the incorrect sprites may appear for the next day due to server cache. The BlobsPaper.png 15:15, 25 March 2020 (UTC)


 * Do we even still need sprite sheets? --AttemptToCallNil (report bug, view backtrace) 17:15, 25 March 2020 (UTC)


 * I doubt it, unless InvSprite pulls directly from that big image. -PancakeIdentity (talk) 21:14, 25 March 2020 (UTC)


 * PancakeIdentity@undefined The sprites are directly pulled from the large images; deleting these images would break the templates. The BlobsPaper.png 02:18, 26 March 2020 (UTC)


 * I meant, why not go back to the old system of individual files per image? The performance issues seem to no longer be substantial (there are issues if you're using, like, _hundreds_ of different images per page). As for the sprites in navboxes, they're not really needed; the large navboxes themselves could be candidates for deletion as they aren't very effective for navigation (a task better accomplished by a well-designed category system).
 * I should also note that there's the possibility that with the transition to UCP, functionality critical to the sprite system may become unsupported without any replacement (except to use individual files). --AttemptToCallNil (report bug, view backtrace) 09:42, 26 March 2020 (UTC)


 * iirc, sprites are introduced to optimize numbers of HTTP request, thus reducing protocol overhead. And on the SEO side, search engines seem to favor well-written sites. I know HTTP protocol has been overhauled in recent years but I'm not a web developer, so I don't know if these theories are still true today. For templates, it's true templates aren't intended for navigation on MediaWiki, but the readers would prefer easy-to-read template rather than plain category page imo. CuervoTalk 16:39, 27 March 2020 (UTC)


 * I'd this, although the Sprite editor would have to be changed to support this feature. Also, is there a variation of progressive JPEGs for PNGs? These first load a really low quality version of the image before scaling up the resolution once more of the image loads (for 16x16 images it wouldn't appear much different at all). <b style=background:#0800aa;padding:2px> <b style=color:white>Nixinova</b> </b><b style=background:#006eff;padding:2px> <b style=color:white>T</b> </b><b style=background:#00a1ff;padding:2px> <b style=color:white>C</b> </b> 01:42, 31 March 2020 (UTC)

Cleaning up the meaning of "1.16"
Should we change pages such as the 1.16 disambig page to be a bit more useful?

Recently on discord, said that the classification of the old Playstation versions of 1.16, completely unrelated to the upcoming Nether Update, were confusing (link image). I agree with this sentiment; especially now that version numbers will match on Java and Bedrock, listing these old versions prominently with the Nether Update 1.16's in places such as 1.16 and Java Edition 1.16's sidebar can be very confusing.

In addition, were we to implement the above suggestion of allowing 1.16 and similar formats to be used, the "1.16" page would be really nice to have directly linked to the Nether Update page.

This change would also obviously any future (1.17+) versions, though I don't think it'd be necessary to apply it to older versions, as many of these issues don't apply there. -PancakeIdentity (talk) 02:22, 1 April 2020 (UTC)
 * I don't see the issue here. I fixed the wording of the version nav to be less confusing, and the disambiguation page is just leading to different 1.16s. <b style=background:#0800aa;padding:2px> <b style=color:white>Nixinova</b> </b><b style=background:#006eff;padding:2px> <b style=color:white>T</b> </b><b style=background:#00a1ff;padding:2px> <b style=color:white>C</b> </b> 02:36, 1 April 2020 (UTC)


 * My main concern was with the possible new 1.16, linking to a disambig page where 1/2 the pages linked aren't about the intended version might not be a good idea. We could do something like "1.16 redirects here. For other versions numbered 1.16, see [links to the PS 1.16s]." -PancakeIdentity (talk) 05:56, 1 April 2020 (UTC)


 * this. Redirect 1.16 to Nether Update, and put a hatnote on the top of the page to something like 1.16 (disambiguation). Thomanski (talk) 14:16, 1 April 2020 (UTC)


 * Yeah, this is what I was thinking. -PancakeIdentity (talk) 23:06, 10 April 2020 (UTC)
 * I think it's too soon to do stuff like this. For all we know Bedrock could once again start releasing nothing updates again. "1.16" as a disambiguation works fine and in my opinion is the least confusing way; when you search "1.16" you get a disambig instead of a short page that makes it look like (on first glance) that a comprehensive changelog page doesn't exist, which may be off putting for readers. Putting the year in front of the disambig items also alleviates confusion as to whether PS 1.16s had the nethere update, etc, or not. <b style=background:#0800aa;padding:2px> <b style=color:white>Nixinova</b> </b><b style=background:#006eff;padding:2px> <b style=color:white>T</b> </b><b style=background:#00a1ff;padding:2px> <b style=color:white>C</b> </b> 01:15, 20 April 2020 (UTC)


 * Except they've literally said they intend to keep Java and Bedrock version numbers in line from here on out. Everything else, I understand. But I don't think it makes sense to assume things will change for no reason when they've said otherwise. But yeah, I don't really think it's needed anymore. ATCN managed to solve the upcoming template issue which was my main concern. -PancakeIdentity (talk) 05:42, 20 April 2020 (UTC)
 * I know what was said, but Mojang have said a lot of things like that which don't end up happening. Especially when the quote is "That is the plan…" instead of something like "Yes, that is what we'll be doing from now on". Anyway, whatever. <b style=background:#0800aa;padding:2px> <b style=color:white>Nixinova</b> </b><b style=background:#006eff;padding:2px> <b style=color:white>T</b> </b><b style=background:#00a1ff;padding:2px> <b style=color:white>C</b> </b> 05:48, 20 April 2020 (UTC)


 * My preference is for 1.16 to redirect to Java Edition 1.16 and for 1.16.0 to redirect to Bedrock Edition 1.16.0. The change away from this was a backwards step. With the update versions now consistent, I would support a redirect to Nether Update as a second choice. It might not stay that way but both the most recent update and their intention is for consistency so may as well take advantage of it. Never commented before so lmk if I did something wrong. Miss lauralot (talk) 04:20, 6 July 2020 (UTC)
 * While that is technically correct, I usually refer to both as simply 1.16. Redirecting 1.16 and 1.16.0 to different articles would cause confusion. So we should redirect them to a page that does not prioritize either edition, and that is the Nether Update page. The BlobsPaper.png 16:59, 6 July 2020 (UTC)


 * I'd support redirecting 1.16.0 to Bedrock's page. I think 1.16 is general enough that it shouldn't redirect to Java's page. -PancakeIdentity (talk) 19:57, 6 July 2020 (UTC)

Proposal: replace pseudo-headings based on definition lists
Pseudo-headings like ;Header are semantically correct and may produce invalid HTML, which is likely to interfere with assistive technology (like screen readers). Such pseudo-headings is commonly found on version history pages.

I propose to replace them with actual headers (hidden with depth-limited tables of contents if needed) or, if impossible for some reason, with &apos;&apos;&apos;-based bold text.

Linking to wp:Manual of Style/Accessibility as that provides some more information. --AttemptToCallNil (report bug, view backtrace) 17:16, 14 April 2020 (UTC)


 * Is there an easy way to make headings under a certain level not appear in the table of contents? One problem I can immediately think of if we replaced these pseudo-headings with real smaller headings is pages like Java Edition 1.9 would have an extremely cluttered TOC (although we could simply convert the headings in cases like that to bold I guess).--Madminecrafter12 (Talk to me 17:32, 14 April 2020 (UTC)
 * We have TOC limit. --AttemptToCallNil (report bug, view backtrace) 18:13, 14 April 2020 (UTC)


 * or . I see the benefits, and I guess I don't see any issues with the actual idea. I honestly always just thought that was the correct way to do it. I don't feel strongly about this at all though. -PancakeIdentity (talk) 22:34, 14 April 2020 (UTC)
 * on practicality. While Wikipedia needs to be 100% accessible by blind people I wouldn't think MCW needs to be; if you're blind you're not going to be playing video games like this and as such won't be reading the wiki. I don't think it's worth the effort for the 6 people who would read the wiki that need it. Unless I'm missing something in the reasoning. <b style=background:#0800aa;padding:2px> <b style=color:white>Nixinova</b> </b><b style=background:#006eff;padding:2px> <b style=color:white>T</b> </b><b style=background:#00a1ff;padding:2px> <b style=color:white>C</b> </b> 21:20, 21 April 2020 (UTC)
 * If this is really an issue I'd much prefer using JavaScript to replace definition lists with regular bold text over restricting the whole wiki and having to reteach everyone what to do. <b style=background:#0800aa;padding:2px> <b style=color:white>Nixinova</b> </b><b style=background:#006eff;padding:2px> <b style=color:white>T</b> </b><b style=background:#00a1ff;padding:2px> <b style=color:white>C</b> </b> 21:24, 21 April 2020 (UTC)


 * Yeah this is a good point. It's possible we have a limited view of this, but I'm not sure how helpful optimizing this wiki for screen readers would be. If someone more qualified to speak on this thinks different, I'd love to hear it, but as it stands, I don't think re-teaching the wiki this somewhat minor detail is needed. -PancakeIdentity (talk) 04:47, 20 May 2020 (UTC)

Reworking the LootChestItem template
This template is currently a pain to read whatever it outputs. See Armor and Iron Ingot for examples. There's lots of text with lots of numbers, organization is bad, spacing can be weird, etc. I propose that we rework this template to use tables, preferably somewhat modular, like breaking row is. Even if we don't use a table, I think we can agree the current state of this template is less than idea. What should we do to fix this? -PancakeIdentity (talk) 23:04, 15 April 2020 (UTC)


 * I'm pretty sure the French wiki already does something like this. This would also have tied in to the whole loot rework I've been trying to do, so I'm definitely in support of this (the exact same lines of text being repeated over and over is annoying as hell, and tables just look a hundred times better anyway with said information). I don't think we should account for luck though, since it isn't a survival feature as far as chest loot is concerned. - User-12316399 (talk) 23:13, 15 April 2020 (UTC)


 * It's not even a non-survival feature outside of fishing. -PancakeIdentity (talk) 23:17, 15 April 2020 (UTC)


 * User:Sealbudsman seems to have a work-in-progress on his userpage (which uses Template:LootChestItem2 and Module:LootChest2); perhaps we could expand off of that? – Sonicwave talk  03:48, 16 April 2020 (UTC)


 * Those look like they have potential. -PancakeIdentity (talk) 19:12, 16 April 2020 (UTC)


 * I changed the template to use the base3 (table) version of the module a day or two ago, which is much better, while Sealbudsman's template is still in development. <b style=background:#0800aa;padding:2px> <b style=color:white>Nixinova</b> </b><b style=background:#006eff;padding:2px> <b style=color:white>T</b> </b><b style=background:#00a1ff;padding:2px> <b style=color:white>C</b> </b> 01:11, 20 April 2020 (UTC)
 * The template still has issues. Whenever a loot table is the same across editions, this template only lists them under Java edition. This makes it look like they can only be obtained from woodland mansions and (in 1.16.0) ruined portals. However, I know for a fact that they can also be obtained from desert temples. It is even more confusing because the chance of getting an enchanted apple from a mansion chest is the same across editions only other parts of the loot table are different. The BlobsPaper.png 17:27, 20 April 2020 (UTC)
 * The old text-based template had this exact same issue. It's something that needs to be fixed, yes; but it's not a reason to not use the table template. -PancakeIdentity (talk) 17:35, 20 April 2020 (UTC)
 * Personally I wouldn't mind having duplicate information if it's the same in both editions, you'd have a section with every chest loot info for java and a section with every chest loot info for bedrock.--Capopanzone (talk | contribs) 19:39, 21 April 2020 (UTC)
 * Most readers will just look at the list for their preferred edition, so listing the same chance on both would be simpler. The BlobsPaper.png 20:28, 21 April 2020 (UTC)
 * My only worry with this is the possibility of big tables with lots of repeat info, especially if Bedrock loot tables are made to generally match Java's. What I think would be a good solution would be a general section without a version bar for info that's the same in both. And then, both a Java and Bedrock section that displays entries that are different from each other. -PancakeIdentity (talk) 22:28, 21 April 2020 (UTC)


 * I made some adjustments to Module:LootChest. Now, the loot table is given to both editions, even when identical. When using LootChestItem, the table explicitly lists loot for both editions. I would like to have a way to more simply state that the loot table is the same across editions, but the module uses several functions that I am not familiar with.
 * I am not sure if there is an easy way to implement this, but we could document when the loot tables only have minor differences. For example, ruined portals can have glistering melons in stacks of 4-12 in Java Edition, while they come in stacks on 1 in Bedrock Edition. Even worse, the chest loot is almost identical for woodland mansions, but the weights are scaled up by a factor of 5 in Bedrock Edition. The BlobsPaper.png 18:35, 9 May 2020 (UTC)

List of all additions on Java Edition pages (1.12 - 1.16)
On Java Edition version pages, , , and , probably same user (85.247.222.38 & Groovy goose) added on these pages inventory with all "blocks, items and spawn eggs" added in that version. I'm really disappointed about these edits, as those inventory tables look really confusing and we already have guides for Java versions and for Bedrock, we will have soon. So I suggest to remove them from these pages. --Treeislife2 (talk) 09:12, 16 April 2020 (UTC)
 * for these additions. We already have guides + it is only for inventory items with the inventory textures. --Treeislife2 (talk) 09:12, 16 April 2020 (UTC)
 * But, if it will be on guides pages. --Treeislife2 (talk) 09:42, 22 April 2020 (UTC)
 * . I don't really see any problem with them. — Thomanski | t | c | 18:09, 16 April 2020 (UTC)


 * /. I don't see a need for them, but I always am not totally opposed to including them. -PancakeIdentity (talk) 19:11, 16 April 2020 (UTC)


 * for major updates only. I honestly think it provides a nice overview of all the items added in the update (not all readers know that you can easily find a direct list of the features added on the corresponding named update page) and isn't too much clutter imo. The only reservation I have is looking at the former Java Edition 1.9 on my phone with desktop view, the left side of the inventory of items is completely cut off, and since it's not in the form of an image you can't just click on it and see it in a bigger view. If we could add a parameter to Template:Inventory to make fewer cells per row that might fix it, but then again all different devices are different and this is likely an issue we can't fix for everybody.--Madminecrafter12 (Talk to me 19:32, 16 April 2020 (UTC)


 * You say inventory grid gets cut off, you can't see all 9. How many can you see? – Sealbudsman talk | contribs 20:11, 16 April 2020 (UTC)


 * I see 7 clearly while the furthest to the left is completely cut off and the remaining slot directly to the right can only be partially seen. Scrolling and zooming do not help. Again, though, this likely varies different between mobile devices.--Madminecrafter12 (Talk to me 20:35, 16 April 2020 (UTC)


 * Yeah, that's a problem. – Sealbudsman talk | contribs 21:43, 16 April 2020 (UTC)


 * having it, but not heavily so, even though I did like it. I'd be interested in why they were confusing. As for the observation that we already having guides .. well, these lists aren't guides, they're quite unlike a guide except having similar subject matter. And having the same information in two different forms in two places on the wiki, it's somewhat common I think. – Sealbudsman talk | contribs 20:11, 16 April 2020 (UTC)


 * Looks quite good, and provides a neat little overview over everything that's been added. It can also be used as a shortcut to the respective article if you're interested in reading more about a certain item or block. | violine1101(Talk) 16:35, 19 April 2020 (UTC)


 * on major releases, as it's a useful overview. It definitely shouldn't be on pages that have only one or a few new additions (like in Indev) that are obvious by a quick glance at the additions section. <b style=background:#0800aa;padding:2px> <b style=color:white>Nixinova</b> </b><b style=background:#006eff;padding:2px> <b style=color:white>T</b> </b><b style=background:#00a1ff;padding:2px> <b style=color:white>C</b> </b> 01:12, 20 April 2020 (UTC)


 * for using a inventory image or Template:Inventory to list blocks. The item form of a block is not equal to the block itself. Many blocks don't have a item form, and also many blocks do not exactly correspond to the form of the item. Such as bubble columns in 1.13, in, there is a bubble columns in inventory. This is totally wrong, bubble columns have no item form in java edition, and the sprite of it in Template:Inventory is only for bedrock edition. Another thing, using new textures on pages of old game versions is also very inappropriate.
 * But I for adding a neat little overview. However, use game screenshots or block renders to list blocks.--Chixvv (talk) 08:28, 20 April 2020 (UTC)


 * for these additions. (Sorry for the bad english) We already use a picture alongside the link, and a brief description of the block/item/mob, and I personally think that this is more intuitive:

Thanks, RosilloGames (talk) 19:06, 21 April 2020 (UTC)
 * Furnace JE1.png Furnaces
 * Used to smelt blocks and items.
 * Replaces the old smelting system.


 * That format may be used on other language wikis, but that's not done on the English wiki. IMO, of the two systems, the fake inventory works better as everything is in one place at the top of the page. -PancakeIdentity (talk) 22:26, 21 April 2020 (UTC)
 * as it can improve the readability in some ways. -- LakeJasonFace.png Lakejason0  (Talk • Contribs) 06:44, 22 April 2020 (UTC)
 * But it will broke entire page on mobile. --Treeislife2 (talk) 09:55, 22 April 2020 (UTC)
 * + It looks like old creative inventory from Minecraft Beta 1.8.1. If small inventory OK, but if this type of inventory, then no. And entire broking page also happen. --Treeislife2 (talk) 09:58, 22 April 2020 (UTC)
 * Works fine with mobile on Chinese Minecraft Wiki pages. But maybe not all the mobile devices, so maybe we can just hide this thing for mobile devices if necessary. -- LakeJasonFace.png Lakejason0  (Talk • Contribs) 05:36, 23 April 2020 (UTC)

Solutions
Because discussion stopped for 1 month, I've recently decided to put it again to discuss. As mentioned above, we have several opinions, what to do with addition images


 * 1) List of additions in inventory form, above sections - original solution
 * 2) Adding images before the name of addition (blocks, items, even the terrain can be) - Style was used on Beta articles and earlier. - RosilloGames solution
 * 3) Don't do anything - and another solution

It will be good to make some solution, or we/I will need to close this discussion to avoid these-type edits. I will keep discussion/voting for 2 weeks. --Treeislife2 (talk) 19:42, 25 May 2020 (UTC)


 * So, by now, I solution 2 (Adding images before the name of addition ) --Treeislife2 (talk) 19:42, 25 May 2020 (UTC)


 * I'd personally solution 3, though I don't really have any issues with 1 or 2. I just don't think they're necessary as we have the named version release pages and guides for quick overviews. See also the version page detail discussion. -PancakeIdentity (talk) 04:06, 27 May 2020 (UTC)

Handling of Legacy Sprites
So, a recent discussion on discord has had regarding handling legacy sprites on the wiki. As the discord is not a replacement for on-wiki discussion, I thought I'd bring it here. Should we hold legacy block sprites on the wiki (not image files), and if so, how? Should they be in Block Sprite (and similar), or should there be dedicated templates for these legacy sprites? These sprites would mostly be used in history sections and old crafting recipes where needed.

Personally, I'm mostly neutral on all this. I'd weakly support having them on the wiki somewhere, but I don't feel strongly about it and I don't really care how it's done if we decide to do it. -PancakeIdentity (talk) 01:13, 9 May 2020 (UTC)

Currently, the BlockSprite, ItemSprite and EntitySprite templates all contain a large amount of different textures. A lot of these are left over from updating the template to comply with the Texture Update, and are rarely used, despite them taking up almost half of the space on the sprite sheets in question. This also makes editing them difficult, even in edit sprite form, since they take up huge chunks of space. I'm considering creating dedicated sprite sheets and templates to move these textures to, so that they don't have to take up as much space on the current templates in question and so that the normal ones only hold textures that apply to current Java, Bedrock and Education Edition features. All textures of removed features or outdated textures would be moved t the legacy templates instead.

By default, specifying the name of a block without stating what revision it is would default to the version of that texture as it were on Java Edition prior to the Texture Update, but further details could be specified if a different version of the texture is desired.

I will take 100% responsibility in splitting these sprite templates into the current and legacy versions as well as converting existing pages that use legacy sprites to use the correct templates.

Would anyone explicitly oppose such a change, or would I be free to go ahead with it? - User-12316399 (talk) 01:30, 9 May 2020 (UTC)


 * The spritesheets are too large so I splitting off the legacy sprites. <b style=background:#0800aa;padding:2px> <b style=color:white>Nixinova</b> </b><b style=background:#006eff;padding:2px> <b style=color:white>T</b> </b><b style=background:#00a1ff;padding:2px> <b style=color:white>C</b> </b> 01:17, 9 May 2020 (UTC)
 * for splitting off the legacy sprites. --Treeislife2 (talk) 19:42, 9 May 2020 (UTC)
 * I see no reason to keep the sprites in any form (split or not); we already have revision renders, and aside from invsprite in version pages and history sections, I see no use for them. FVbico (talk) 19:51, 9 May 2020 (UTC)
 * So we're ignoring pages like Java Edition 1.13/Flattening then, which use modern sprites despite the fact that they have no business using block sprites from a year ahead of what they document? - User-12316399 (talk) 20:22, 9 May 2020 (UTC)
 * I'm not ignoring them, those can be changed to the renders instead of the sprites. FVbico (talk) 20:24, 9 May 2020 (UTC)
 * I mean there are examples of things like historical crafting recipes and such, I'm not sure if they can use renders. If they can, then yeah, I don't see much a need either. If they can't, is it worth all the effort to fix it? -PancakeIdentity (talk) 21:33, 9 May 2020 (UTC)
 * While they could be replaced with renders on pages like the mentioned flattening page, the 16x16 block sprites are almost exactly the same size as the text itself, and replacing these with renders would either require scaling them down to being indecipherably small or having them be bigger in a way that unnecessarily stretches the template out. Since blocksprite has them at just the right size to be able to convey the necessary information, I'm still sticking with keeping the legacy sprites in a dedicated template. - User-12316399 (talk) 21:40, 9 May 2020 (UTC)
 * This would just be very inconsistent in my opinion. And I think User-12316399 also got a very strong argument here. Sagessylu (talk) 14:03, 16 May 2020 (UTC)
 * If we were to keep them, would you rather they be split or kept together? -PancakeIdentity (talk) 17:55, 16 May 2020 (UTC)


 * I don't see any reasons for which we shouldn't split. It would indeed make the sprite sheets smaller and easier to maintain. Sagessylu (talk) 14:03, 16 May 2020 (UTC)

If there aren't any objections within the next 12 hours I'll go ahead and split the three relevant sprite templates; if the consensus later turns to just outright removing legacy sprites, the legacy templates can just be deleted anyway to achieve the same effect. - User-12316399 (talk) 21:42, 12 May 2020 (UTC)


 * As there hasn't been any opposition in the given time frame I'm proceeding with the split of templates. Again, since both parties agree with having legacy sprites removed from the main template this shouldn't be controversial, and the dedicated legacy templates can just be deleted if that side wins. - User-12316399 (talk) 12:35, 13 May 2020 (UTC)


 * This was open for only 4 days, and 1 oppose and 1 support; you're in no position to say to go through immediately until there is more support. FVbico (talk) 14:00, 13 May 2020 (UTC)


 * In case I can still give my opinion, I'd say I splitting sprites into their legacy versions, especially the InvSprite. I think removing them completely is a little extreme. I can also run the bot User:Dr03bot if needed. --dr03ramos Piston.gif (talk) Admin wiki[pt] 01:03, 24 May 2020 (UTC)


 * I won't be touching invsprite so someone else will have to do that one if it needs changed. - User-12316399 (talk) 04:35, 27 May 2020 (UTC)


 * , now it seems that Template:BlockLink's doc can not be loaded by documentation at all, I think we need split it no matter whether legacy sprites should be removed.--Chixvv (talk) 00:35, 7 June 2020 (UTC)
 * I tweaked Module:Documentation a bit, it should work better now. I think this shouldn't affect split discussions though. --AttemptToCallNil (report bug, view backtrace) 01:45, 7 June 2020 (UTC)


 * splitting legacy sprites to a separate sprite sheet. It's more visually consistent with current sprites than revision renders, at least for blocks and entities. – Sonicwave talk  00:38, 18 August 2020 (UTC)

Seems like consensus is to remove old sprites so I'll be doing that soon enough. - User-12316399 (talk) 11:56, 28 September 2020 (UTC)

Terrible tutorial pages
Let's face it, the tutorial pages are incredibly bad 90% of the time. So herby a request to rewrite the pages from scratch or discussion to delete them.

An example: the commands page lists commands not valid in any version, advocates terrible setups ("to clear a reeled in fishing rod" can be done so much easier...) and more. FVbico (talk) 15:20, 13 May 2020 (UTC)


 * -ish?. I agree the tutorial pages really need clean up. They ignored by our more active editors most of the time so they kinda get out of hand. I just feel hesitant about strongly supporting this fully for some reason. No real objections from me though I don't think. As for the commands tutorial, imo most commands pages should (aim to) explain commands well enough that tutorials aren't needed. (Edit: The below comments have mostly explained my thoughts better than I did) -PancakeIdentity (talk 17:02 13, May 2020 (UTC).


 * Since the tutorials pages are subpages of Tutorials, they can't be accessed by Special:Random the "Random page" link. Fadyblok240 (talk) 16:48, 26 August 2020 (UTC)


 * Rewriting the tutorials pages, but deleting them except perhaps on a case by case basis. I would lean away from deleting even pages like the commands page which borderlines on "miscellaneous builds." They have a lot of content and can be useful in seeing how to apply redstone/command knowledge. For example, Tutorials/Traps has a lot of inspiring ideas for someone wanting to build a trap, especially for someone new to Minecraft. It might be beneficial to remove messy tutorials from the ginormous, however. That really needs cleaning up. jahunsbe (talk) 00:55, 15 May 2020 (UTC)


 * , but only if done on a case-by-case basis. I totally agree that lots of tutorials pages suck, but not to the extent that they should be deleted or completely rewritten in all cases. I agree deletion/complete rewriting for pages that are really terrible (for ex : Tutorials/Desert shelter, Tutorials/Airlock,, etc.) Sagessylu (talk) 13:56, 16 May 2020 (UTC)
 * Could Goldenghost1000 please explain why he cancelled the small edit I made to my own comment, if I may ask ? Sagessylu (talk) 14:00, 18 May 2020 (UTC)
 * I'm sorry, undo my undo. I thought it was a useless vandal edit, sorry. If you like to discuss further than go to my user page. Thanks User:Goldenghost1000 (talk) 14:27, 18 May 2020 (UTC)
 * OK, I understand. But please, be more careful the next time :) Sagessylu (talk) 16:25, 18 May 2020 (UTC)


 * and I think we should move Beginners Guide Rewrite to Guides Rewrite and add here all guides and their progress (of a rewrite). --Treeislife2 (talk) 17:20, 21 May 2020 (UTC)

But there is already a project called Tutorial Modernization--Treeislife2 (talk) 06:37, 15 June 2020 (UTC)
 * Yes, but, to my knowledge, the purpose of this project is to update the content of the tutorial pages to the latest version, and not to rewrite them or clean them up. Sagessylu (discuss | edits)


 * No, they're all good. I went to Tutorials/PvP and read it one day. I started reading it when I was bored instead of actually playing Minecraft. That shows you how good the tutorials are. 182.65.102.56 08:35, 27 July 2020 (UTC)


 * Well, if that specific tutorial is helpful and up to date, you need not worry. This was not a proposal to get rid of all tutorials, but to update and modernize them instead. This process may involve removing some useless tutorials, but there's no need to worry about important tutorials, such as for PVP. -PancakeIdentity (talk) 08:46, 27 July 2020 (UTC)

Brewing, smelting, grinding, looming, smithing, stone cutting usage
I wonder if anyone is interested in some other type of usage templates besides crafting usage? Looking at Module:crafting usage, it occurs to me that the same module can be adopted to serve many other usage without too much change in the code. If anyone finds that interesting, I can start working on that.

For the technical reader, the DPL category search of crafting usage will be reused, but with a different target template in the parameter. This will mean that the recipe categories will not only include crafting table recipes, but I personally think that makes sense.--Arthur200000 (talk) 15:59, 25 May 2020 (UTC)


 * . Don't see why not, but these methods of crafting are also far less complicated than crafting tables; they're likely not very necessary. -PancakeIdentity (talk) 04:04, 27 May 2020 (UTC)
 * I could support this, but Crafting usage is quite inefficiently done. The DPL & category system by itself is not a good way to do it, but replacing it would require installing something more serious like the Cargo extension. Also, crafting is certainly much common than any other means of production combined. — <b style="line-height:19px;letter-spacing:1px"> Babylon A S </b> *Happy Camper* 07:36, 24 September 2020 (UTC)

Convert some disambiguation pages into broad concept articles
Some disambiguation pages, such as Jockey, hold the title of a primary topic. I think these pages could be rewritten as broad concept articles. For example, the page mob doesn't simply show a list of all mobs in Minecraft, but also show common properties of mobs. Also, there are some disambiguation pages that could be classified as set index articles. See WP:Broad-concept article for more information. --Fadyblok240 (talk) 16:32, 26 July 2020 (UTC)


 * . This is more of a narrow concept, but Insomnia does something similar, though on a much smaller scale; a description of the mechanic with links to various related pages. -PancakeIdentity (talk) 08:37, 27 July 2020 (UTC)
 * Do you think I should start a list of disambiguation pages to be converted into articles?Fadyblok240 (talk) 17:53, 3 August 2020 (UTC)

"Attempted Fixes" section on version pages?
I mentioned this on the discord and people seemed to like the idea, so I thought I'd bring it here for formal discussion. Should we have an "attempted fixes" section on version pages? These would be tickets that Mojang listed in their blog post (or were otherwise marked as fixed by them prior to the version's release), but were not actually fixed. Seems like it'd be simple to implement and to me it makes sense to document this stuff. -PancakeIdentity (talk) 07:11, 30 July 2020 (UTC)


 * It would be useful and can be done rather quickly. Sagessylu (discuss | edits) 08:07, 30 July 2020 (UTC)
 * The changelog for Bedrock Edition 1.11.0 says that they fixed falling through the world at powers of 2, but they did not actually fix this. The BlobsPaper.png 18:14, 30 July 2020 (UTC)
 * Agree with the reasons above but might take a long time and be a hassleHumiebeetalk contributions 17:28, 4 August 2020 (UTC)
 * , as those fixes were at least mentioned in the blog posts and should also be worth mentioning on the wiki. Elite hog (talk) 09:03, 16 August 2020 (UTC)
 * , might reduce some confusion for people seeing those attempted fixes listed on the official changelogs. – Sonicwave talk  00:23, 18 August 2020 (UTC)

Regarding Project:Welcome
Is this project still alive in anyway form or shape? I'm guessing not because I asked this same question there 2 days ago without reply. If so would anybody be interested to restart it? Because as a new user I have some ideas about what could be done better. Asarta  (Talk)  09:18, 3 August 2020 (UTC)
 * I looked at the list of users, and most of them are from far back. AFAIK the only active user on the list is . I will contact them. The BlobsPaper.png 15:17, 3 August 2020 (UTC)


 * I've seen a few users welcomed (though, it's usually a preface to a warning :P). -PancakeIdentity (talk) 05:41, 5 August 2020 (UTC)

request to create more protection levels
currently, we only have 2 levels of protections (and 1 abuse filter) that limit editing, Stop ip-addresses, Stop newcomers, and Stop all but admins. So i think that like wikipedia, we should hava a protection level that only autopatrol/experienced users(look at recent changes) can edit so that pages such as Template:Version/FP can be edited by trusted users, instead of admins only.---HumiebeeDiscuss anything with me Look at my edits 23:29, 12 August 2020 (UTC)


 * Autopatrol-level protection was suggested several times in the past (mostly in the Discord), but I believe it was mentioned that custom protection levels may cause technical issues, though I personally don't recall major issues with the custom directors protection that we already have. Autopatrol protection on Template:Version/FP wouldn't work since it's overridden by the main page's cascading protection (which is admin-only). – Sonicwave talk  23:51, 12 August 2020 (UTC)
 * I looked at previous discussions and unfortunately.......they can't add it😭😡---HumiebeeDiscuss anything with me Look at my edits 22:19, 16 August 2020 (UTC)
 * more protection levels (specifically autopatrol) as they'd be useful in general, even if not applicable in the specific situation mentioned in the proposal. -PancakeIdentity (talk) 08:58, 16 August 2020 (UTC)
 * . Why? What are problems with current one? Also, auto patrols shouldn't are basicly editors, who are so editing, that admins have problems with monitoring other users. --TreeIsLife (talk) 22:56, 9 September 2020 (UTC)
 * with that argument. for more protection levels. Autopatrol level protection is important, especially when abusive persistent vandalism and sockpuppetry forced the admins to set full protection. One example is Human, which was bombed over and over by sockpuppets until full protection halted all edits, delaying useful grammar edits for a month. That protection of Human recently wore off, but Splash is fully protected due to sockpuppetry. This isn't good, as the page has a work in progress template, and many other things there may need constructive editing. Expanding the protection from directors to autopatrol allows more edits, while requiring enough contribution to the wiki to be trusted. Blockofnetherite Talk Contributions 03:09, 21 September 2020 (UTC)
 * Not to mention that the WIP template doesn't use the section param. For now maybe the protection duration should be reduced to about 1 week instead of 1 month to resume constructive edits sooner. By the way, you should submit Gamepedia help tickets regarding the creation and modification of new protection levels, as even the admins of the wiki cannot modify protection levels. Fadyblok240 (talk) 02:33, 22 September 2020 (UTC)
 * The difference is that autopatrol users have been marked by an admin as having useful edits, so locking a page to autopatrol and above would be useful for pages that get sockpuppeted. It's especially useful now as accounts are now really easy to make due to the move away form solely Twitch, and since semi protection only locks it to registered accounts it's very easy to get around, leading to situations where Splash is director protected only due to spam from new accounts. I'll work on making an abuse filter that accomplishes autopatrol level page locking later. <b style="border:1px solid #10a"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b></b>  03:22, 21 September 2020 (UTC)
 * a protection level similar to Wikipedia's semi-protection and extended-confirmed protection, based a mandatory combination of account age and number of edits on this wiki (say, 10 days and 20 edits). a protection level allowing the autopatrol right only in extreme cases because it casts too wide a net, too many constructive editors don't have that right. ~ Amatulic (talk) 05:28, 21 September 2020 (UTC)
 * . TheGreatSpring (talk) 05:30, 21 September 2020 (UTC)
 * Is it possible to create a protection level in which only 'Experienced Users' (recent changes) can edit, similar to wikipedias 30/500 protection? pages like splash could be demoted.---HumiebeeDiscuss anything with me Look at my edits 19:32, 21 September 2020 (UTC)
 * You're referring to "extended confirmed protection". I suggested 10/20 in my vote above. Maybe 10/100. For this wiki, 30/500 seems a bit aggressive. ~ Amatulic (talk) 05:47, 22 September 2020 (UTC)
 * True, I guess that is quite agressive, maybe wikipedia's semi-protection? I would be fine with yours. With the excpetion of previously blocked users, I never see vandalism on the 'learners' section.---HumiebeeDiscuss anything with me Look at my edits 12:02, 23 September 2020 (UTC)

Can create a EarthEntitySprite?
Because there will be more and more creatures in Minecraft Earth.Odyssey08 (talk) 08:39, 14 August 2020 (UTC)


 * Is there a benefit from splitting it from the current entity sprite sheet? -PancakeIdentity (talk) 08:57, 16 August 2020 (UTC)
 * why, no point as there is already a normal entity sprite. with PancakeIdentity---HumiebeeDiscuss anything with me Look at my edits 22:18, 16 August 2020 (UTC)
 * for consistency. There's already a DungeonsEntitySprite (with 72 sprites) and the EarthEntitySprite would have about 48 sprites, expanding rather quickly, so it's as reasonable as the Dungeons one. Sagessylu (discuss | edits) 14:20, 17 August 2020 (UTC)
 * changed to ---HumiebeeDiscuss anything with me Look at my edits 19:21, 17 August 2020 (UTC)

Proposal: remove images from history and put them into separate gallery subpages
This is distracting with how many animations there are. This is annoying to read and translate with how many images there are. This disrupts the flow of text because the images are large.

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


 * , and while doing that for revisions, maybe it's also an idea to do it for the block states sections like with redstone wire? Currently, some block states are hard to understand with the explanation they have. Images for visual block state differences would help. FVbico (talk) 09:37, 21 August 2020 (UTC)
 * , it took a lot of time to update these spawn egg images on Chinese Wiki (from sprites to images), and barely does nothing. It might be a bit useful when there are a little images along with historical texts, but only a little.-- LakeJasonFace.png Lakejason0  (Talk • Contribs) 10:07, 21 August 2020 (UTC)
 * , they are just an eyesore at this point. I had this idea beforehand but not encouraged enough to make a remark. For now, I would only think that separating them is the best decision. – ItsPlantseed ⟨₰|₢⟩ 10:30, 21 August 2020 (UTC)
 * I'd say this is more of an issue with the History template itself than its contents, and we can all agree that said template is way overdue for a revamping. - User-12316399 (talk) 12:00, 21 August 2020 (UTC)
 * with you, also about this topic---HumiebeeDiscuss anything with me Look at my edits 12:56, 21 August 2020 (UTC)
 * , sheep kinda does this already. -PancakeIdentity (talk) 03:32, 23 August 2020 (UTC)
 * . — Thomanski | t | c | 13:15, 23 August 2020 (UTC)

Proposal
I have created a potential mock-up on User:Thomanski/Sandbox/Gallery for Log. Any feedback appreciated. — Thomanski | t | c | 13:15, 23 August 2020 (UTC)
 * . -DEJVOSS (talk)  13:47, 26 August 2020 (UTC)
 * Changed to ---HumiebeeDiscuss anything with me Look at my edits 17:29, 4 September 2020 (UTC)

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

Acceptable uses: Disallowed uses: Unsure: There are more uses of subpages on this wiki but I am still unsure about whether they are acceptable. Fadyblok240 (talk) 21:23, 23 August 2020 (UTC)
 * Anything that Wikipedia accepts as subpages—User subpages, template documentation, etc. It is laughable to even think about removing these subpages from the Minecraft wiki.
 * Mod pages (until all mod pages are moved to FTB)—The Minecraft Wiki only concerns the vanilla game. Although some of these pages are full articles, we don't want readers to end up on pages about specific mods.
 * Writing about a feature of the same name for a different edition—These pages are articles and there are better ways to disambiguate the name than making it look like one article forms part of another when it does not.
 * Category subpages—Categories were created to replace mainspace subpages on Wikipedia. Using subpages for categories is pointless and sometimes the names get ridiculously long.
 * Mechanics pages—These pages are also articles, and in the past there was a dispute on whether these pages should be named "Mechanics/X" or "X/Mechanics".
 * Tutorials subpages—These pages are less like encyclopedia articles, but they still contain helpful instructional material so they should be moved to a new namespace.
 * File subpages—I don't know whether there are such pages or even if the subpage feature is enabled, but it should be disabled because some filenames create accidental subpages and hierarchy among files is bad.
 * Previous versions of features—These articles are useful to a historical perspective, but completely irrelevant in the latest version of the game.
 * Command subpages—These pages are legitimate articles, but pages starting with "/" cause technical problems.
 * Schematic pages—They are merely pseudo-images that are transcluded, but sometimes they may be used on more than one page so maybe they should be converted to templates.


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

1 more thing, what do you mean by previous versions of features? are you talking about Java Edition 1.13/Flattening? ---HumiebeeDiscuss anything with me Look at my edits 22:59, 23 August 2020 (UTC)
 * 1) User subpages  be allowed.
 * 2) Minecraft Wiki namespace subpages  be allowed.
 * 3) Archive subpages  be allowed.
 * 4) Documentation  be allowed (template)
 * 5) Guides, Commands and Official subpages  be allowed.
 * 6) Previous versions of features  be allowed.
 * 7) Development versions subpages  be allowed (ex:Java Edition 1.0.0/Development versions)
 * 8) Subpages that make sense but are too technical to be in a main article (Ex:/DV, /Structure, Category Data Pages, or others).
 * 9) Mod subpages  be allowed (as they still haven't been completely exported yet)
 * 10) Writing about a feature of the same name for a different edition  be allowed as it makes sense but the argument also makes sense so i'm sorta split?
 * 11) Mechanics pages should be  to another subpage/possible tutorial namespace
 * 12) Tutorials subpage should be  to another namespace
 * 13) Category subpages should be  be allowed like theres such thing as subcategories (Ex Objects requiring isometric renders/Re-render)
 * Kinda, I meant pages like "X/Before ". which in my opinion I am still not sure about. Fadyblok240 (talk) 17:21, 24 August 2020 (UTC)
 * I support keeping those as let's take the Far lands, old farlands sounds so wrong and also, merging the Far Lands/Java Edition and Far Lands will create a lot of confusion, thats why it was split---HumiebeeDiscuss anything with me Look at my edits 17:46, 24 August 2020 (UTC)
 * What does this (Writing about a feature of the same name for a different edition) mean? like I don't know any example and I'm pretty sure there's no subpage, can you give an example?---HumiebeeDiscuss anything with me Look at my edits 17:48, 24 August 2020 (UTC)
 * A page like Achievements/Java Edition. I prefer moving pages like these to " X" (i.e. Java Edition Achievements and Java Edition Far Lands). I also support moving the current Far Lands page and moving it to Bedrock Edition Far Lands and leaving a disambiguation page behind. –Preceding unsigned comment was added by Fadyblok240 (talk • contribs) at 17:58, 24 August 2020 (UTC). Please sign your posts with
 * I don't think moving "X/Edition" to "Edition X" is a good idea; the former provides a semantic relation that is more visible to search engines. I'm not sure what "category subpages" are or whether they are used on MCW. As for mechanics, "X/Mechanics" has the same consideration of semantic relation as with editions. --AttemptToCallNil (report bug, view backtrace) 18:01, 24 August 2020 (UTC)
 * There are already articles using the "Edition X" format, e.g. Java Edition mentioned features. Also, there is such a thing as category subpages on this wiki. I have reworked Template:Needs render to avoid category subpages, but Template:Render uses dozens of category subpages (e.g. Category:Objects requiring isometric renders/Historical features/Stems/Invalid states) which is too much for me to handle. Fadyblok240 (talk) 18:36, 24 August 2020 (UTC)
 * Above is 1 such example---HumiebeeDiscuss anything with me Look at my edits 18:40, 24 August 2020 (UTC)
 * Oh, those? Yeah, I agree, they're not the best idea. --AttemptToCallNil (report bug, view backtrace) 18:43, 24 August 2020 (UTC)
 * Mixed opinion on this. Subpages automatically link back to their parent pages at the top and allows easy access to them; this is especially useful on mobile where neither categories nor navbox templates show up. With that in mind, I think it makes sense to keep at least the following as subpages (and probably other scenarios that I missed):


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


 * However, I would support template-like subpages (such as Renewable resource/row) to the template namespace, as well as cleaning up category subpages. I would also support moving "Mechanics/Redstone" to "Redstone mechanics" since the mechanics page itself is a redirect to a different page. Regarding some of the suggestions by, I am neutral on moving Tutorials pages to a separate namespace (assuming that it's searchable like the MCD and MCE namespaces), but disagree with making a namespace for "X/Mechanics" pages as they are similar to regular articles, just more technical. – Sonicwave talk  20:08, 24 August 2020 (UTC)
 * Ok, I agree on pretty much your whole statement above including the gallery subpage idea but but I think the Mechanics should possibly go into Tutorials:Mechanics/whatever.---HumiebeeDiscuss anything with me Look at my edits 20:15, 24 August 2020 (UTC)
 * I dont know, if mechanics are (not) tutorials, but I have no problem with that. So I am this idea. –Preceding unsigned comment was added by TreeIsLife (talk • contribs) at 20:50, 24 August 2020 (UTC). Please sign your posts with
 * I mean it is teaching you the mechanics of whatever so that make sense.---HumiebeeDiscuss anything with me Look at my edits 22:47, 24 August 2020 (UTC)


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


 * Many of the Tutorials subpages are ignored by the Minecraft Wiki's most active editors. Special:Random The "Random page" link never links to subpages. If the tutorials were moved to a new content namespace, they wouldn't be subpages and therefore be accessible from the Random page link and more likely for editors to notice. Fadyblok240 (talk) 02:09, 27 August 2020 (UTC)
 * Special:Random does not link to anything besides mainspace so that's.......---HumiebeeDiscuss anything with me Look at my edits 02:24, 27 August 2020 (UTC)
 * The "Random page" link does link to other namespaces, namely Minecraft Earth and Minecraft Dungeons. If a Tutorials namespace were created, the wiki manager could classify it as a content namespace. Ironically, Special:Random also links to subpages, although the "Random page" link does not. Fadyblok240 (talk) 02:40, 27 August 2020 (UTC)


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


 * See Minecraft Wiki talk:Community portal/Archive 26 for further info about moving tutorials to a new namespace. Fadyblok240 (talk) 00:22, 18 September 2020 (UTC)
 * Should you open up a new discussion about this? I would like a new tutorials namespace, supporing and  ideas.---HumiebeeDiscuss anything with me Look at my edits 01:19, 18 September 2020 (UTC)
 * Here is a quote
 * ---HumiebeeDiscuss anything with me Look at my edits 01:25, 18 September 2020 (UTC)
 * And Another one
 * All in all, the opposes are not very convincing but the supports are, should I reopej the discussion?---HumiebeeDiscuss anything with me Look at my edits 01:27, 18 September 2020 (UTC)

Bot noticeboard?
I know this sounds really dumb but I kind of want like a page, similar to the Minecraft Wiki:Admin noticeboard that people can post on that requests something that a bot would do such as fixing links due to UCP. Maybe is should be called something else but idk what. Link????Minecraft Wiki:Bot noticeboard---HumiebeeDiscuss anything with me Look at my edits 20:29, 26 August 2020 (UTC)
 * I'm kind of skeptical. The Russian wiki has made one long ago. Now it's unused. Completely. The last 3 edits were in 2016, 2017, and one IP request about a month ago. --AttemptToCallNil (report bug, view backtrace) 20:40, 26 August 2020 (UTC)
 * Is there a link?---HumiebeeDiscuss anything with me Look at my edits 20:40, 26 August 2020 (UTC)
 * ru:MCW:Запросы к ботоводам. --AttemptToCallNil (report bug, view backtrace) 21:07, 26 August 2020 (UTC)
 * Oh... ever since 2016, it's been unused??---HumiebeeDiscuss anything with me Look at my edits 21:17, 26 August 2020 (UTC)
 * It seemed to be pretty active at 2014 but for some reason, it completely died down..---HumiebeeDiscuss anything with me Look at my edits 21:18, 26 August 2020 (UTC)
 * Thanks!---HumiebeeDiscuss anything with me Look at my edits 21:16, 26 August 2020 (UTC)
 * Wikipedia has a similar page named Wikipedia:WP:Bot requests but on the Minecraft Wiki there are not that many bots, so maybe the Bot Noticeboard doesn't warrant its own page, but should be a section of subpage of the Admin Noticeboard or linked directly on the sidebar. Fadyblok240 (talk) 20:46, 26 August 2020 (UTC)
 * I don't think it should be in the sidebar but I do on it to be a subpage/subsection of the admin noticeboard.---HumiebeeDiscuss anything with me Look at my edits 20:49, 26 August 2020 (UTC)
 * I would a small section dedicated for this. Although I feel like the community portal would a better place for this than the admin noticeboard, as bot edits aren't necessarily for admins. — Thomanski | t | c |  21:55, 26 August 2020 (UTC)
 * Though bots rights are only given to bots of trusted users so I have some mixed opinions---HumiebeeDiscuss anything with me Look at my edits 21:56, 26 August 2020 (UTC)
 * It's not super hard to be considered a trusted user if you're somewhat active and consistently constructive. Also, bots don't really have many different rights than normal user accounts, it's more to do with reducing spam and stuff. -PancakeIdentity (talk) 21:53, 27 August 2020 (UTC)


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

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

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


 * 1) Welcome
 * 2) Screenshot Minecraft Versions
 * 3) Beginner's Guide Rewrite
 * 4) Minecraft in schools
 * 5) Screenshot Fixing
 * 6) Rewrite for Style
 * 7) Version cleanup
 * 8) Tutorials Modernization
 * 9) Userboxes standardization
 * 10) Redirect cleanup
 * 11) Renaming
 * 12) Cleanup open tags
 * 13) Capitalization Fixing
 * 14) Individual Biome Pages
 * 15) Upload Missing Wiki Sounds
 * 16) Refactoring edition specific information
 * 17) Minecraft Earth Wiki
 * 18) Texture Documentation Cleanup
 * 19) Gallery organization
 * 20) Wiki videos
 * 21) Minecraft: Story Mode Mobs

21 pages, with some of them could be deleted.

So i start with my ideas
 * 1) Fandom has automatic Messages from some MediaWiki page. Also i don't see anybody adding Welcome template, so I consider.
 * 2) Should be merged with Screenshot fixing
 * 3) Better merging with Minecraft in Education
 * 4) Should be merged with Screenshot Minecraft Versions
 * 5)  but, compleate it.
 * Ok,
 * 1) Keep it
 * 2) No activity, it's in dead point from it's creation, consider removing it
 * 3) It is compleated, we should archive that
 * 4) Keeping it
 * 5) Keeping it
 * 6) Happy to see it will be done (one time), so keep it
 * 7) It is compleated, so archive
 * 8) Keeping longer for discuss
 * 9) Archive
 * 10) Keep
 * 11) This is not most useful project, so discussion
 * 12) Keep that
 * 13) Keep it, but i notice that's outdated.
 * 1) Keep that
 * 2) Keep it, but i notice that's outdated.

--TreeIsLife (talk) 20:54, 26 August 2020 (UTC)
 * I have some opinions as well.


 * , Madminecrafter12 is the only user to even remotely work on it, completly unused though the template should still remain as the template, not the project is still used.
 * , would be better to merge with capitalization fixing.
 * , don't bomb it, improve it.
 * 1)  with Rewrite for Style
 * 2)  there's still a discussion with like 90% support and so more discussion is not really needed
 * 3)  Story mode is discontinued so since less people have it, I don't think it's worth the effort so ---HumiebeeDiscuss anything with me Look at my edits 21:15, 26 August 2020 (UTC)
 * I think Rewrite for Style and Capitalization Fixing should be merged. Fadyblok240 (talk) 16:57, 27 August 2020 (UTC)
 * , don't bomb it, improve it.
 * 1)  with Rewrite for Style
 * 2)  there's still a discussion with like 90% support and so more discussion is not really needed
 * 3)  Story mode is discontinued so since less people have it, I don't think it's worth the effort so ---HumiebeeDiscuss anything with me Look at my edits 21:15, 26 August 2020 (UTC)
 * I think Rewrite for Style and Capitalization Fixing should be merged. Fadyblok240 (talk) 16:57, 27 August 2020 (UTC)
 * 1)  with Rewrite for Style
 * 2)  there's still a discussion with like 90% support and so more discussion is not really needed
 * 3)  Story mode is discontinued so since less people have it, I don't think it's worth the effort so ---HumiebeeDiscuss anything with me Look at my edits 21:15, 26 August 2020 (UTC)
 * I think Rewrite for Style and Capitalization Fixing should be merged. Fadyblok240 (talk) 16:57, 27 August 2020 (UTC)
 * 1)  there's still a discussion with like 90% support and so more discussion is not really needed
 * 2)  Story mode is discontinued so since less people have it, I don't think it's worth the effort so ---HumiebeeDiscuss anything with me Look at my edits 21:15, 26 August 2020 (UTC)
 * I think Rewrite for Style and Capitalization Fixing should be merged. Fadyblok240 (talk) 16:57, 27 August 2020 (UTC)
 * 1)  Story mode is discontinued so since less people have it, I don't think it's worth the effort so ---HumiebeeDiscuss anything with me Look at my edits 21:15, 26 August 2020 (UTC)
 * I think Rewrite for Style and Capitalization Fixing should be merged. Fadyblok240 (talk) 16:57, 27 August 2020 (UTC)
 * I think Rewrite for Style and Capitalization Fixing should be merged. Fadyblok240 (talk) 16:57, 27 August 2020 (UTC)


 * Mostly agree with your conclusions. At this point, I'm not sure we need #16 anymore, we only deal with two editions. We're not perfect in how we document them yet but I'm not sure if need a project, especially as it never really had much discussion on what to do. Also, just wanted to check, the Earth Wiki project has no relevance now that it has its own namespace, correct? -PancakeIdentity (talk) 17:32, 27 August 2020 (UTC)
 * The Minecraft Earth Wiki project is still relevant, as many of the articles in that wiki's namespace are stubs. Fadyblok240 (talk) 09:43, 31 August 2020 (UTC)
 * Also, we should reclassify some projects as semi-active, as the Minecraft Wiki is never complete. The cleanup open tags project has turned into a white elephant project. Fadyblok240 (talk) 02:16, 19 September 2020 (UTC)

Documentation template revamp
Can somebody add links to "/sandbox" and "/testcases" subpages of templates to the Template:Documentation template? Fadyblok240 (talk) 19:08, 28 August 2020 (UTC)
 * Why? --TreeIsLife (talk) 22:39, 9 September 2020 (UTC)
 * I (along with Humiebee) have created several template sandboxes, but the documentation template does not recognize that they are template sandboxes and shows that they have no documentation; they appear in Category:Templates with no documentation instead of Category:Template sandboxes. Fadyblok240 (talk) 22:32, 26 September 2020 (UTC)
 * I don't see the need for those pages, they'd just become outdated and useless quickly. Just use the Template:Sandbox or your own user subpage instead. <b style="border:1px solid #10a"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b></b>  02:10, 27 September 2020 (UTC)
 * Template sandbox subpages would be useful for implementing major changes to high-risk templates with complex code or many parameters, where the "show preview" button alone would not guarantee whether the template is free of errors. Fadyblok240 (talk) 03:31, 5 October 2020 (UTC)

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

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


 * , the reason why I upload files to those interwikis is to remove their dependency of the English wiki so we can finally remove the grid files here. I honestly don't know what to do with these wikis though. I don't think straight up deleting them is a good idea (for people that don't understand English), but on the other hand, these interwikis are REALLY outdated and inaccurate information is never a good thing for a wiki. — Thomanski | t | c | 21:45, 4 September 2020 (UTC)
 * Yeah, but like putting it into a translation project isn't harmful.---HumiebeeDiscuss anything with me Look at my edits 22:01, 4 September 2020 (UTC)


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


 * I think it has to do with the Cyprus dispute Fadyblok240 (talk) 00:36, 5 September 2020 (UTC)
 * What does this have anything to do with the discussion?---HumiebeeDiscuss anything with me Look at my edits 00:42, 5 September 2020 (UTC)
 * - why can't we just delete the untranslated pages instead, and add dedicated "this info is disgustingly outdated" templates to it instead? I wouldn't be against just getting rid of the wikis entirely either given the lack of interest. - User-12316399 (talk) 00:40, 5 September 2020 (UTC)
 * Yes, because whats the point about having a wiki page translated in multiple languages and the translated pages not even be finished and be forgotten about. I would consider it wiki clutter. So unless someone takes the time out of their day to rework all these translated pages, i think it's best to just axe em'. James Haydon (talk) 04:05, 5 September 2020 (UTC)
 * doing something about these translations, the Greek wiki is just a complete import of the English one, issues pages and all (this should never be how translations are done), so everything is 3+ years outdated and clutters maintenance on this wiki. Add to that the fact that, since the wiki is in English, its a target for spammers who won't be reverted like they are here. E.g.: el:Alpha 1.2.4: there's no'one other than English wiki users to revert them. I can barely find many pages that have actually been translated apart from like a disambig, though there is el:Κρύσταλλος_του_Ender, el:Βιβλίο και Πένα, el:Κύβοι Διαμαντιού‏‎, el:Μπλοκ‏‎, but that's it. I'll just import all of the translated pages back here so they're safe if we feel like nuking that wiki. <b style="border:1px solid #0800aa"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b>  20:20, 5 September 2020 (UTC)
 * There: Special:Prefixindex/MCW:Projects/Greek translation/ – that's literally all the translated Greek pages. The wiki can be safely nuked now if that's decided. <b style="border:1px solid #0800aa"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b>  20:34, 5 September 2020 (UTC)
 * What about the turkish wiki?---HumiebeeDiscuss anything with me Look at my edits 22:53, 5 September 2020 (UTC)


 * for the Greek wiki, mainly because so many pages are untranslated (which kinda defeats the purpose of a traduction). for the Turkish wiki, mainly because of the inactivity. Sagessylu (discuss | edits) 17:37, 6 September 2020 (UTC)
 * , the Greek wiki is already translated.---HumiebeeDiscuss anything with me Look at my edits 20:55, 6 September 2020 (UTC)
 * by Nixinova Greek wiki only ---HumiebeeDiscuss anything with me Look at my edits 20:55, 6 September 2020 (UTC)
 * Well, not really, I've just moved a couple to this wiki, el: still exists. <b style="border:1px solid #0800aa"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b>  01:33, 7 September 2020 (UTC)
 * okay ill wait and see if someone will actually finish them now that there back in the works. James Haydon (talk) 00:50, 7 September 2020 (UTC)


 * I'm worried about the Ukrainian wiki potentially suffering from the same fate. It's also on the brink of dying out. There is one local user who appears to have edited in the last few days, but aside from that, there are predominantly edits by users from other wikis, notably Mak_and_Iv (a Russian admin) who is also an admin on the Ukrainian wiki. — <b style="line-height:19px;letter-spacing:1px"> Babylon A S </b> *Happy Camper* 12:20, 30 September 2020 (UTC)

Replace /ED, etc, subpages with DPL section transclusion
TIL that DPL can be used for labelled section transclusion:. This can replace having /ED, /BE, etc subpages. <b style="border:1px solid #0800aa"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b>  22:47, 5 September 2020 (UTC)


 * Changing it might break some nbt inherit templates though. FVbico (talk) 20:58, 6 September 2020 (UTC)
 * What about change it to only certain templates where it won't break?---HumiebeeDiscuss anything with me Look at my edits 20:59, 6 September 2020 (UTC)


 * Oh, LST finally works now? I believe there could be a workaround for NBT pages, but if it can be easily done with non-NBT data, then I am all for it. — <b style="line-height:19px;letter-spacing:1px"> Babylon A S </b> *Happy Camper* 07:23, 24 September 2020 (UTC)

Converting .ogg files to .mp3 and .wav
Given that .ogg files aren't supported on mobile, maybe we should convert all .ogg files into .mp3 (Music samples) and .wav (sounds) files with software like Audacity. One user at Terraria wiki did this to Terraria: Otherworld tracks, wich were .ogg files. --Superwill771 (talk) 15:55, 8 September 2020 (UTC)
 * There will be much much work. Only if you want to do converting and uploads, then, i am --TreeIsLife (talk) 16:04, 8 September 2020 (UTC)


 * Umm... for me, the sounds on skeleton, which are ogg sounds, work fine on mobile. FVbico (talk) 16:12, 8 September 2020 (UTC)
 * Probably (as I understood from discussion) meant on mobiles with mobile view. But even there, it is working. --TreeIsLife (talk) 16:24, 8 September 2020 (UTC)


 * I use Duckduckgo on an ipad with desktop view and they don't work.--Superwill771 (talk) 16:36, 8 September 2020 (UTC)
 * Well, it can be problem with iPads/iPhones. Duckduckgo is search engine. --TreeIsLife (talk) 16:40, 8 September 2020 (UTC)
 * Ogg sounds are not supported in Safari browsers. --AttemptToCallNil (report bug, view backtrace) 17:49, 8 September 2020 (UTC)
 * Duckduckgo is also a browser app on iOS/Android. I don't know if they meant that. — Thomanski | t | c | 19:38, 8 September 2020 (UTC)


 * . For the above reasons that some devices don't support these ogg files, I support. However, looking at User:TreeIsLife,'s argument it is a lot of work, I say go ahead and do that, I don't see it as a bad thing. Good luck on that. Blockofnetherite Talk Contributions 18:05, 8 September 2020 (UTC)
 * for below reasons. Blockofnetherite Talk Contributions 21:22, 9 September 2020 (UTC)
 * , this wiki is about work, I use safari and it fails completely, the terraia wiki example is good.---HumiebeeDiscuss anything with me Look at my edits 19:26, 8 September 2020 (UTC)
 * for conversion to MP3, definitely not WAV. See my explanation on Terraria Wiki. --AttemptToCallNil (report bug, view backtrace) 19:38, 8 September 2020 (UTC)
 * So your saying we could use FLAC?---HumiebeeDiscuss anything with me Look at my edits 19:41, 8 September 2020 (UTC)
 * It looks possible, but I don't think this was actually done on the wiki before. --AttemptToCallNil (report bug, view backtrace) 20:05, 8 September 2020 (UTC)
 * , but I'm not gonna do it. — Thomanski | t | c | 19:39, 8 September 2020 (UTC)
 * . Just because ogg isn't supported on some mobile devices now, doesn't mean it won't be later, given that it's a license-free open-source thing. Firefox and Chrome already support ogg. I note that the VLC player supports ogg on all mobile devices. And I believe the Opera browser does also, which is also available on any mobile device. ~ Amatulic (talk) 16:28, 9 September 2020 (UTC)
 * why strong oppose TheGreatSpring (talk) 07:56, 22 September 2020 (UTC)
 * As a matter of principle, I strongly oppose creating unnecessary time-wasting busy-work, which is basically what is being proposed. Ogg is playable on all desktop browsers and on all mobile devices using VLC. By the time all the work has been done to convert ogg to mp3, mobile browsers will likely be supporting it anyway. ~ Amatulic (talk) 21:13, 22 September 2020 (UTC)
 * as a temporary measure until the majority of affected devices end up supporting playback. - User-12316399 (talk) 17:11, 9 September 2020 (UTC)
 * . I definitely don't like mp3 because it's not lossless, and I think this wiki supposedly being a source of information should present that information without losses. I see the issues with wav and ogg as well, though. What other possibilities are there? Blue Banana whotookthisname (talk) 07:39, 21 September 2020 (UTC)
 * Well, the sounds and music are stored in Minecraft as Ogg files in the first place, so if data integrity is a concern, they should be used and uploaded directly, which was already done. (For music files, it’s possible to cut the file to 30 seconds without re-encoding it — FFmpeg does allow that, not so sure about Audacity.) — <b style="line-height:19px;letter-spacing:1px"> Babylon A S </b> *Happy Camper* 15:09, 24 September 2020 (UTC)
 * TheGreatSpring (talk) 07:56, 22 September 2020 (UTC)
 * — Transcoding Ogg Vorbis (one lossy format) to MP3 (another lossy format, with worse quality by the way) isn't good practice in general, and using WAV will lead to much larger files. Safari not supporting Ogg is Apple's fault, and VLC is also available (if I recall correctly™) on iOS/macOS as well. As for royalty free, this advantage of Ogg is no longer relevant now, as all patents on MP3 have already expired, however Ogg Vorbis is still superior quality-wise (as in, Ogg file will sound better than an MP3 of identical size). It doesn't seem to be worth the effort. — <b style="line-height:19px;letter-spacing:1px"> Babylon A S </b> *Happy Camper* 07:19, 24 September 2020 (UTC)
 * I now the idea TheGreatSpring (talk) 12:56, 24 September 2020 (UTC)


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

The Skeleton Horseman problem, and how should we fix it?
Recently, has had its link changed from Skeleton Horse to MCD:Skeleton Horseman. Two major problems emerged from doing so: Is it called a skeleton trap, a skeleton jockey, or a skeleton horseman? This change of redirect of the Skeleton Horseman page has caused some confusion for me. Blockofnetherite Talk Contributions 20:33, 8 September 2020 (UTC)
 * 1) Many "Skeleton Horseman" links of the Minecraft jockey-like mob suddenly redirected into a Minecraft Dungeons mob. This created problems for the Minecraft topic section of the Skeleton (disambiguation) page.
 * 2) At least two templates, Template:EntitySprite and Template:EntityLink's id is "skeleton-horseman", not "skeleton-trap".
 * Ok, try do to your best and fix it, i have no other argument, so I am ing. --TreeIsLife (talk) 20:40, 8 September 2020 (UTC)
 * Thanks for the support, but I currently don't want to fix it yet, as I still don't exactly know how to fix it, nor do I know how to change those two templates which use the id "skeleton-horseman". @Humiebee very recently undid @Fadyblok240 's edit, but it's not over. Blockofnetherite Talk Contributions 20:44, 8 September 2020 (UTC)
 * To avoid confusion, I added the redirect template.---HumiebeeDiscuss anything with me Look at my edits 20:46, 8 September 2020 (UTC)
 * It should be redirected back to skeleton trap with a hatnote (for) added to the top of the section. Vanilla should always take priority. <b style="border:1px solid #0800aa"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b>  20:41, 8 September 2020 (UTC)
 * What about the templates? Blockofnetherite Talk Contributions 20:47, 8 September 2020 (UTC)
 * , but with redirect instead---HumiebeeDiscuss anything with me Look at my edits 20:43, 8 September 2020 (UTC)

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

Add shorthand Namespaces for certain things
Now there are shortened namespaces such as MCD:Zombie or MCE:Muddy Pig but others such as Templates don't have one. All namespaces except for main (obviously) should have an abbreviation. Already Existing Not Sure if exists Does not exist, definitely want If this gets implemented, want for consistancy Ones that I really just don't want or need but it would br nice for consistancy ---HumiebeeDiscuss anything with me Look at my edits 20:09, 11 September 2020 (UTC)
 * 1) MCW (Minecraft Wiki)
 * 2) MCT (Minecraft Wiki talk)
 * 3) MCE (Minecraft Earth)
 * 4) MCD (Minecraft Dungeons)
 * 1) Minecraft Dungeons talk or Minecraft Earth talk
 * 2) My proposals would be MDT and MET respectively
 * 1) TP for Template
 * 2) TPT for Template talk
 * 3) MW for MediaWiki - Automaticly redirects to mediawiki.org, so that's impossible to add.
 * 4) New Proposal for MediaWiki. MDW for MediaWiki.
 * 5) MWT for MediaWiki talk
 * 6) CAT for Category
 * 7) CTT for Category talk
 * 8) M or MOD for Module
 * 9) MT or MDT for Module talk
 * 1) T for talk
 * 2) U for User
 * 3) UT for User talk
 * 4) F for File
 * 5) FT for File talk
 * 6) H for Help
 * 7) HT for Help talk
 * 8) W for Widget (didn't even know this existed)
 * 9) WT for Widget talk
 * 10) S or SP for Special Page
 * 11) UP for UserProfile
 * 1) G(T) or GA D (T) for Gadget (talk)
 * 2) GD(T) for Gadget definition (talk)
 * Not sure these should all be created, but I can definitely make a template that does this. <b style="border:1px solid #0800aa"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b>  20:10, 11 September 2020 (UTC)
 * I think, their existence wouldn't harm the wiki. FVbico (talk) 20:18, 11 September 2020 (UTC)
 * How do tou create a template for namespaces?---HumiebeeDiscuss anything with me Look at my edits 20:21, 11 September 2020 (UTC)
 * Not for the namespaces themselves, but for linking to them. That wouldn't affect searching, however, but I could also make a script that does this for individuals. <b style="border:1px solid #10a"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b></b>  20:29, 11 September 2020 (UTC)
 * I would love the script as I search for templates a lot and it's annoying when I misspell it as trmplate (r is on the way from t to e so yeah), where would the script go, common.js?---HumiebeeDiscuss anything with me Look at my edits 20:32, 11 September 2020 (UTC)
 * Yes, common.js, try adding  to yours to test my new script. <b style="border:1px solid #10a"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b></b>  20:49, 11 September 2020 (UTC)
 * Oh, ok, thank you, can you delete the test page I made and it's documentation?---HumiebeeDiscuss anything with me Look at my edits 20:51, 11 September 2020 (UTC)
 * Why does it go to like the search then the desired page, nothing of a big deal though, is it a limitation or is it diffucult to change that?---HumiebeeDiscuss anything with me Look at my edits 21:29, 11 September 2020 (UTC)
 * Fixed. <b style="border:1px solid #10a"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b></b>  21:45, 11 September 2020 (UTC)
 * I think it broke again.... I searched UT:Nixinova and it didn't work..., thanks for everything!---HumiebeeDiscuss anything with me Look at my edits 21:55, 11 September 2020 (UTC)
 * Fixed as well. Take further reports to . <b style="border:1px solid #10a"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b></b>  22:07, 11 September 2020 (UTC)
 * I think they could be implemented into shortcut redirects, but implementing them as aliases would require modifying the wiki software. Also, I prefer CAT: over C: for categories. Fadyblok240 (talk) 20:34, 11 September 2020 (UTC)
 * ---HumiebeeDiscuss anything with me Look at my edits 20:39, 11 September 2020 (UTC)
 * I don't see the point of most of these, they would add confusion since most other wikis don't have these abbreviations. The only ones that I support are Minecraft Dungeons/Earth talk since these are more of a handful to type out, and are more likely to be linked to (as opposed to the MediaWiki namespaces, for example). – Sonicwave talk  22:14, 11 September 2020 (UTC)
 * I agree with you, especially about the talk pages of non-article pages except for the Minecraft Wiki: namespace. Even Wikipedia doesn't have alias for most types of talk pages. Fadyblok240 (talk) 22:52, 11 September 2020 (UTC)
 * changing, except MDT and MET. Sry, but shortcuts are SHORT-CUTS. So it is for shorter things, and for things, which won't get confused. This means, it is for project talks or ns with more then 8 characters. And MediaWiki, NO! I don't know, how it will work, but MediaWiki shouldn't be shortcutted in any way! I don't want, that users will easily get to MediaWiki ns. Also, special pages,... No! --TreeIsLife (talk) 17:43, 12 September 2020 (UTC)
 * Why oppose special pages and templates? You gave no reason for special pages and templates have more than 8 characters and I use them as search terms a lot---HumiebeeDiscuss anything with me Look at my edits 22:12, 12 September 2020 (UTC)
 * with sl and example of course by Nixinova. The only issue is that it shows in  ---HumiebeeDiscuss anything with me Look at my edits 20:10, 12 September 2020 (UTC)
 * I'll fix the wanted pages thing, however these still don't go towards making universal namespace shortcuts. <b style="border:1px solid #10a"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b></b>  20:12, 12 September 2020 (UTC)
 * Wait actually you just have to do sl, does it still come up in ?---HumiebeeDiscuss anything with me Look at my edits 20:29, 12 September 2020 (UTC)
 * Well, with sl, i'm not oppose, i only was scared, if many users, which want to browse wiki content will see MediaWiki:Hydra.css by just MDW or other things, which are not wiki content.--TreeIsLife (talk) 19:51, 13 September 2020 (UTC)
 * Why would they type media wiki in the first place? You would type the shortcut if you knew the destanation and as for sl, if they saw the link and pressed it, they would just press the back button (an example of this "back button" sense is .---HumiebeeDiscuss anything with me Look at my edits 20:47, 13 September 2020 (UTC)
 * This is already partially implemented with sl, however, for this to be 100% implemented, would have to be implemented to MediaWiki:common.js, however, tjis will need a consensus. There still has not been a clear answer but it seems like User:Nixinova is support and User:TreeIsLife is Oppose. Any thoughts or clear opinions?---HumiebeeDiscuss anything with me Look at my edits 20:52, 13 September 2020 (UTC)
 * for most talk namespaces and site-wide automatic implementation. Even Wikipedia doesn't use shortcuts for most namespaces. We should use shortcuts on a page-by-page basis, meaning we can abbreviate the page name, not just the namespace. Fadyblok240 (talk) 22:45, 13 September 2020 (UTC)
 * Putting shortcuts on pages? There are so much more pages then shortcuts, I don't get why your proposing this and your only reason for opposition was


 * do you have any more opposition reasons? I mean the shortcut for searching substitutes it, not like normal Ex:If i'm searching MCT:CP, MCT doesn't turn into Minecraft Wiki talk:whatever page, it keeps it but this commons.js thing does this, T:Golden Apple->Talk:Golden Apple. Again, it's helpful and I don't see anything wrong, it's nice and convenient, also you have to put T: (colon) so it won't affect normal searching---HumiebeeDiscuss anything with me Look at my edits 00:19, 14 September 2020 (UTC)
 * as this is a quality of life change that assists editors and viewers. I really don't see any real problems, and no technical issues as of what I know. Blockofnetherite Talk Contributions 00:14, 15 September 2020 (UTC)
 * I am still about this idea. This is bad idea with auto redirect. Yes, even Wikipedia has no "shortcut ns". What you see like WP:R is basicly an article with redirect. Sry, but not everything is good. --TreeIsLife (talk) 18:04, 15 September 2020 (UTC)
 * per above reasons. TheGreatSpring (talk) 10:32, 18 September 2020 (UTC)

New proposal
It looks like the most support is headed towards implement for only MET and MDT and the others are not really nessicary, so would you support just I feel like MD and ME could also be helpful (so that is why I added it to the list)---HumiebeeDiscuss anything with me Look at my edits 22:37, 19 September 2020 (UTC)
 * 1) Only MDT and MET
 * MD, ME, MDT, MET
 * 1) Everything on my definitely list (+ MD and ME)
 * 2) Everything except Gadget, Widget, and their talk and definition variants.
 * 3) Everything


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


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


 * Certainly Option 1 at least. I dislike the idea of CAT shortening (suggested by Fadyblok) because no category uses short names like Minecraft Wiki pages or even some templates do. Help shortening does seem to be helpful, the same may apply for templates, and if both these get shortcuts, then their talk pages should probably have them as well (HT and TT). But implementing shortcuts for all namespaces just for the sake of it is certainly not worth the effort.
 * On a side note, why exactly MDT and MET? The respective article namespaces are abbreviated MCD and MCE. Unless such shortenings are limited to three letters for some reason, I’d suggest using MCDT and MCET respectively for the sake of consistency (though, we already have MCT for Minecraft Wiki talk...). — <b style="line-height:19px;letter-spacing:1px"> Babylon A S </b> *Happy Camper* 06:27, 25 September 2020 (UTC)
 * For consistancy that is (all namespaces has 3 letter) and yes, it would be consistant with MCT (it's not MCWT))---HumiebeeDiscuss anything with me Look at my edits 14:11, 26 September 2020 (UTC)
 * Option 1 TheGreatSpring (talk) 06:58, 25 September 2020 (UTC)
 * Still staying with per my above reason. Just don't see anything wrong with this addition, saving characters is useful. Blockofnetherite Talk Contributions 19:31, 1 October 2020 (UTC)

Add sort keys for version exclusive articles (including articles about versions themselves)
I think it would benefit to add sort keys to remove prefixes from version exclusive articles. (e.g. the sort key for Java Edition level format would be Level format) It would provide a better ordering of lists of pages in version exclusive categories. Fadyblok240 (talk) 21:10, 12 September 2020 (UTC)
 * Go ahead, this should be an uncontroversial change. <b style="border:1px solid #10a"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b></b>  22:10, 12 September 2020 (UTC)
 * It may take a long time to add all the sort keys for the version articles. Maybe consider modifying or creating templates (see ) to automatically create the sort key? Meanwhile, I will add sort keys for articles that are not about versions. Fadyblok240 (talk) 22:21, 12 September 2020 (UTC)

Change the main discussion from MCT:CP to MCW:Centralized discussion
This is a very big change proposal but I have some reasons to back it up. ---HumiebeeDiscuss anything with me Look at my edits 22:14, 28 September 2020 (UTC)
 * 1) This page should be used for discussing the Community Portal itself
 * 2) The ftb wiki does this as well
 * 3) It could be linked on the sidebar (as centralized discussion)
 * 4) How did this name start anyways?
 * 5) There is not any page to describe this main community discussion, now that it is in MCW namespace instead of MCT namespace, it could have a proper talk page.
 * 6) This would be an enourmus change and could break a lot of links.
 * 7) However, I will try to fix the links
 * 8) However, it fits more nicely


 * The community portal page itself needs almost no discussion as most of it is requesting pages or linking other discussions, I don't see a need for a dedicated talk page. This page is the portal to community, including community discussion, so the name seems clear enough to me. Plus, centralized discussion can lead to confusion, such as that the page is the only place we discuss wiki topics. Additionally, as you said, this is a huge change which will break basically any reference to the portal; none of the benefits you listed outweigh breaking all links from former discussions. – KnightMiner  · (t) 16:08, 29 September 2020 (UTC)
 * Looking at the What links here tool, 214 pages link here, and since at least like 50 of them are like redirects and duplicates (yes if it shows a redirect, it shows it indented below the redirect AND as normal) so it shouldn't be such a hard task. Since this page would not be used as much, it's redirects could just change without worry of the actual page, and like you said, if there is no discussion, it could temporaraly become a redirect while the links try to be fixed.---HumiebeeDiscuss anything with me Look at my edits 22:24, 30 September 2020 (UTC)


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


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


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

suppressredirect permission, UCP, and autopatrolled users
On UCP, regular users won't have the permission to move pages without leaving a redirect. This permission will become admin-only. Since there are valid use cases for non-admins using this permission, but concerns with all users having it, I propose to grant autopatrolled users and patrollers this right. Non-English Minecraft Wikis may have other custom groups that they feel should not lose this right and aren't going to cause much damage with it; if so, I encourage the users of these wikis to list these groups here. See also the Wikipedia group that inspired this proposal. --AttemptToCallNil (report bug, view backtrace) 12:40, 2 October 2020 (UTC)
 * Is moving without redirect vandalism (or in general bad edits) really common though? because if not, I see no reason to take that permission from anyone who may not have autopatroller rights. Dhranios (talk) 13:10, 2 October 2020 (UTC)


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


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


 * I added the  permission to the following groups:
 * en: Patrollers, Autopatrol
 * es: Patrulleros
 * pl: Redaktorzy
 * pt: Patrulheiros
 * zh: 巡查员
 * -- HorseHead.png Gamepedia icon.png MarkusRost (talk) 22:50, 2 October 2020 (UTC)

Comparison of Lua-based templates and non-Lua counterparts
According to Template:SimpleNavbox/doc, Lua-based templates seem to be slower than their non-Lua counterparts, contrary to the situation on Wikipedia. This might change when the Minecraft Wiki is transferred to the UCP. I want someone to prove or disprove the statement that Lua runs slower than parser functions, before and after migration to the UCP. Fadyblok240 (talk) 02:26, 3 October 2020 (UTC)
 * That template is not a useful general judgement for Lua vs. wikitext. In fact, in many cases Lua-based templates are going to be faster. In addition, with UCP we are expected to eventually get LuaSandbox, an extension that makes Lua even faster. --AttemptToCallNil (report bug, view backtrace) 04:33, 3 October 2020 (UTC)

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

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

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

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

Here are options for Planned Additions
 * 1) Have Planned Additions on Caves & Cliffs page
 * 2) Have Planned Additions on Java Edition 1.17

Options for Planned Fixes
 * 1) Have it on update page
 * 2) Have it seperate page
 * 3) Don't have it

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


 * With Planned additions, i Option 2, and with Planned Fixes also ing Option 2. --TreeIsLife (talk) 19:16, 3 October 2020 (UTC)
 * Planned additions go on the Caves & Cliffs page for now, and is transcluded on JE & BE 1.17, but fixes are edition-specific and should go on their respective pages. <b style="border:1px solid #10a"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b></b>  19:45, 3 October 2020 (UTC)
 * Maximally, we could make subpage for entire update content, like Legacy Console Edition has.

Smash content
Hi hi. I'm not a regular editor of the Minecraft Wiki, but rather a visitor from SmashWiki, which—as you can imagine—has been busy with the reveal of Steve and company in SSBU. I was curious as to how you all are going to handle the Minecraft content in Smash. We're already linking to you on a few pages, and I've proposed making a formal partnership between wikis to higher-ups on SmashWiki, but it's still in discussion right now. I suppose right now I just want to ask and gauge interest, since there doesn't seem to be much about Smash on this wiki right now. Is Smash content something you would like to further elaborate on for the wiki, and if so, would partnership (being able to reference and cross-link us where necessary) be of any interest? DryKirby64 (talk) 00:50, 5 October 2020 (UTC)
 * There's some discussing over at Talk:Super Smash Bros., and personally I think we should indeed document it here. Not sure where exactly, though. <b style="border:1px solid #10a"> Nixinova </b> <b style="border:1px solid #06f"> T </b> <b style="border:1px solid #0af"> C </b></b>  00:53, 5 October 2020 (UTC)