mojira.dev
MC-14097

Bred horses lose all extra health when hit

When You breed horses to give them higher health, i.e. 26 hearts, when they get hit once, there health drops to 12 hearts. You can heal them back up, but they lose tons of health. (Horses take normal damage afterwards) Also, on logout and back in, the horses total health resorts to around 13 hearts (I guess the extra health isn't fully implemented)

Linked issues

Attachments

Comments 10

Not sure if it is the same issue, but when I breed a 26 heart horse the first time it jumps the health drops to 11 hearts.

Confirmed.
It seems that they have less than the 26 displayed hearts. I find strange that they could have so much health given that the best horses I got only had 15 hearts.

Looks like bred horse's healthbar always shows 26 hearts. Try to reload the world to see correct health bar.

The first picture shows the health of a horse that was bred from two spawned horses. The second picture demonstrates the bug in which the health of the horse reverts to a lower number.

Can't reproduce, it's possible Dinnerbone has fixed this for snapshot w21

Looks like the buggy heathbar was fixed (MC-13662)

I got this glitch when i switched minecraft versions from 13w21a to 13w19a.

Playing on latest realms version today, I am still encountering this issue.

 

  1. Bred horses with 12-14 hearts, gave 2 children, both with 13 hearts. 1 took around ~3 hearts of damage, the other took ~1.

  2. Rode each horse, noted that they had 9 and 12 full hearts respectively, with empty black hearts indicating their max of 13.

  3. Tied up both horses by haystacks, and came back after some time when they should be healed. Instead of being healed, their max hearts had been reduced to match their current (reduced) health.

From this I can conclude that the bug is in your healing code. Horses are simply unable to heal damage properly in the current version, and attempting to do so permanently reduces their stats.

This is a report from 2013, please do not zombify ancient reports. Issues can reoccur, but should then be re-reported.

Understood, my apologies. I guess I just missed the '1' in scanning the date field, and read it as 2023, because I thought this was a recent issue. It's actually on the wrong tracker as well, so I'm opening a new issue. Thanks for catching this.

Collin Dammann

(Unassigned)

Community Consensus

horse

Snapshot 13w16a, Snapshot 13w18b, Snapshot 13w18c, Snapshot 13w19a

Snapshot 13w21a

Retrieved