Talk:Caves & Cliffs

Merge Pages
Wouldn't it be easier to merge the pages from Java 1.17 with bedrock 1.17.0? They are practically the same and few things change. We could put a section on the Caves & Cliffs page about unique changes in these editions (or bug fixes). it would be easier and less unnecessary copy paste, and everyone would just know where to edit new update freatures. (I also suggest doing it to all update pages). The pages with small updates could be separate again, like 1.17.2, 1.17.3, 1.17.4...L7876 (talk) 19:53, 17 January 2021 (UTC)
 * No, the editions have different features right now, and goats shouldn't be listed as added yet on the java end, and skulk sensors vice versa. Additionally, there's guarenteed to be changes between the editions at the time of release too, even 1.16 had differences, despite being parity checked. Dhranios (talk) (Join the wiki videos project!) 20:15, 17 January 2021 (UTC)
 * Well, at least some time the resources will mix, the features that are different will be in the minority as the version is still being tested. That is why I said that at least one section on the page should be created for them, (In the future when the version finally comes out). These differences are not a big deal at all.L7876 (talk) 20:48, 17 January 2021 (UTC)
 * sorry if i'm too dramatic I oppose becuase of consistancy. Java 1.16 is different than Be 1.16. Also think about bug fixes and other things. Also what would you even call the page? Temporarily merging the pages just creates a lot of mess with cleaning up the pages. Also Dhranios is a long time contributer and administator and i'm 100% sure that an admin would be more reliable than a new user.Humiebee (talk) 23:43, 17 January 2021 (UTC)
 * Not getting anyone's point, what do you mean by calling the page what? It would be just a mix! Also why not doing this at least in the future? And i dont know what do you mean by "bug fixes and other things" since i already said thats not a big thing, likes it is a confusion (Just create a new section with the bedrock and java bug fixes so that the reader can distinguish it). Think I will try to create a test page, to prove that "new users" can also be trust wordy.L7876 (talk) 13:37, 18 January 2021 (UTC)
 * It seems humbiebee was a bit unsure what you meant. The point we're trying to make clear is that there's still going to be numerous exclusive changes, even if mojang is focusing on parity within the update. A bug fix can result in a change to something's behavior, that should be mentioned outside the bug fixes section too.
 * Having 1 page listing 2 updates (even if the same *base* update) is going to get really messy really quickly. We separate pages across the wiki a lot if the editions are different enough, and updates are not an exception. Think of the command system, it is very different between editions, or data packs/ad-on scripting, those are exclusives to their editions and shouldn't be listed on the others'.
 * The moment you get a page with "both, java, bedrock", you're asking to reader to look all over the page for the changes to, eg, data packs, while keeping it separate pages only asks them to look at 1 place. The readers are generally interested only in 1 edition. Dhranios (talk) (Join the wiki videos project!) 13:44, 18 January 2021 (UTC)
 * Ok, thanks for being more clear i got your point now. But theres a way to create a test page here? Like wikipedia? L7876 (talk) 13:52, 18 January 2021 (UTC)
 * Per the discussion, I wouldn't reccomend you to do that, but if you would like to test it, you can do that on your user page (or a subpage of it), but remember that you should clear it when you finish testing. Your user page won't be deleted if you specify that you are testing something, because it takes space. The best option would be the Sandbox page, where you can edit freely folowing the rules and style guide; however the edits made there are undone after a while, so it's your own decision. Anyway, Dhranios already explained why it wouldn't be a good idea, and I think that you should listen to him, but you are free to decide . Thejoaqui777 (talk) 14:02, 18 January 2021 (UTC)
 * for a few reasons. Firstly, it passively promotes parity, a problem that a lot of people are worried about. Secondly, It makes comparing the two versions easier if there is not perfect parity. Lastly, it is less confusing to casual readers who are new and don't understand the difference between the two. --TurtleOutLoud (talk) 18:23, 25 March 2021 (UTC)
 * because honestly, I feel like it would be more confusing to new readers, not less. If they notice the edition listed at the top, that shows a decent indicator of whether or not features will work on their version. If they look up which version they are on before or after testing an edition exclusive feature, it makes it much easier for them to find fun ones they can use in their version. My first introduction to the fact that there were two versions of Minecraft was in testing out one of the Java Edition features and wondering why it didn't work. From there, I was able to learn about them and know which one directly applied to me. The fact that both versions will always be significantly different from each other programming-wise is another argument against it. Because the programming languages are different, the bug fixes will always be significantly different, even if the features are the same. If players want a page that shows parity, the main update pages like Caves & Cliffs are where they should go, not the version update pages. PegasusDust (talk) 03:49, 26 March 2021 (UTC)
 * It would just be extremly messy. What would you do, put 1st level headers? That just destroys the purpose of the merge. Also, there is Official pages/Parity issue list.Humiebeetalk contribs 19:51, 29 March 2021 (UTC)

Protect the page
Can somebody protect the page and disallow ips from editing it? Most of the ip edits just get undone because they have some problem. 18:32, 1 March 2021 (UTC) hmm...I do not know how to but an admin can help you--Jadon0506 (talk) 00:18, 22 April 2021 (UTC)Jadon

Can Someone add the new Bedrock mountain biomes?
I don't see why they shouldn't be on this page since they are part of the update. Miraculer89 (talk) 11:54, 7 March 2021 (UTC)
 * They are mentioned briefly under the world generation section. However, I could see how it would make sense to at least put a little more information about them to the biomes section, even if the section on mountains stays where it is. PegasusDust (talk) 04:57, 9 March 2021 (UTC)
 * to be consistant with Goat.Humiebeetalk contribs 19:51, 29 March 2021 (UTC)

Labeling the caves as "Java Edition Only" and mountains as "Bedrock Edition Only"
On the page, the new cave generation is labeled as "Java Edition Only", and the new mountains are labeled as "Bedrock Edition Only". I know that this is because the cave generation is only in the snapshots and the mountains are only in the betas, but the wording makes it sound like one version is only going to get one half of the terrain generation in the full update. I'd change this, but I don't know if it's meant to be worded this way?
 * Personally, I think it also should be changed, but for consistency I think that is how it is supposed to be worded. --TurtleOutLoud (talk) 21:49, 1 April 2021 (UTC)
 * It sounded that way to me at first when I started reading this website a few years ago. The reason they have that is because currently only one edition has those features, even though both will eventually get both. However, there has been a recent change where pages that contain features currently exclusive to one edition can have the other edition as "planned" if it has been confirmed that it will receive them. Maybe you could ask for a template like that? I'm not certain how to do that, but it seems like a possibility. PegasusDust (talk) 03:56, 2 April 2021 (UTC)

why is the update two parts
why is the update two parts--Jadon0506 (talk) 23:09, 14 April 2021 (UTC)Jadon
 * See the new video posted on Minecraft official YouTube channel. Windwend (talk) 00:11, 15 April 2021 (UTC)

Skulk Trap
This is just an idea, but I think the Skulk Trap will be a block that will either detect if someone (or something) is on top of it, or it will grab the player and send a redstone single. This is just an idea :D 70.181.135.90 02:21, 26 April 2021 (UTC)
 * It is an interesting one, but "just ideas" shouldn't be added to the main page. PegasusDust (talk) 04:29, 27 April 2021 (UTC)

Sculk Sensor
If the sculk sensor is going to be in 1.17, does that mean the warden will be in 1.17? Because wardens attract vibrations from sculk. – Unsigned comment added by Zachbarbo (talk • contribs) at 19:31, 28 April 2021‎ (UTC). Sign comments with
 * The sculk sensor will be commands-only in 1.17; both will be fully implemented in 1.18.  Nixinova   T   C   21:38, 28 April 2021 (UTC)

Warden
Why can’t the warden be released on 1.17? – Unsigned comment added by Zachbarbo (talk • contribs) at 14:32, 28 April 2021 (UTC). Sign comments with

Underground cabin
If the underground cabin may appear in 1.17, doesn’t that mean the warden will appear? – Unsigned comment added by Zachbarbo (talk • contribs) at 23:33, 28 April 2021 (UTC). Sign comments with
 * I honestly doubt that it will. Kingbdogz, the main deep dark developer, has mentioned that many of the deep dark features will be postponed till 1.18, since the world generation, warden mechanics, and new blocks are interwoven a lot. There's a small chance that they might add underground structures that will eventually be added to the deep dark, but without the warden to balance out their loot tables and without the generation and blocks to make the experience immersive, I seriously doubt that any deep dark structures will be added in 1.17, whether underground cabin or otherwise. Also, Kingbdogz has confirmed that the warden is definitely coming in 1.18, not 1.17, for the reasons listed above. It's a little sad, but at least we have a lot to look forward to. PegasusDust (talk) 04:58, 29 April 2021 (UTC)