[MCM-1712] Using new queries returns unnecessary content log errors

Partner Rank: 3

Partner Team Reporting: XP Games

Verification Build: 1.20.31

Summary

Using new queries returns unnecessary content log errors

Impact

We're utilizing the new queries introduced a few updates ago, namely `q.is_item_name_any` and `q.property`, to effectively carry and check for server-side data to the client-side `player.entity.json` file. The queries themselves works flawlessly as intended and allowed us to have more control and room for technical capabilities, instead of limiting ourselves to "dummy" components. However, when loading up the pause menu, and more importantly, the dressing room, the game throws content log errors regarding the use of these queries.

We use these queries quite frequently in our map and add-on development, and whenever we open the dressing room, it causes a lag as the amount of player renderers in the UI is quite a lot, as each renderer will try to log these errors.

While we do have a workaround of detecting if the player model is being called in the context of UI, it's very finnicky in that we have to do the checks for every query we call. Thus, can overall impact our productivity and progress, and can overall become very confusing to navigate the changes made.

My team manager said that we could not disable the dressing room entirely, due to an apparent guideline imposed. Hopefully, we can get this issue resolved. Thank you very much!

Repro Steps:

Download, import and open the world attached to this report
Open the pause menu and dressing room
Observe content log errors

Observed Results

There should be no content log errors.

Expected Results

Returns content log errors:

[Molang][error]-minecraft:player.0.CustomSlim081f7545-f183-376a-b3a1-2d2d15dcc0d0fce20ac3-e80b-4c00-8230-d815c8a0665c | Error: query.property does not have an actor.
[Molang][error]-minecraft:player.0.8f242985-689c-4c6c-a82d-85d19959c4ff.acozyanimalsraccoonn | Error: query.property does not have an actor.
[Molang][error]-minecraft:player.0.persona-8d865704005f4b82-1 | Error: query.property does not have an actor.
[Molang][error]-minecraft:player.0.persona-8d865704005f4b82-4 | Error: query.property does not have an actor.
[Molang][error]-minecraft:player.0.10b13776-e41b-4af4-9231-00d7e29df987.TemplateSkin1 | Error: query.property does not have an actor.

Notes: Our workaround involves by utilizing `q.has_property`, `q.is_in_ui`, and `v.is_paperdoll`. But sometimes we can't fully rely on these queries. The use is simply very inconsistent and unnecessary for its intended purpose.