Parks must drop an obsolete custom attribute from instanced bench components in a plaza assembly. What is a safe guiding principle?
Select an answer to reveal the explanation.
Short Explanation
You can remove the obsolete tag without rebuilding every bench: choose the right assembly authoring path and avoid disturbing the shared prototype. That precision keeps the edit focused while preserving instancing across the plaza.
Full Explanation
Removing an obsolete custom attribute from instanced plaza benches calls for an authoring target and method that remove the attribute without unintentionally deinstancing benches or rewriting their shared prototype. Aim the edit at the assembly path that owns the obsolete opinion, and use instance-aware techniques when only some benches need to change. This protects data hygiene and instancing performance. Editing anonymous session leftovers while leaving the assembly layer that authors and persists the attribute untouched does not remove the real opinion and can create a confusing, non-durable fix. Deleting the plaza root prim to clear one custom attribute is catastrophically overscoped. Converting all benches to payloads misunderstands payloads: they do not make attributes impossible and this conversion would disrupt a workable instancing setup. Exam caveat: clearing a property is not always equivalent to blocking it with an empty local opinion; know whether sparse clear semantics or an override is needed, and confirm the composed result. Practical check: locate the attribute’s strongest contributing opinion, remove it on the contributing layer that owns it, use instance-aware scope if needed, then recompose. Verify that the attribute is gone only where intended and that other benches remain instanced. If the whole plaza deinstances, restore and narrow the edit.