Eat crops straight from the ground with EatWheat!


EatWheat allows players to eat ripe crops directly from below their feet, with tons of configurable options. It's actually pretty fun, and is very useful on true survival servers. 1.7.2 is up! Don't forget to head over to the subscriptions page to get updates!.


  • Eat crops directly from the ground
  • Will listen to every and any protection plugin, and even logs every crop eat as a block break
  • Optionally set a customizable, colorable message to appear upon eating a crop
  • Easily customize how much eating a crop will feed and heal a player
  • Permissions support
  • Sound effects!
  • Almost guaranteed to have no loopholes or bugs


Just walk up to a fully-grown crop, right-click it, and EatWheat does the rest. By default, a player is fed 1 food bar upon eating a crop, one-third of what bread (three pieces of wheat) will heal you, but health can be configured to be given as well, and both are completely customizable. EatWheat even obeys every protection plugin, including vanilla Minecraft's spawn radius protection. If you can't break it, you can't eat it.


  • /eatwheat - Plugin info and help
  • /eatwheat reload - Reloads the local configuration file from the disk
  • /eatwheat config - Provides quick, clean, human-readable information about what the current EatWheat settings are.


  • eatwheat.* - Gives holder every EatWheat permission
  • eatwheat.eatcrops - Allows holder to eat crops with EatWheat
  • eatwheat.reload - Allows holder to use /eatwheat reload
  • eatwheat.config - Allows holder to use /eatwheat config


Please see the configuration help page.


EatWheat uses the metrics data tracker, which submits lightweight, anonymous data to the metrics website, like how many times my plugin has been started and how many people are using it. If you want to disable this harmless feature, you may set "opt-out" to "true" in the "PluginMetrics" folder of your plugin directory.

To-do list:
  • Nothing here yet, but I'd love to hear some new ideas!
  • None at the moment!

I spend literally 90% of the time I develop plugins just bug fixing and adding failsafes to every scenario I can think of. I try as hard as I can to make sure my plugins never have any bugs or loopholes, and they go through rigorous testing before every release. That being said, if there's anything I missed, please let me know.


Posts Quoted:
Clear All Quotes

About This Project


Recent Files