[MC-145140] Fireballs cannot be interacted with when summoned

Entities are randomly non-interactive or turn invisible.

Steps to reproduce:

1) Start a new creative world.

2) Run /summon minecraft:fireball ~ ~ ~ {direction:[0.0,0.0,0.0]} to create a static fireball

3) Punch or observe the fireball. If it is non-interactive or blinking in and out of existence the bug is occurring.

If the fireball appears normal and can be punched repeat steps 1 through 3 some worlds/biomes seem to always have this issue where some it is more intermittent.

When the bug is occurring you cannot punch the fireball at all. You can however, place a block on the fireballs location and it will explode showing that the entities exist but cannot be interacted with by the player.

Linked issues

is duplicated by 15

MC-145754 Fireballs become invisible and non-interactive Resolved

MC-149593 Fireballs not punch-able far from spawn chunks Resolved

MC-150678 Unpunchable fireball Resolved

MC-151058 Summoned fireballs disappear and reappear. Resolved

MC-152501 Fireballs Flicker In and out of existance Resolved

10 more links

relates to 1

MC-140959 small_fireball entity ID is broken Resolved

Attachments

MC-145140.wmv

Comments 16

[Mod] Neko 2019-02-28T21:05:55Z

Is this an issue with fireballs or all entities?

joe bing 2019-03-01T09:49:47Z

May be limited to entities with the direction tag - fireball, small_fireball, dragon_fireball. This is the only way I can reproduce somewhat reliably.

Romain 2019-03-28T06:23:44Z

Same issue in 19w11b in all biomes.

fireball are only moving when immediately punched after summoned and sometime blink. (see video)

small_fireball and dragon_fireball turn immediately invisible after summoned.

Arrows are not affected by this. Arrows still move after summoned. I guess arrows are not affected by this issue.

Romain 2019-04-10T18:55:12Z

Still in 1.14 Pre-release 1

Sal 2019-04-12T13:25:49Z

1.14 Pre-release 2, its still happening.

I've done some testing myself. As Romain stated you can punch the fireballs immediately after summoning, but you can also leave the render distance of the Fireball and return. This also allows you to punch the fireball as normal, so there is something happening shortly after the initial rendering that makes it bug toward the player.

Additionally you can hit the fireballs with projectiles like arrows or snowballs with no issues after the initial summon.

6 more comments

Eat Your Hashs 2019-11-06T01:33:37Z

Can confirm this also applies to wither skulls.

Logical_Cyclops 2019-12-05T13:59:18Z

I'm guessing this'll probably get fixed in a bug fix update of 1.15; ever since 1.13+ fireballs have been a pain in the ass to work with. The good ol' /execute summon to create a fireball mechanic doesn't work anymore, and now not even summoned fireballs can be hit ;(.

Logical_Cyclops 2019-12-13T13:27:04Z

Affects 1.15.1 pre-release.

Lars 2020-02-08T17:59:24Z

Still in 1.15.2

In 20w06a however the fireball is only invisible for the first seconds and then works correctly

Workaround for 1.15.2

Summon fireball with initial "power" as mentioned earlier:

summon minecraft:fireball ~ ~ ~ {"direction":[0.0,0.0,0.0],"power":[0.0,-0.0002,0.0],"Tags":["wd_fireball0"]}

Setting the "power" back to 0 immediately:

execute as @e[type=minecraft:fireball,tag=wd_fireball0] run data merge entity @s {"power":[0.0,0.0,0.0],"Tags":[]}

The second command can be executed every tick.

This preserves the ability to interact with the fireball even so the power is 0 and the fireball is motionless.

FaRo1 2020-02-09T13:31:44Z

No, it's still the same for me in 20w06a as in 1.15.2: The fireball is occasionally visible flickering, from certain view angles, but otherwise nothing works.