Bredaby
Assigned
No issues.
Reported
Comments
I am also experiencing this with my own experimental addon.
Found it very frustrating at first when the actor property was reverting to its default value, instead of the new value set by set_actor_property. I only noticed it when I was out of range of the entity (when the entity disappears visually by distance - not affected by simulation distance) and returned to see the entity not rendering the same texture value it was set it to using set_actor_property and determined by query.actor_property in the render controller.
This bug has now been fixed in the 1.17 update
To add to this, it also affects all the actor property values if only one is changed. If you reload a world and "save" an entity with multiple actor property values (workaround 1), and change just a single value, all the actor properties will use their default values instead.