0.5 Breaking Changes
This page explains all the breaking changes caused by the 0.5 update for Farmer's Delight.
Please review these changes carefully when migrating old saves, or when updating add-ons, resource packs and datapacks. And of course, as with every update, remember the golden rule: BACKUP YOUR WORLDS!
When first introduced, the Rice crop worked like a double plant: if one half broke, the other broke as well.
On version 0.3.2, the Rice crop was updated to a new block, where each half was independent. The bottom one is waterlogged, and periodically grows a top half which yields Rice Panicles.
The Rice seed has been planting the new form ever since that update. Both old and new rice blocks have separate IDs, which allowed old Rice crops to still exist when updating the mod, although they were no longer plantable.
In version 0.5, the old form of Rice has been removed from the game. This means that, if your world still has the old form planted somewhere, these blocks will be erased permanently on world load! So make sure your Rice has been replanted before updating an old save, or else you'll lose your Rice crops!
Old Rice (tall_rice_crop) is yellower and more saturated than New Rice (rice_upper_crop), and breaks when either half is mined. You can use F3 to check ID's.
The following blocks had their models updated, so resource packs may require an update:
- Cooking Pot (textures split in 16x files, new handle texture);
- Basket (different cube shaping, extra top texture);
0.5 modifies the Cooking Pot's blockstates a bit, swapping the old down boolean for a new support enum:
nonetrayhandle
This means that, when loading your saves, all placed Cooking Pots will lose their tray temporarily. This is a cosmetic change, and can be fixed in the following ways:
- Mine and place the Cooking Pot again;
- Sneak-use (shift + right-click) the pot to toggle between handle and tray states.
Add-on makers: some internal classes have been reordered to be more organized. This may break things if you're directly referencing them; make sure to check if your add-on is working as intended with the 0.5 version.