BC-0216 · TROUBLESHOOTING
Editorial review 2026-09-26
Prompt Created Duplicate Objects
For duplicated scene objects, identify whether the extra appearance is an intended repeated object, a restored object from another attempt or an unwanted additional instance. Decide what must remain and which relationships depend on it before removing anything. Matching visuals alone do not establish shared identity.
Symptom
Additional or overlapping objects appear after a revision and may alter the intended scene or objective.
Immediate action
Distinguish their roles and state before choosing any removal.
Diagnostic branches
- Repeated objects are intentional scenery with no observed interference.
- Treat removal as an aesthetic choice rather than a proven functional fix.
- An additional active object changes qualification or passage.
- Name the intended survivor and preserve its required relationships.
- The appearance is the legitimate fresh-attempt restoration.
- Keep the reset behavior instead of deleting the restored object.
- Roles cannot be distinguished without risky actions.
- Keep deletion unresolved and use existing evidence only.
Least-destructive change
Remove only a confirmed unwanted role while retaining the objective's usable dependencies.
Retest
- The intended object and destination remain usable.
- The unwanted simultaneous copy is absent in the relevant state.
- Legitimate repeated scenery and fresh-attempt restoration remain intact.
Escalation
Use role, location and state evidence for a scoped inspection. This does not reveal hidden object identity, establish safe bulk deletion or guarantee exact selection.
Working notes
Use observable role and location to distinguish the suspected copies. A pair of decorative lamps may be intentional; an additional objective parcel may alter completion; overlapping gates may affect passage. The practical problem is the extra object's effect on the scene, not duplication as an abstract visual category.
Check whether the extra appearance follows a known state transition using existing safe observations. A collectible returning on the designed retry may be correct. If an extra appears while the original is still available in the same attempt, record that difference without inferring a hidden spawner or object identifier.
Choose the surviving object and its dependencies explicitly. Preserve the route marker, qualifying interaction and any intended destination relationship that belongs to it. Removing all objects with the same color or name could make the objective impossible or erase intentional repeated decoration.
Retest the affected scene state and the legitimate transition that produced the observation. Do not repeatedly collect unintended extra rewards or destroy valuable work to verify a cleanup. If a safe observation cannot distinguish the roles, leave the deletion decision unresolved and carry the evidence into an inspectable editing workflow.
Examples
- Functional extra: an additional delivery parcel appears beside the original before collection, but the intended objective requires the authored parcel-to-desk relationship. Preserve the intended parcel and destination; do not delete every parcel-like object without checking that relationship.
- Legitimate repetition: the same-looking collectible is restored at the start of a new attempt. That is different from multiple available copies in the same state and should not be removed solely because its appearance repeats.