Invalid Content Log Error

Affects latest release 1.14.30

 Partner Rank: 3

Summary

There seems to be an issue with the submission pipeline for games at the moment. Twice now I've submitted custom entities that are just copies of existing entities but then the tester is reporting these Molang errors:

 

[Molang][error]-razzleberries:decorator_trader | Error: accessing a variable that doesn't exist: variable.raise_arms
[Molang][error]-razzleberries:decorator_trader | MolangScriptArg::get<>() called on incompatible type texture.level_stone

 

The entities (such as razzleberries:decorator_trader) don't have any custom textures, models, scripts, animations, animation controllers or render controllers. Instead they just have an entity definition file that copies the minecraft:villager_v2 layout. 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 repro steps but I have attached a copy of the pack causing the error message. A rough repro step is:

• Define a new entity and make its resource pack identifier a copy of minecraft:villager_v2.
• Run the pack in a world through whatever submission process Mojang testing uses.

Note that in the example pack there are four entities that are all copies of villager_v2 but only two of them were reported by the testing team as giving the Molang errors. I have submitted several maps with these exact custom entities just with different identifiers and loot tables and only two have come back with this error.

Observed results

Custom entities sometimes cause molang errors for variables and textures that are pointing at existing vanilla resources,

Expected results

The map passes testing without these errors.

Notes:

Both times this has happened I have replied contesting the issue and it was agreed to ignore it and publish anyway but while this remains an unknown to the testing team and an error in the output log, game submissions are slowed down by the back-and-forth discussion that happens around the error.