Talk:Java Edition 1.11

Setblock syntax
This page currently has a argument written in its examples for the new /setblock syntax. /setblock doesn't have a quantity argument, but the page is protected from edits, so I can't change it. –Preceding unsigned comment was added by 172.68.35.93 (talk). Please sign your posts with
 * It seems FVbico fixed it. -Xbony2 (talk) 21:03, 10 August 2016 (UTC)

16w32a public to-do list (all done)

 * Sprites
 * upload Template:InvSprite image for zombie villager egg by Majr


 * Green robe villagers
 * their name is 'Nitwit' (check the lang files, it's true)
 * The zombie villager variant spawns naturally, and the villager spawns in villages.
 * No trade menu by default, but gets one stage of proper trades when converted from a green zombie villager, no further stages unlockable
 * trades are always the tier 1 trades of the other professions. (see )
 * document on 16w32b and 1.11 the fact that these are added.
 * document addition of green robe villager on zombie and villager, and their /ED pages by Sealbudsman
 * upload green robe zombie villager render


 * Blog post items
 * "More robust handling of invalid items and hopefully less duping bugs due to this change"
 * "Lightning storm will now attract less skeleton horses"
 * also document in detail on Lightning and Horse pages
 * "Changed the duration of hunger and saturation effects"
 * Not actually a change to the duration of the hunger and saturation status effects. It's a change to how hunger and saturation themselves are affected by player actions.
 * also document in detail on Hunger pages and wherever else may be relevant


 * Husks
 * document on Zombie what has changed about husks avoiding water


 * Network IDs
 * Investigate whether there are different network IDs for Horse, guardian, skeleton and zombie variants, document on their respective pages

– Sealbudsman talk/contr 17:03, 11 August 2016 (UTC)


 * Not completely true about the nitwits, they spawn in villages too.
 * Also, the fact that they have trades on curing the zombie is a bug, see MC-106058, for your knowledge, they're always the tier 1 trades of the other professions.
 * Perhaps it's a good idea to look around on the bug tracker, before you state such things.
 * – FVbico talk/contr 20:50, 11 August 2016 (UTC+1)


 * Thanks for the tips.
 * I just copy pasted what redstonehelper had on the reddit thread, verbatim, because it was a useful starting point for investigation. Because this is just a draft, and a talk page.  Chill out.
 * Also, something being on the bug tracker per se is neither here nor there. If it's in the game, it's documentable behavior.  If the devs fix it, it gets removed.  No big deal. –  Sealbudsman talk/contr 19:17, 11 August 2016 (UTC)


 * I didn't mean to sound angry or alike, I just wanted to mention that not all information provided here was correct.
 * – FVbico talk/contr 21:21, 11 August 2016 (UTC+1)


 * I see, I apologize for misreading you. Thank you again for mentioning that stuff. – Sealbudsman talk/contr 19:31, 11 August 2016 (UTC)


 * No worries.
 * – FVbico talk/contr 21:34, 11 August 2016 (UTC+1)

Shepherd villagers now offer all types of wool
When was this added? Shepherds now offer all types of wool for 1-2 emeralds, and I don't know how long this has been ingame. Nixinova (talk) 18:35, 20 August 2016 (UTC)
 * This is a bug, the first trades of any villager are from a random profession and career, see.
 * – FVbico talk/contr 21:34, 11 August 2016 (UTC+1)

Two Shield sections
I noticed there a two sections titled Shields. Is this on purpose, should we combine them? If we do combine them, do we put them both into Gameplay or Items? -PancakeMan77 (talk) 22:04, 8 September 2016 (UTC)


 * I think it's fine, personally. – Sealbudsman talk/contr 17:39, 9 September 2016 (UTC)

16w38a public to-do list (all done)

 * On the fishing page, there's a table that should be adjusted to reflect the ink sac changes. – Sealbudsman talk/contr 19:39, 20 September 2016 (UTC)
 * – Sealbudsman talk/contr 18:45, 15 October 2016 (UTC)

Why are we putting the Minecon stuff in as if it's already been added?
Shouldn't it go in planned changes/additions? -PancakeMan77 (talk) 19:32, 25 September 2016 (UTC)


 * Was wondering the exact same thing, but the wiki didn't allow me to edit that for some reason.
 * Then again, is it really worth putting it there only to change it for the next snapshot as it'll all be contained in that one. FVbico (talk) 21:38, 25 September 2016 (UTC + 2:00)


 * Yes, it should be in Planned Additions, placing it in the regular additions section makes the article a complete mess and often leads to misinformation after the update is released.
 * If you see this happen in the future, feel free to fix as the style guide requires the Planned Additions section to be used instead – KnightMiner  t/c 19:45, 25 September 2016 (UTC)


 * Likewise, the information should not be on any other article until there actually is a snapshot with the feature. If you cannot add it to the history section with a version it stays on this article. – KnightMiner  t/c 19:54, 25 September 2016 (UTC)

New pages
Are there any more pages that I need to make that are related to 1.11 Gameplayer434 (talk) 12:41, 29 September 2016 (UTC)
 * I'm pretty sure they're all there. – Sealbudsman talk/contr 14:59, 29 September 2016 (UTC)

OK, just let me know if you want new pages because I will always make more if needed Gameplayer434 (talk) 16:00, 29 September 2016 (UTC)

Major update or small?
On the same sentence it's described both: ...is an upcoming major update... ...but still a relatively small update... –Preceding unsigned comment was added by 172.68.28.37 (talk) at 19:27, October 13, 2016‎ (UTC). Please sign your posts with
 * Right, it's a relatively small major update. – Sealbudsman talk/contr 01:21, 14 October 2016 (UTC)

Edit
in the curse of unbinding section it has 2 takes for no reason--77.100.46.169 18:32, 14 October 2016 (UTC)
 * Fixed, thanks for the heads-up. DelboyDylan (talk) 18:38, 14 October 2016 (UTC)

16w44a public to-do list

 * Observer behavior was changed. We should make sure Observer behavior is updated accordingly, specifically, what it detects and does not detect.  Also if it is now, in fact, a block-state-change detector, and not really a block-update detector, that should be considered. –  Sealbudsman talk/contr 22:10, 3 November 2016 (UTC)