Perhaps a better explanation or example is needed since this bug has been on-going since many MANY previous updates, so I'll allow some benefit of the doubt. Now, with items that can shoot a projectile, such as a bow, snowball, any given shooting item, if you are trying to react quickly and move your mouse on target and then shoot, depending on the speed, the projectile will undershoot, sometimes not so much but a lot of other times it will undershoot by a large margin. If I had to explain what this feels like, it's as if you have 2 separate crosshairs, the one you can see, and one you can not see. When you move your visible crosshair, the other "invisible crosshair" will follow, but it will be delayed. It will copy every movement at the same speed, but it will only do that after some odd milliseconds, but it will click at the same exact time as your mouse no matter what. It feels like every projectile seems to follow that invisible crosshair instead of the one that it SHOULD be following, which would be the one you can actually see. There is another way you can see this same effect which was personally implemented as a feature in a recent update. The "aim assist" feature shows how bad this delay is, because when you move your mouse to another block, the aim assist outline will move at such a delayed time it's laughable. Mojang, please. People have made numerous complaints about this, me included. From what I hear this bug has not been around forever, and maybe adding raw input will help, but even that won't fix this issue, since it's underlying somewhere else within the coding for projectiles. This issue also effects weapons added from addons, so it is a clear issue with how the projectiles are coded in the first place.