@DrownedZombie You sure? Seems like too much of a coincidence that your name is DrownedZombie.
Also, why does the end portal even have an inventory texture? Under the Expected Results section, it states that — No end portal block/items should be obtainable.
Wait... If they are new sounds, then why is the affects versions section set to 1.9.0.0? And why is it fixed, not resolved as WAI?
That's very weird. It still affects 1.11 when it should've been fixed in 1.9.
Разве это не обычная анимация смерти сущностей?
Translation for people other than David:
Isn't that just the normal death animation of entities?
Almost every Minecraft Bedrock Edition Beta Release has this under its Fixes and Crashes/Performance section in its changelog:
Fixed several crashes that could occur during gameplay.
Yep, but I was in 1.9 when trying to pick block an end gateway block. So...
Ok, so it is fixed in 1.11.0.3, so why is it still open?
You just moved out of the particle render distance.
The items definitely just despawned.
Wow, really? Open up settings in your world and go to "video". Bam. There's your "Particle Render Distance" option.
Um, I was asking for a "Duplicate" resolution, not a "Cannot Reproduce" resolution.
But now they do. According to the Official Minecraft Wiki page on Bedrock Edition beta 1.10.0.4 under "Fixes":
Custom entities can now be used with the
[type=]
command argument.
Wait, Jay, did you realize that it was a graphics issue in general before tryashtar commented? Or did you think it was about the associated block entity or the command block itself all along?
Yes me too. I thought it was an issue with the block entity associated with it or something, but guess what? Nope.
Oh, thanks tryashtar!
Jay, yes it is correct on the outside, and Jonathan, this is not a separate issue, it is just that the arrow always has an indent inside of the command block.
Hey Jay, can you resolve this please? Resolution: Duplicate.
Sorry for the trouble, but I realized that this is not when scaffolding falls on fire, but simply a laggy CPU that caused the glitch.
Confirmed for 1.15 snapshots