Change DayZ cfggameplay.json Settings from Discord

Updated 15 October 2026

Much of how a DayZ server plays is set in cfggameplay.json: whether bases can be raided, how stamina works, how dark nights are. On a console server you normally edit it through Nitrado's file browser. Law's KillFeed puts the common settings on one panel in Discord and uploads the file for you.

The panel

• Raiding: base and container damage on or off together, for raid days.
• Base damage and Container damage: one at a time.
• Infinite stamina: on or off.
• Build anywhere: turns the building placement checks off (and back on). It does not let players walk through walls.
• Bright nights: on for brighter nights, off for dark nights.
• Hit marker and the colour menu: show hitmarkers and pick their colour.
• Custom object spawner: add, remove or list object spawner files.

Run /serversettings. The panel shows what your server has now, and each button flips one setting. Green means on. After every change the bot reads the file back, so what you see is what the server has. With several servers, pick one at the top.

What each setting changes in cfggameplay.json

• Base damage: GeneralData.disableBaseDamage. Off stops damage to walls, gates and other base parts.
• Container damage: GeneralData.disableContainerDamage. Off stops damage to tents, barrels and other storage.
• Raiding: both of the above at once.
• Infinite stamina: in PlayerData.StaminaData, sets sprintStaminaModifierErc, sprintStaminaModifierCro, staminaKgToStaminaPercentPenalty and staminaMinCap to 0.01. Turning it off puts back the defaults: 1.0, 1.0, 1.75 and 5.0.
• Hit marker: UIData.HitIndicationData.hitDirectionOverrideEnabled and hitDirectionBehaviour.
• Hit marker colour: hitDirectionIndicatorColorStr, with hitDirectionStyle set to 2 (the arrow style) for a custom colour, or both back to the default.
• Bright nights: WorldsData.lightingConfig. 0 gives brighter nights, 1 dark nights.
• Build anywhere: the placement checks in BaseBuildingData.HologramData (disableIsCollidingBBoxCheck, disableIsCollidingPlayerCheck, disableIsClippingRoofCheck, disableIsBaseViableCheck, disableIsCollidingGPlotCheck, disableIsCollidingAngleCheck, disableIsPlacementPermittedCheck, disableHeightPlacementCheck, disableIsUnderwaterCheck, disableIsInTerrainCheck) and in BaseBuildingData.ConstructionData (disablePerformRoofCheck, disableIsCollidingCheck, disableDistanceCheck), all on or all off.
• Custom object spawner: the list of object spawner files in WorldsData.objectSpawnersArr.

The panel edits the same keys you would change by hand, so you can check the file afterwards and see exactly what was set. For every other setting, the free cfggameplay.json Editor shows them all as switches and boxes.

When changes apply

DayZ reads cfggameplay.json when the server starts, so a change takes effect at the next restart. Restart straight away with /server restart, or let your scheduled restart pick it up.

The file has to be switched on in your Nitrado settings for these settings to work. Base and container damage are the exception: when the file is off, the bot changes Nitrado's own setting instead.

Who can use them, and limits

The panel is for owners by default. Give staff some or all of it through a permission group linked to a Discord role: each setting keeps its own permission (raid, basedamage, containerdamage, infinitestamina, noclipping, nightlight, hitmarker, hitmarkercolor, customobjectspawner), and buttons someone can't use are greyed out. The free plan allows 10 changes per server per day; the paid plan has no limit.

Editing the file works on Xbox and PlayStation servers only.