Connect custom DayZ JSON to cfgGameplay safely

Use double-quoted keys and strings, balanced braces and brackets, and no trailing comma after the final item. Normal JSON does not allow explanatory comments inside the data. Validate the final text before uploading it.

An ObjectSpawner file, restricted player area, effect area and underground trigger file have different structures. A filename alone does not identify its schema. Mod JSON also requires the exact installed mod version and its documentation; it must not be guessed from a vanilla example.

Custom object files are commonly stored under the mission's custom folder and referenced with an exact relative path. Keep the filename and extension identical in cfgGameplay.json, including letter case where the server filesystem treats it as significant.

ObjectSpawner files belong in WorldsData objectSpawnersArr. Other supported world systems use their own arrays or settings, such as player restricted area files. Preserve every unrelated WorldsData, PlayerData, GeneralData and MapData setting already present in the live file.

Object positions, restricted-area boxes, safe positions and effect locations must be checked against the selected map. For three-dimensional data, height is important as well as X and Z. Copying coordinates between maps can place objects outside the playable world or below terrain.

Validate the custom JSON, cfgGameplay.json and the exact referenced path together. A safe package tells the owner which files to upload and where, preserves the complete current cfgGameplay file, and confirms results from server logs after restart.