On 1.30 (server build 1.30.164078, PS4 community server, Chernarus), "disableBaseDamage": true in cfggameplay.json no longer keeps base-building objects invulnerable. The file is valid and loads without errors. The cause looks like a line added in 1.30 to the BaseBuildingBase constructor (scripts/4_World/Entities/ItemBase/BaseBuildingBase.c). Right after ProcessInvulnerabilityCheck(GetInvulnerabilityTypeString()) there is now SetAllowDamage(true);, which immediately cancels the SetAllowDamage(false) that the check just applied. In 1.29 the constructor ended with the invulnerability check alone. The persistence load path (OnStoreLoad, AfterStoreLoad and SetPartsFromSyncData) never re-applies the check. Every fence, watchtower, flag pole and shelter loaded from storage is therefore damageable after each restart. The check only runs again in Construction.BuildPartServerEx and PluginRepairing, so a part regains protection only when it is built or repaired, and only until the next restart. Containers, tents and barrels (disableContainerDamage) are unaffected; their constructors did not change. Console servers cannot run script mods, so there is no server-side workaround, and the setting is effectively broken for every console community server that relies on it.

1. Set "disableBaseDamage": true in cfggameplay.json and make sure the server loads the file.

2. Build a fence with a wall and confirm it can't be damaged (melee or a grenade).

3. Restart the server.

4. Damage the same wall with melee, firearms or a grenade.

Expected result : With "disableBaseDamage": true in cfggameplay.json, fences, watchtowers, flag poles and shelters stay invulnerable at all times, including after a server restart, as they did in 1.29. Melee, firearms and explosives should do no damage to them.

Actual Result : After any server restart, every base-building object loaded from storage takes damage from melee, firearms and explosives and can be destroyed, even though disableBaseDamage is true. A part only becomes invulnerable again when it is built or repaired, and loses that again at the next restart. disableContainerDamage (tents, barrels, containers) still works correctly.