pWhen a door of a rebuilt house (tested on Land_House_1M5, metal door) is destroyed or dismantled while a combination lock is locked on it, the lock drops to the ground still in the locked state. The dials on its outer and inner sides then show different numbers, and neither matches the code that was set. When this lock is attached to a door again, the game takes the new code from the OUTER dials only. Players who read the inner side or remember the old code can no longer remove the lock, so it looks like the lock is broken.

Notes
Reproduced twice in a row on a local vanilla 1.30 server. Possibly related to DZG-1269, DZG-1290 and DZG-1305.

Cause (1.30 scripts): ConstructionBase.DropEssentialAttachments (dismantle/destroy of a door part) drops the lock without calling CombinationLock.UnlockOnServer, which is what syncs both dial sides. Fence.HandleDropAttachment does call it, so fence gates are not affected. CombinationLock.LockServer then takes the new code from the outside dials only. Suggested fix: call UnlockOnServer for CombinationLock / DigitalCodeLock in DropEssentialAttachments, like Fence does.

1. Rebuild a door on a restorable house (Nasdara), close it.

2. Attach a 3-dial combination lock, set code 358 and lock it.

3. Destroy or dismantle the door.

4. Look at the dropped lock: outer dials show 496, inner dials show 439 (real code is still 358).

5. Rebuild the door and attach the same lock.

6. Try to remove the lock with 358 or 439: it does not open. Code 496 (the outer dials) opens it.

The lock keeps its code, or is unlocked with both sides aligned when it drops, and reattaching does not silently set a new code.