[MCM-1029] Invalid Content Log Error

Affects latest release 1.14.6

Partner Rank: 3

Summary

There seems to be an issue with the world log for games at the moment as mentioned before : https://bugs.mojang.com/browse/MCM-955

In this case a MoLang error has presented itself without a resource or behaviour pack existing in the world.

[Molang][error]-minecraft:zombie | Error: accessing a variable that doesn't exist: variable.is_paperdoll

[Molang][error]-minecraft:zombie | Error: accessing a variable that doesn't exist: variable.map_face_icon

[Molang][error]-minecraft:zombie | Error: accessing a variable that doesn't exist: variable.is_first_person

[Molang][error]-minecraft:zombie | Error: accessing a variable that doesn't exist: variable.item_use_normalized

[Animation][error]-minecraft:zombie | error: animation 23 of state third_person of root encountered an error

[Molang][error]-minecraft:zombie | Error: accessing a variable that doesn't exist: variable.last_blink_time

The zombie entities referenced don't have any custom textures, models, scripts, animations, animation controllers or render controllers. In fact the world has no resource or behavior pack included. There is no custom molang so there should be no errors. The entities appear to look, animate and behave as expected in-game.

Impact

Release/Submission pipleline

Repro Steps

I don't have access to the Minecraft builds that log errors so I cannot provide exact repro steps. A rough repro step is:

Download a copy of "Tales from Emythia: Dragonrock 1.0.1" by Razzleberries from Auger (submitted May 5th).
Open the world through whatever submission process and build Mojang testers use. (These errors do not appear in my public copy of Minecraft Bedrock).
Observe content log errors by enabling the content log UI and viewing the content log. I assume as this is a survival spawn that the error happens immediately on loading the world. Sara Lempiäinen may be able to clarify.

Observed results

MoLang errors for missing variables are logged despite only vanilla entities existing.

Expected results

The map passes testing without these errors.

Notes:

The issue of content log errors blocking content has been going on for over a month now across multiple map submissions. When queried, CR agree that the warnings can be ignored and the map is passed on to QA but this back-and-forth slows down map submissions by adding a report and response delay that doesn't need to be there.