mojira.dev
MCPE-42730

Ravager headbutt animation is very slow

Ravager headbutt/bite/ram animation is very slow that sometimes the ravager does not use it's headbutt animation when they are very close to their target.

Attachments

Comments 17

Biting isn't the ravager's only attack, it also butts with its head, for example when it breaks blocks. What makes you think the attack in the video is biting?

The video explains the ravager damaging the villager with the biting animation. Then they attack the villager for the 2nd time without using their biting animation.

Still affects 1.12.0.4 Beta

Still affects 1.12.0.6 Beta

Still affects 1.12.0.9 Beta

7 more comments

Still affects 1.16.200 betas

I cannot reproduce this in 1.16.221 Hotfix on PC or Nintendo Switch. I was confused by earlier comments distinguishing head butting from biting. When I test I only see one attack, which consists of the head extending and then tilting upward while the mouth bites. I tested this over and over and saw all parts of the animation every time.

In the video attached to this report, I can see all three parts of the animation during the first hit on each villager, but only the upward tilt of the head after the second hit on each villager. That can make it look like different kinds of attacks, but really it's not. The head and neck extension and the bite are just being skipped on the second attack. That could be because they are too slow and the damage is done before they can be execute. Or it could be that the damaging of the attack occurs too soon, at the start of the animation rather than after the head and neck extend.

The more I think about it and review the video, the more I think the latter is the case. I suspect that the reason only the head tilt plays on the second attack on each villager is that the attack kills the villager, which causes the ravager to lost its target, which it turn causes the attack behavior to immediately cancel, and the main animation to cancel with it. On that analysis combined with what I see when I test, I think this issue has already been fixed.

On the other hand, this could just be a bug that I don't get. In fact, I couldn't even get a ravager to attack a villager on the other side of a wall as shown in the video. It would nice to get an updated video on this ticket.

This issue affect 1.20.40

@unknown: It has been nearly 3 years since anyone has commented on this report. The staff here was never able to reproduce it (with the possible exception of the reporter, who hasn't been active here for a long time). I have just tested it in 1.20.40 and can reproduce what I see in the attached video, but I don't understand what is being called "very slow" animation.

The only thing I see in the video that might be described as "very slow" is the ravager's rate of attack. There is a delay of about 2 seconds between attacks. That seems quite reasonable to me, given how powerful its attack is; if it attacked more quickly, there would be almost no chance of its victim escaping, and if the victim is a player that means the player would have no tactic to escape death. Mojang adheres to a design policy that doesn't allow the game to trap players in such situations. So if the attack were made quicker it couldn't be much quicker, and therefore calling it "very slow" is unreasonable. For this reason, I don't think that the rate of attack is what was the description was calling slow. But that leaves us with no alternative way to interpret it, which is why this report has stalled.

Since you now seem to be the only person still interested in resolving the reported issue, we need your help to understand what the problem is. Does the attached video demonstrate what you believe the issue is? If so, what exactly happens slower than you think it should? If not, can you attach a better video, or failing that describe the problem in more detail? Specifically, what is happening slowly, and what makes you believe it should be happening faster? (Note that if it's just your personal feeling about how it should be, that's a feature request, not a bug.)

Cleaning up old tickets. There has been no response from the author and no activity on this report for over 10 months, so it's being closed as Cannot Reproduce.

DrownedZombie

(Unassigned)

383744

Community Consensus

Android

1.13.0.1 Beta, 1.16.200.56 Beta, 1.16.0.66 Beta, 1.16.0.64 Beta, 1.15.0.51 Beta, ..., 1.12.1, 1.12.0, 1.14.30 Hotfix, 1.14.60 Hotfix, 1.16.100

Retrieved