Xbox community server hosted by Nitrado, Nasdara / dayzOffline.nasdara. Last verified server build: 1.30.164200. No Workshop/script mods; customization uses mission JSON/XML.

Editor-added rebuildable houses lose their own construction-slot materials and completed windows after restart. This concerns the house's rebuilt parts and attached materials, not ground loot or barrels. Several players report it at multiple added houses. Native terrain houses have not been tested for comparison.

Controlled test: the owner rebuilt windows at DAM BASE, then restarted normally through Nitrado. The pre-restart ADM confirms five completed metal windows: window9_metal, window12_metal, window11_metal, window10_metal and window8_metal, followed by disconnect at shutdown. After reconnecting, the owner confirmed the windows disappeared again. Build positions strongly identify a Land_House_3S1 in the custom export; the action log itself leaves the target class blank.

Verified configuration: the active Object Spawner JSON has four Land_House_2S2 and four Land_House_3S1 entries with enableCEPersistency=1 and scale approximately 1. These classes exist in live types.xml with lifetime=3888000 (45 days), nominal=0. economy.xml has dynamic load/save enabled and building init=1/load=1/respawn=0/save=1. cfgignorelist.xml does not exclude them. Construction/placement collision bypasses are already enabled.

Only log_storageinfo was enabled for the diagnostic restart. Placements, lifetimes and falling/clipping settings were unchanged. Earlier RPTs show valid building storage loads, which does not establish that this house was saved. The host has not exposed the post-test RPT yet. Duplicate instances, corruption and the exact failure remain unproven. Lock attachment status is unknown.

Related: https://report.bistudio.com/issues/DZG-1404 . Official Xbox notes dated November 3 list a lock-slot duplication fix in 1.30.164289: https://dayz.com/article/game-update/dayz-badlands-out-now/dayz-xbox-patch-notes . That build is not verified on this server, and the same cause is not established. Please advise whether persistent JSON-spawned rebuildable houses are supported and whether this should be retested against that fix.

Private identifiers, base coordinates, credentials and full raw logs are omitted. A sanitized minimal placement example can be supplied if needed.

1. On Xbox Nasdara, add a rebuildable Land_House_3S1 through the mission JSON Object Spawner and register the file in WorldsData.objectSpawnersArr. Use enableCEPersistency=1, scale=1, an existing types.xml entry with a 45-day lifetime, and enabled building load/save.

2. Attach construction materials using the house's own slots and complete several metal-window fortifications.

3. Restart normally.

4. Reconnect and inspect the same house. In the observed test the windows disappeared; materials in the house's slots have also been reported lost.

This describes the observed customized-server scenario, not a clean-room reproduction. Native-house comparison and post-update retest are pending.

Completed window fortifications and attached construction materials should survive a normal save/restart/load of a persistent editor-added rebuildable house. Please document any additional supported console configuration, or confirm if this Object Spawner use is unsupported.