This is essentially just MC-125252 except that it only affects phantoms attacking players at high elevations. I'm not sure what constitutes "high" elevations, but the behaviour is consistently bugged at about y=96, y=187 and y=256. It works fine for me at y=32 and below.
To be clear, the issue is that after phantoms swoop at the player, they are supposed to fly back up and gain some altitude before swooping at the player again. Instead, they just nosedive into the ground and hang around there doing a faceplant for awhile before eventually flying back up.
If you use "data get entity" to check the value of their AY tag (The y coordinate they are trying to hang around), you'll notice that it is above the player initially, goes up (For some reason?) when they decide to attack the player, and goes down again after they swoop. In the case of high elevations, it goes too far down, as in far down below the ground too far, which is what's making them faceplant into the ground constantly, because they're trying to fly through it.
Comments 9
Please attach the crash report ([minecraft|http://hopper.minecraft.net/help/finding-minecraft-data-folder]/crash-reports/crash-<DATE>-client.txt), otherwise we can not diagnose this issue.
For technical support please use the Mojang Support Center.
-- I am a bot. This action was performed automagically!
Also, if anyone else is having this issue, you can workaround it with a data pack by checking for any phantom's AY tag being significantly below its own position. If it is, just set its AY tag to be some place a bit above the player's position.
Make sure not to do this modification on the same tick that the phantom is summoned however, or you will prevent it setting its default circling location and cause it to fly to 0,0.
I think the "future version" thing you mention is a bug in the the bug reporter ...
As for the phantom bug, I also see this, including phantoms trying to fly down through the roof of buildings and player created platforms.
Sometimes they come unstuck if I approach them closely.
Please do not mark unreleased versions as affected.
You don't have access to them yet.