The wiki says:
Removed attribute ID prefixes such as generic.
. Changed formats of data components, loot tables and predicates. Added new data components, loot tables and item tags. Added key input predicate. Added crafting_transmute
recipe type. Renamed enchantment effect damage_item
to change_item_damage
No mention of changes to format for recipes
I'm also seeing this problem. Villagers have been given bread, potatoes, beetroot until they won't pick up any more. There are three times as many beds as villagers but they still generate anger particles.
EDIT: I managed to get them to breed (once, so far) by placing eight extra beds in the open next to the meeting point. They apparently can't see most of the ones in houses.
I have just observed this in 1.14.3 probably the baby zombie spawned just before I switched to Peaceful via the command line.
[media]MC-134816 doesn't mention not being able to pick up, and in my case it does not always crash. I think the not picking up is a separate issue.
Singleplayer world upgraded from 1.12.2 to 1.13, played in 1.13, does not exhibit this issue.
I had removed Minecraft from my multiple monitor configuration PC because of the issue.
I just reinstalled it and the log window no longer opens minimised.
Mark as fixed?
Wrong window - it was the log window, not the launcher.
Still in 18w01a
Also in 17w50a.
This is really annoying.
It's possible to select from the commands/arguments list with the mouse, so it doesn't need up/down key navigation.
Whereas losing command history navigation is a real pain.
Ely: I have not seen any evidence of your (1). However it does seem to be the case that (in snapshot 17w06a at least) the re-triggering occurs only when there is redstone dust present at the output when the water arrives.
Related to MC-631
As you can see from the attached screenshot this is not just a visual glitch. Although the blocks cannot be mined, you can stand on them and cannot move through them. Also if standing on them in Survival mode, the player is kicked with the message "Flyng is not enabled on this server".
Still an issue in 1.11.2, please reopen.
As you can see from the attached screenshot this is not just a visual glitch. Although the blocks cannot be mined, you can stand on them and cannot move through them.
Likewise - MultiMC works fine with the latest NVIDIA driver, Mojang launcher does not.
Maybe the launcher is asking the driver to do something it can't do and getting an error as a result.
In that case the driver would be correct in returning an error. The driver should not always be blamed without investigation.
Confirmed for 1.11.2
Confirmed for Minecraft 1.11 Pre-Release 1
Two new screenshots showing the application that has been broken, and the workaround to fix it. It's a slow clock generator. The one without a repeater used to work - the dispenser drops water which goes around the track until it reaches the observer, which triggers the dispenser to remove the water. When it is gone the observer triggers the dispenser to drop water again. Multiple triggering of the observer makes the clock much too fast. The repeater in the next screenshot blends the double pulse into one, restoring the speed at the expense of a slight increase in complexity. There may be other applications not so easily fixable, but if this is deemed to be standard behaviour and documented I guess it can be worked with.
Update: The continual re-triggering only occurs if the output of the observer is connected to redstone dust. If instead a repeater is placed facing away from the output, or there is only air at the output it is only triggered twice when the water arrives, if this is its furthest extent/lowest level.
The same thing happens if a source block is placed in the observed location with no way for it to flow anywhere else.
If a source block is placed in the observed location with air next to it in this configuration the observer triggers three times and then stops. This is still wrong. In both cases there is only one change of state.
Although in the last case it could be argued that the source block changes from not flowing to flowing that still makes only two changes, not three.
FM: That is not the issue. In the case of the last (lowest level) block of flowing water, after the water has arrived at the observed block its level does not change, and yet the observer keeps re-triggering. Also, you can observe a block of non-flowing water (source block) and the observer keeps re-triggering. This only started happening in the last two snapshots. I have no issue with re-triggering when the level actually changes.
While fishing with rod in the right hand and nothing in the left, I selected a different slot with the mouse wheel and the fishing line moved to where it would be if fishing with the left hand.
Thanks to @Dhranios, recipes now updated.