"RuleSets": [
{
"name": "default",
"enabled": true,
"defaultAllowDamage": false,
"flags": "AuthorizedDamage, HumanNPCDamage, NoHeliDamage, NoHeliDamageQuarry, LockedBoxesImmortal, LockedDoorsImmortal, AdminsHurtSleepers, CupboardOwnership, SelfDamage, TwigDamage",
"rules": [
"players cannot hurt deployables",
"explosives cannot hurt deployables"
]
},

{
"name": "deployables",
"members": "mining.pumpjack, mining.quarry, mining_quarry, miningquarry_static, pumpjack-static, small_refinery_static, furnace_static, refinery_small_deployed, planter.large.deployed, planter.small.deployed, furnace.large, furnace, generator.wind.scrap, electric.windmill.small, water_catcher_large, water_catcher_small, waterpurifier.deployed, waterstorage, waterbarrel, watchtower.wood, composter, water.catcher.small, water.catcher.large, water.barrel, large.furnace, vendingmachine.deployed",
"exclusions": ""
},
{
"name": "explosives",
"members": "explosive.satchel, explosive.timed, ammo.rocket.smoke, ammo.rocket.basic, ammo.rocket.hv, ammo.rocket.smoke, ammo.rocket.fire, ammo.rifle.incendiary, ammo.rifle.explosive, grenade.f1, grenade.beancan, ammo.grenadelauncher.he, ammo.shotgun.fire, arrow.fire, surveycharge",
"exclusions": ""
}

Read the documentation to understand the AuthorizedDamage and CupboardOwnership flags

The documentation explains that these flags determine if the damage is allowed or blocked, which is why your rules are not being evaluated. This is by design, and has its obvious pros and cons. You can solve this by adding the AuthorizedDamageRequiresOwnership flag when 2.0.4 is released.

Also,

You have defaultAllowDamage set to false (and it should be) so all damage will be blocked by default anyway. You only need to add rules that allow damage. If you ever require a large amount of members in an entity group then you are likely going about it the wrong way.

Because of this, your current rules and entity groups are redundant and should be deleted. 

There are 2 exceptions to this:

1) As already stated, certain flags, such as those mentioned above, will not evaluate rules

2) When a rule contradicts another rule. In the case of the rule anything can hurt players it is necessary to include the rule players cannot hurt players if you do not want the first rule to include players.

The default configuration file has been completely rewritten to serve as a proper example of how to setup the plugin in the most optimal way. While it does contain a couple redundancies, they serve as helper examples for new users trying to get a grasp on the plugin. All of this was done because the vast majority of configurations available in this forum are extremely bloated. This all stems from improper use of the defaultAllowDamage setting.

yes, it is available in 2.0.3 but currently blocks damage to the bradley. 2.0.4 fixes this issue

np