[MC-72774] Entities render incorrectly on the first frame after being summoned

The bug

Entities will sometimes render incorrectly on their first frame, probably due to entities not having NBT data until the first tick (or simply not rendering it).
This has been observed both with common commands

/summon minecraft:zombie ~ ~ ~ {active_effects:[{duration:-1,amplifier:0b,id:"minecraft:invisibility"}]}

and spawn eggs

/give @s minecraft:squid_spawn_egg{EntityTag:{id:"minecraft:squid",CustomName:"{\"text\":\"column\"}",CustomNameVisible:0b,NoAI:1b,Silent:1b,active_effects:[{duration:-1,amplifier:0b,id:"minecraft:invisibility"}]}} 1

Both status effects (specifically, invisibility), and rotation are affected by this problem.

I believe this causes the commonly seen bug of TNT and fireworks rendering for 1 tick even when they are supposed to explode immediately.

Linked issues

is duplicated by 3

MC-82204 Mobs Aren't Instantly Invisible With The ActiveEffects Tag! Resolved

MC-276637 render issue when summoning an invisible entity Resolved

MC-277250 Summoned invisible mobs are visible for a few frames upon summoning Resolved

relates to 5

MC-245781 Fish summoned on water render on their side for a single tick Open

MC-262213 Baby sniffer's head is smaller on the first frame of existing Resolved

MC-89141 Shulker spawn instant position is crooked (not aligned to block grid) Resolved

MC-196472 Spawning a Strider outside of #strider_warm_blocks causes them to flash red for a game tick Resolved

MC-272577 Summoning any entity with rotation causes it to be rotated incorrectly Resolved

Attachments

MC-72774.mp4

Comments 23

Dlawso the Really Lucky Rabbit 2014-10-07T00:28:16Z

Command used?

Jasper van den Berg 2014-10-07T13:25:41Z

/summon Zombie ~ ~ ~ {ActiveEffects:[{Id:14,Amplifier:1,Duration:999999}]}

marcono1234 2014-10-17T16:48:12Z

Confirmed for:

1.8.1-pre2 Just build a clock summoning invisible mobs and you will see some of them appearing

kasamikona 2015-02-01T17:51:06Z

Confirmed for 1.8.2-pre6, although the bug is actually kinda different. Entities will gain their effects instantly, but always get rendered in their default state on the first frame/tick regardless of any NBT tags present (potion effects, marker tag on armor stands, even just the entity's rotation).

KingSupernova 2015-02-02T03:17:02Z

You seem to be correct about the rotation, but this doesn't happen to me with the "Invisible" tag.

13 more comments

marcono1234 2015-04-10T14:50:37Z

For me it still happens sometimes in 1.8.3 it seems to depend on how much lag there is currently

kumasasa 2015-09-07T06:15:56Z

Forward resolved to MC-88181 - there is described the cause of this behaviour

KingSupernova 2015-09-07T06:39:49Z

That doesn't actually describe the cause. It just has "I don't think entities have any NBT in their first tick of existence." That could be the problem, but there are other options. It would be nice if more information were given about that thought. That ticket also doesn't mention rotation values.

Nasm Nasmus 2015-09-07T10:19:43Z

I agree that this is the better bug report, there's more information here, and finding the issue is easier using this(only a summon command with just one effect).

kumasasa 2015-09-07T20:57:21Z

Ok, reopened.

marcono1234 2015-12-14T16:17:00Z

We could seperate MC-88181 and this report a little more by saying that MC-88181 is not caused by a missing onUpdate() call for the entity.
For example the problem that you see PrimedTnt for 1 frame is that the S0EPacketSpawnObject (MCP 1.8 names) contains only basic information about position, rotation, the entityId (acts as entity index), the entity type id and one additional integer. After that other packets are send containing the other needed information. However while the second packet has not arrived the entity has not all information. For example PrimedTnt. This applies for example also for armor of mobs.
Additionally for PrimedTnt the S1CPacketEntityMetadata packet which is send after the spawn packet does not contain the correct fuse value. This seems to be caused by the DataWatcher not watching the fuse value.