Talk:Java Edition 1.13/Flattening
- 1 Move proposal (Done)
- 2 Light gray stained glass pane
- 3 Merge table fragment regarding banner items with the banner blocks? (Done)
- 4 Adding history section?
- 5 Reorganization proposal - Nevermind, I missed the names section somehow
- 6 Renaming pages in accordance to the "The Flattening" renamings
- 7 Numeric IDs
Move proposal (Done)
The content of this page was mainly placed here because of the French wiki doing the same. I don't feel this is really a subpage of Data values anymore however because this page is not linked on there. Instead this page is linked on the 1.13 page, so I feel this should be a subpage of 1.13. The recent content of this page is also not directly about "data values", but more about the "flattening" in general. So I would like this to be moved to either 1.13/Flattening, 1.13/The_flattening or maybe just 1.13/Data_values. My personal preference goes to 1.13/Flattening. --Pepijn (talk) 21:44, 25 July 2017 (UTC)
- I vote for 1.13/Flattening. -FVbico (talk) 23:46, 25 July 2017 (UTC+1:00)
- Seconded. - tryashtar (talk) 22:23, 25 July 2017 (UTC)
- Thirded Sun Cat (talk) 22:36, 25 July 2017 (UTC)
- Fourtheded? MinecraftPhotos4U (talk) 20:40, 26 July 2017 (UTC)
Light gray stained glass pane
In the table, I noticed that the nominal id for light gray stained glass pane is given as "light_stained_glass_pane", with no "gray" in it. I'm confident that was an accidental omission, however I don't have access to any Java 1.13 info to check.
Never mind, I realized the notes had a link to the source info so I fixed it. --– Auldrick (talk · contribs) 12:03, 29 September 2017 (UTC)
Seeing the table now lists the same IDs for
minecraft:white_banner (and other colours) for the item as for their block forms, shouldn't these be merged into the same table cells? Stating "these will have an item form" instead of mentioning them separately? I've moved the whole bunch closer together in this edit, so this might be easier. If not merged, at least they are now close together. Also, regarding sorting anyway, is there any particular sorting applied to or planned for this table at all? For instance "leaves" and "leaves2" are spread out instead of next to eachother. – Jack McKalling (t • c • p) 15:33, 14 November 2017 (UTC)
- Agreed, I merged them. For reference, the current list’s sorting is based on numeral ids, but since they’ll (basically) be gone in 1.13, we may reorder the list into how the creative inventory will look after this change has happened. FVbico (talk) 10:47, 15 November 2017 (UTC)
Adding history section?
Do you think that this page deserves a history section? I mean, we can tell when the report was made, the original plan of this happening in 1.10, the changes in commands in preparation of the flattening, etc. So, should we add it? FVbico (talk) 11:44, 29 November 2017 (UTC)
- Personally I don't think so, as the flattening was purely a subproject to improving the game, not necessarily a component of it that has relations to different versions (read: major releases). It made sense to complete this subproject within one version, and although it was substantial enough for it to have needed preparations in earlier versions, the concept of the flattening itself has only relation to just the one version it was implemented in. I would have felt differently if the changes were spread out over multiple versions, when the whole process would have existed in partial implementation in some official releases. But one could argue the implementation across different snapshots could deserve individual history entries. I don't know how the history tables usually are made. – Jack McKalling (t • c • p) 12:52, 29 November 2017 (UTC)
- Sub-pages generally don't have a history table. They're meant to be linked to from main pages. But since we can't really spam the main page (1.13) history table with this info, it might be worth it. So maybe? --Pepijn (talk) 13:07, 29 November 2017 (UTC)
- While not common practice, there's nothing preventing history sections from going onto pages like these, I don't think. I personally like to see history; most of my initial work on the wiki was digging up, fleshing out and trying to get correct history. So that's me. It's interesting information in any case. And it's a very long-planned project whose preparation came in stages, even if it was finally released in just one snapshot. – Sealbudsman talk/contr 19:14, 29 November 2017 (UTC)
Reorganization proposal - Nevermind, I missed the names section somehow
I feel this page isn't organized very well, especially if you don't already know what exactly you're looking for. My biggest issue is with the renames. It's very hard to tell which items had their names changed and which didn't. I propose some reorganization or marker(maybe a note?) to help distinguish these changes. This was discussed a little bit on the 1.13 talk page already. -PancakeMan77 (talk) 00:26, 30 November 2017 (UTC)
- As far as I can see, all renames are listed in the Names section. Are some missing?
- How exactly do you suggest to reorganize this page? This doesn't qualify as a proposal unless you've actually proposed something. 「ディノ奴千？！」? · ☎ Dinoguy1000 02:26, 30 November 2017 (UTC)
Renaming pages in accordance to the "The Flattening" renamings
I see that not all pages listed in the names section, have been renamed to their new 1.13 in-game name. Like Tall Grass has become a redirect to Grass, but the new Snow Block is still a redirect to the original Snow. Is this an in-progress project still, or intended?
Secondly, should the links in the left column of this changed names list point to a redirect of the old name, or to the new name directly but as a piped link with the old name? – ] 10:26, 7 December 2017 (UTC)[
- Page renaming will probably be done when 1.13 hits, not earlier than that. --Pepijn (talk) 12:18, 7 December 2017 (UTC)
- Before, the numeric IDs were hardcoded. Now, they're simply gone (or rather dynamically generated), and the split blocks and such mean the IDs are wildly different and change between versions. For the most part, they're too volatile to be useful for documentation. You can use the data generator system to create a dump of the IDs for the current version (although it only includes block state IDs, not block IDs which are now only used in 2 places over the network and basically nowhere else) --Pokechu22 (talk) 04:35, 6 August 2018 (UTC)