I just had this happen in 1.6.4. I left a horse in the Nether, and when I returned, it was glitched partway into the wall it had been standing next to and was taking damage.
This is definitely NOT the same bug as MC-14826. I've had both. The invisible-but-still-attached one has popped up a couple of times, but I get this one all the time. The leads are lying on the ground and the horses are wandering far, far away from their hitching posts. This is quite a bit different than having a horse appear to be free, but be unable to ride it more than 10 blocks away from the hitching post. Trust me, when you've had both you can tell the difference.
For those looking for the actual lead breaking bug, here is another report, which has (miraculously) not been closed yet: https://mojang.atlassian.net/browse/MC-19925 Maybe they're starting to believe that this bug exists, too?
Definitely chunk loading related. I have always had it occur when reentering the area where my pasture and stables are located. I pretty much always do so using a Nether portal; I'm afraid I can't remember if it's ever happened when I just walked there. The interesting part, though, comes from my stable area having been built on the intersection of four chunks. Whenever this bug happens, it does so within one chunk and (usually) leaves the other three alone. You can see where the edges of the involved chunk are by where the horses are free and wandering and where they're still tied up. I have dozens of horses tied to regularly spaced hitching posts, so the line of demarcation is quite obvious. I haven't noticed any particular pattern regarding which chunk it shows up in. It's happened in every one at least a couple times.
@Torabi: No, this is a different bug. Maybe they're both related to the same section of coding, but the symptoms are completely different. I say that as someone who has had both bugs multiple times. Actually, I've had both happening in different areas of my stable complex at once. I'm just lucky that way.
@Torabi: Sorry, I know you're just trying to help. I'm just frustrated because they keep closing these reports claiming that they are duplicates of that bug. Like they just did this with this one.
I just had this happen in 1.6.4. I left a horse in the Nether, and when I returned, it was glitched partway into the wall it had been standing next to and was taking damage.
This is definitely NOT the same bug as
MC-14826. I've had both. The invisible-but-still-attached one has popped up a couple of times, but I get this one all the time. The leads are lying on the ground and the horses are wandering far, far away from their hitching posts. This is quite a bit different than having a horse appear to be free, but be unable to ride it more than 10 blocks away from the hitching post. Trust me, when you've had both you can tell the difference.For those looking for the actual lead breaking bug, here is another report, which has (miraculously) not been closed yet: https://mojang.atlassian.net/browse/MC-19925 Maybe they're starting to believe that this bug exists, too?
Edit: Nevermind, they closed that one, too.
Definitely chunk loading related. I have always had it occur when reentering the area where my pasture and stables are located. I pretty much always do so using a Nether portal; I'm afraid I can't remember if it's ever happened when I just walked there. The interesting part, though, comes from my stable area having been built on the intersection of four chunks. Whenever this bug happens, it does so within one chunk and (usually) leaves the other three alone. You can see where the edges of the involved chunk are by where the horses are free and wandering and where they're still tied up. I have dozens of horses tied to regularly spaced hitching posts, so the line of demarcation is quite obvious. I haven't noticed any particular pattern regarding which chunk it shows up in. It's happened in every one at least a couple times.
@Torabi: No, this is a different bug. Maybe they're both related to the same section of coding, but the symptoms are completely different. I say that as someone who has had both bugs multiple times. Actually, I've had both happening in different areas of my stable complex at once. I'm just lucky that way.
@Torabi: Sorry, I know you're just trying to help. I'm just frustrated because they keep closing these reports claiming that they are duplicates of that bug. Like they just did this with this one.