Talk:Java Edition 1.13

Semi-protection
Please semi-protect the page of 1.13 like other versions.-- 17:02, 15 April 2017 (UTC)

Block states in /give etc.
I don't think the bug report was read correctly, near the top of the ticket it states "Other changes: Damage parameter should be removed from /replaceitem, /clear and /give." as well as "Damage tag should be moved to the tag tag {Damage:0}" -FVbico (talk) 14:28, 16 April 2017 (UTC + 1:00)
 * Indeed I may have read it incorrectly. You are closer to that bug report, please rewrite the article as you see fit. – Sealbudsman talk/contr 14:46, 16 April 2017 (UTC)
 * Should it be moved to the Confirmed features? Dinnerbone now specifically mentioned the flattening in a reply if commands will auto update "They could, sometimes! But a lot of things aren't really autofixable, they'd need a human to decide stuff. Mostly about the flattening." (https://twitter.com/Dinnerbone/status/887941459902689280) -FVbico (talk) 10:37, 20 July 2017 (UTC + 1:00)
 * Looks like enough confirmation that the flattening is coming in 1.13 to me. What do you think is included with the term "flattening"? Is it just giving the variant/color/type blockstates their own block or does it also include all the other stuff regarding damage and removing block entities for flower pots etc? --Pepijn (talk) 12:04, 20 July 2017 (UTC)
 * All of those things you just mentioned are included with the flattening(I created the list on the bug report as grum was making the changes), splitting the blocks and as such damage values and flower pot block entity removal too as they are part of that split, nothing is said what will happen to maps or beds (block form) though, so that may be worth mentioning separately. To quote grum on the bug tracker: "Some things might change in the future but parts of the list is what I am working on indeed. So <3 [Mod] FVbico (Steven Verberne) for the effort involved with keeping it somewhat up2date with my random ramblings" -FVbico (talk) 14:51, 20 July 2017 (UTC + 1:00)

DataTag
How to understand "/scoreboard had [dataTag] removed from its commands, as they're no longer needed."? — RDmitriyS (talk) 18:43, 23 July 2017 (UTC)
 * It's because of the selector argument nbt= being added; making the command argument unnecessarily -FVbico (talk) 22:22, 23 July 2017 (UTC + 1:00)

Command Syntax
A lot of information on this page comes from Dinnerbone's Reddit post about major changes in 1.13. In this post, DB uses a syntax for commands which is different from the command syntax of this wiki but DB's syntax is very very likely going to be used ingame for the new command UI. I made a topic on the Talk:Commands page about switching the entire Wiki to DB's syntax (and when to do it). Regardless of when we will update the entire wiki to this new syntax, I suggest we keep the new syntax on this page. The places where this syntax is used on this page are directly copied from DB's post, converting the syntax is extra work and just makes it inconsistent with its source. So please do NOT edit/revert edits regarding the syntax of commands back to the wiki syntax. Instead, post your opinion and reasoning here first. We don't want to start edit wars over the syntax. --Pepijn (talk) 20:58, 11 August 2017 (UTC)

Link to 1.14
There used to be a small section on the planned versions page that said that 1.14 might include survival changes. It is now removed from the page, but there is still a link from 1.13 to the planned versions page, specifically the 1.14 section that no longer exists. Should the link be removed?
 * Kagenari Nagumo (talk) 13:21, 22 August 2017 (UTC)
 * . Makes no sense to keep a link to a useless redirect. --Pepijn (talk) 13:26, 22 August 2017 (UTC)

Texture changes
So it was finally confirmed that the texture changes were not going to happen in 1.13 (most people already had a feeling this wouldn't happen, but it was never confirmed by Mojang). I suggest we remove the information about the textures (text and images) from here since they have nothing to do with 1.13. by BDJP007301. --Pepijn (talk) 10:43, 17 October 2017 (UTC)

Shorthand values for commands
I, for one, believe these should be kept for ease of use. Any mention on the reasoning behind the planned removal? Superjedi224 (talk) 19:50, 26 October 2017 (UTC)
 * Out of the scope of this wiki, but shorthand notations are ambiguous (which is bad practice). Tab completion is a thing, so there's no need to type out the whole word in most cases anyway. --Pepijn (talk) 22:14, 26 October 2017 (UTC)

Repeat Execute Chat Spam
Is there a way to stop the chat from getting spammed when using execute in a repeating command block?

--MCweb 19:40, 12 November 2017 (UTC)


 * There are two gamerules that you have to activate. The gamerule CommandBlockOutput stops them from spamming the chat. However, it will still spam the logs. Use the gamerule LogAdminCommands to stop that from happening. Hope that helps!


 * Gregatron6000 (talk) 20:42, 12 November 2017 (UTC)


 * However, there is currently a bug (https://bugs.mojang.com/browse/MC-121783) preventing gamerules from being changed via /gamerule. An NBT editor is required to change gamerules in level.dat, or waiting for the next snapshot for the bug to be fixed. Skylinerw (talk) 20:46, 12 November 2017 (UTC)


 * That’s a really odd bug. I haven’t been playing in the snapshots, so sorry for the irrelevant information.


 * NBTExplorer is a really good NBT editor. I personally don’t use it unless I’m trying to build an iron farm, to verify how many villages I have.


 * Gregatron6000 (talk) 02:46, 13 November 2017 (UTC)

Listing name/id changes on this page
I personally think we should at least list the name and id changes on this page. Maybe we could set up a table to help with organization? -PancakeMan77 (talk) 18:52, 26 November 2017 (UTC)
 * That is in 1.13/Flattening, which is linked on this page. Listing all changes that are part of the flattening is too much for this page, where you may want to just look through the overal changes FVbico (talk) 19:24, 26 November 2017 (UTC)

The flattening
Stop repeating, misplacing, splitting up and deleting information. Some examples: We do not need to list here that golden apples have been split up, that falls under the flattening which is already linked; We do not need to have one individual subsection for trapdoors, buttons etc just to tell they ALL got the other wood variants; The bark blocks got split up (which falls under the flattening), the block form of bark has no changes besides this. the ITEM form of the bark block was added, so it falls under item additions. --Pepijn (talk) 11:33, 27 November 2017 (UTC)


 * Please consider addressing others with a little more courtesy, in your edit summaries. The practice of making the version page a comprehensive change log is a long standing one, and if we have recently decided otherwise with respect to the flattening page, we don't need to assume incompetence or malice. – Sealbudsman talk/contr 12:20, 27 November 2017 (UTC)


 * Unrelated to this talk page, take it to me personally on my talk page if you have a problem with something. --Pepijn (talk) 12:44, 27 November 2017 (UTC)


 * I view the Flattening subpage as a necessary diversion from our normal practice, owing to the sheer length of changes. That being said, I'm surprised I haven't seen anyone suggesting to include it on the version page in a collapsible element yet (though note I'm not making that suggestion myself; I personally don't like hiding article content in collapsible sections). 「 ディノ 奴 千？！ 」? · ☎ Dinoguy1000 17:47, 27 November 2017 (UTC)


 * I think part of the problem is that some changes (especially name changes) aren't obvious that they would be on that page. And even if it was, it's still hard to find all the name changes there. This might be better for that page, but I think it might need some better organization. -PancakeMan77 (talk) 22:11, 28 November 2017 (UTC)


 * Maybe, we could arrange the blocks/items by the order in which they appear in the Creative Mode inventory. So, we have blocks, then decoration, then redstone, etc. “Flattened” blocks that are not in the Creative Menu can be listed after all of these, sorted by ID. By doing this, we can also split the page into separate sections, making it easier to edit and view.


 * Gregatron6000 (talk) 00:01, 29 November 2017 (UTC)