Describe the bug
AutoEat TresholdModes "Any" and "Health" Should check if player has Less Than 20 hunger points before starting eating automatically.
Currently, it is not being checked. If you bring player to low health, but maintain full hunger bar, AutoEat will try to eat, even though it is not possible to eat anything. This puts player into false "eating" state.
This is not a major problem, until you check "Pause Baritone" or "Pause Auras". Then this false "eating" state will prevent baritone and kill aura from functioning, until the fake "eating" state ends. And that is not so simple
You could have thought AutoEat would exit the "eating" state when the hunger bar goes down even by just 0.5 points, which would make AutoEat actually start eating, but that doesn't happen. Because the "eating" state already started, AutoEat won't start it again until forcefully qiuting this state. And currently this can only be done by turning on and off AutoEat Module, or reconnecting with the server
To fix this you should just check if the player hunger is <= 19.5 before starting to eat.
Steps to reproduce
- Get some food in hotbar
- turn on AutoEat module
- switch TresholdMode to Any or Health
- turn on "Pause Baritone" or "Pause Auras"
- bring your health below the HealthTreshold while maintaining full hunger (ex. take a few harming potions)
Now you have entered the false eating state and you should be unable to use either baritone or kill aura until you reset AutoEat or disconnect.
Meteor Version
Meteor 1.21.4-42
Minecraft Version
MC 1.21.4
Operating System
Windows
Before submitting a bug report
Describe the bug
AutoEat TresholdModes "Any" and "Health" Should check if player has Less Than 20 hunger points before starting eating automatically.
Currently, it is not being checked. If you bring player to low health, but maintain full hunger bar, AutoEat will try to eat, even though it is not possible to eat anything. This puts player into false "eating" state.
This is not a major problem, until you check "Pause Baritone" or "Pause Auras". Then this false "eating" state will prevent baritone and kill aura from functioning, until the fake "eating" state ends. And that is not so simple
You could have thought AutoEat would exit the "eating" state when the hunger bar goes down even by just 0.5 points, which would make AutoEat actually start eating, but that doesn't happen. Because the "eating" state already started, AutoEat won't start it again until forcefully qiuting this state. And currently this can only be done by turning on and off AutoEat Module, or reconnecting with the server
To fix this you should just check if the player hunger is <= 19.5 before starting to eat.
Steps to reproduce
Now you have entered the false eating state and you should be unable to use either baritone or kill aura until you reset AutoEat or disconnect.
Meteor Version
Meteor 1.21.4-42
Minecraft Version
MC 1.21.4
Operating System
Windows
Before submitting a bug report
This bug wasn't already reported (I have searched bug reports on GitHub).
This is a valid bug (I am able to reproduce this on the latest dev build).