The bug
Fields can sometimes spawn in such a way that some parts of them are so dark that crops will drop when planted.
How to reproduce
Note: This seed and the coordinates do not produce such a field structure anymore in the latest versions. If you find a village where this is the case please comment on this report.
Seed: -60702326697312579
Coordinates: /tp -760 67 875
Related issues
is duplicated by
relates to
Attachments
Comments


Unrelated to this specific issue, your Java is very, very badly out of date and will invalidate almost any ticket you place here, as well as being a major security risk to your computer. I would strongly recommend updating to the latest Java 1.7 or 1.8 versions if possible.
Secondly, may I say that is an awesome village spawn...

Please update your Java to the latest version (1.7.0_72 / 1.8.0_25): http://www.java.com/en/download/.
When using a 32-bit browser on a 64-bit operating system the automatic version detection will only show the 32-bit version of Java, the 64-bit version needs to be downloaded manually: http://www.java.com/en/download/manual.jsp.

Confirmed, but I doubt that this will be fixed as this falls in the category "lovely terrain generator quirks", see MC-610

Confirmed that the village generates that way. Of course that's a MC-610, but it's still a bug that villagers try to plant at too dark spots.
BTW at spawn of that seed is a village house with grass blocks in the village house, another 'lovely terrain generator quirk'...

@@unknown That other issue is MC-73880

Thank you very much for the information, that my Java is out of date, I changed this once to test something and forgot to use the latest version again 😞
Thank you very very very much 😉

The provided seed and coordinates do not generate such a field structure anymore because the village generation changed. However, villagers still plant seeds when it is too dark, which I put into MC-112971.
Cannot reproduce with this seed in 1.12.1. It seems like the field has moved up and some structures in the village slightly changed. (see attached screenshot)

Please check if this is also an issue in the 1.13 pre-release.