There are multiple problems inside net.minecraft.world.entity.animal.Rabbit$RaidGardenGoal and related code:
1. Rabbits can't reach the crops and always stop one block short of them.
2. Rabbits eat the crop instantly even while still jumping and being in the air.
3. The goal is immediately aborted (usually after a few ticks - when a target crop block was selected) due to problems inside canContinueToUse and isValidTarget
Further helpful links:
Related: MC-150224
Linked issues
Comments
[Mod] Jingy
litetex
Depends on what you define as "thing"...
By the same AI-Goal? Yes
By the different pieces of code inside the goal? Yes
Dhranios
Each of them will require a separate fix though, and fixing one does not fix the others. Since they are not the same issue on different instances either (example: comma spliced strings), you should probably create separate reports for each problem.
[MOD] Greymagic27
Thank you for your report!
However, this issue is Invalid.
Please put only one bug report in each ticket. It is very difficult to keep track of bugs when they are not in their own tickets.
However, please review the Bug Tracker Guidelines before creating new reports. Be sure to search for an existing issue as it is likely to have already been reported.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
litetex
Okay, why was this closed as invalid now?
The overall bug - which is experienced in the gameplay as "Rabbits usually fail to raid carrot crops" - is caused by having multiple pieces of broken code in the same file/behavior. So this is ONE bug/faulty behavior which is caused by multiple pieces of broken code.
Also MC-150224 is a single bug despite having problems in at least 5 pieces of code...
Each of them will require a separate fix though, and fixing one does not fix the others. Since they are not the same issue on different instances either (example: comma spliced strings), you should probably create separate reports for each problem.
This is correct but to fix the broken behavior you need all fixes at once, otherwise the overall behavior will not be fixed.
Also I have no idea what is meant with "example: comma spliced strings"
bodakugga
Closing this an invalid makes no sense (same gameplay issue, just like MC-150224). Leave this up to Mojang to decide, not random users
Are all three of the problems stated in this report caused by the same thing? (from what I've read, the answer is no)
If not, these would be separate issues that should all be reported independently from one another.