When a temporary Animator component is created to animate material properties, specifically when using a MaterialPropertyBlock, and subsequently destroyed, the animated material properties may unexpectedly revert to their default values. This behavior occurs even if the MaterialPropertyBlock is updated after the Animator is destroyed. In contrast, material color changes made directly via Material.color or Material.SetColor("_Color", ...) persist after the Animator is destroyed, though these methods force the creation of material instances. The issue specifically arises when a MaterialPropertyBlock is used to modify properties, leading to an unwanted reset of values (e.g., color reverting to white) instead of maintaining the last set or animated state. This necessitates storing and reapplying base colors, adding complexity to workflows that require immediate Animator destruction and subsequent material property updates.