Include a history section?
Should we include a history section on this page? I'm leaning towards no, as it would require a lot of research to go back and document old changes. Maybe have a note at the top of the history section that it only catalogs changes from 1.14 onwards? -PancakeIdentity (talk) 23:57, 14 June 2019 (UTC)
- Whenever you are asking the question "should History be added?" the answer will always be yes. – Nixinova 23:58, 14 June 2019 (UTC)
Should this page be integrated into main articles yet?
I just discovered this page's existence as a result of an edit to Redstone Comparator replacing some of its block placement limitations with a link to here. Based on WhatLinksHere, I assume similar edits were made to other pages. I question whether that's a good idea. Does it really benefit the reader to break up the list of block placement limitations, sending them to a separate page for just the transparent ones, where they have to find the information they need in a table that is mostly irrelevant to what they were trying to learn? As a reader, I find that quite annoying. I realize that avoiding redundant information makes the wiki easier to maintain, but it shouldn't be done at the expense of the reader's convenience.
I also question whether the page's scope is broad enough. It was created in 2015, when Java Edition was the only version, and it mentions no differences for other editions. I'd be astounded if all this information is accurate for all of them. I suggest that it shouldn't be integrated into articles intended for all editions if it isn't relevant to all of them, especially since it doesn't even mention that the information is only for Java.
I would also say that it needs more explanation about what's included in the tables. For instance, the table for "placing on top" includes columns only for certain blocks. I expected to find Brewing Stand there. Is that an accidental omission, or does it not fit the criteria you used to decide which blocks to include? The section should describe the criteria used to select blocks for its rows and columns. – Auldrick (talk · contribs) 16:36, 22 June 2019 (UTC)
- For the first point, I'd be open to adding the relevant info to each page, though I don't think this page should be removed. For the second point, this was created this year, and I am the only person who's really done anything with it. I don't have access to any other versions, so I wasn't able to add them here. If someone could help me expand this page, that'd be great. For the third point, I only included A) Blocks that actually had some sort of unique behavior (for example, glass wasn't included because everything can be placed on it) and B) Blocks that can't stand alone. Brewing stands don't need a support block, but blocks like a comparator do.
- For placing this on each item's own page, I do worry that it adds too much technical info that most players won't really care about. I'd be open to it, but I think it definitely needs more discussion. I'll also work on clarifying what is actually covered on this page. -PancakeIdentity (talk) 18:59, 22 June 2019 (UTC)
move this page
If another block can attach to that block, we call that block a solid block. Attachment depends on whether it is a solid block, regardless of opacity. how about moving the page to solid block/Placement.--Chixvv (talk) 10:18, 20 July 2019 (UTC)
- Strong Oppose. This is under "Opacity" as that's the parent page that discusses transparency. In addition, None of the blocks here can be truly classified as solid. -PancakeIdentity (talk) 16:57, 20 July 2019 (UTC)