Compound block names in blacklist for "do not destroy" blocks is ignored

[ZaCloud]

Yo, I'm using this on Minecraft 1.20.1 (Forge). It's great, but there's a problem with designating "do not destroy" blocks when the zombies dig:

Even though it seems like you tried to have wildcards in the config file by default (like "end_" to mean anything made out of End Stone, or "_sign" to include all types of signs, etc), those exceptions are IGNORED, and the zombies dig through things that you clearly wanted them to leave alone.

Plus, this also happens with many blocks that we players add onto the list. In experimenting, I found that every block name with two words (in MC divided by an underscore, such as "iron_block"), both when added directly in-full or using your attempt at shorthand (like "_bricks" intended to protect "bricks", "stone_bricks", "deepslate_bricks", etc), is also ignored when added to the config (And needless to say, the "Any part of a block name" note is invalid too).

So, neither wildcard underscores nor complete compound block names work in this current syntax. Only single-word blocks.

Could they need quote marks around them? Or some other reference method to call upon block names where it can successfully designate compound block names?

We just plain can't make (and keep repairing) a safe-ish base that's also blast resistant (other than HORRIBLY tedious Clay making/digging/smelting-with-coal-in-low-supply/crafting-into-Bricks and Obsidian farming) if the creatures keep ignoring the blocks we want to be safe, and are losing vital components too. 🥺

-

(( EDITED 6/13/2024 - Changed a built-in syntax example to actually be one that's built-in ("_sign"); I think I custom-added the "_bricks" attempt myself, so I moved it to the 3rd paragraph instead. And I noted how this issue means that the instruction accompanying the blacklist is currently invalid. And removed some whining. 😅))

[Habetus]

yo the zombie can broke the bedrock