Spawning a warden normally (with /summon warden or just a spawn egg) will cause them act normally, but as soon as you try summoning one with any NBT data, including simply:
/summon warden ~ ~ ~ {}
the warden will immediately perform its dig action and despawn.
I seem to have figured out why this is happening: if you run the following command -
/data get entity @e[type=warden,limit=1,sort=nearest] Brain.memories
on a normal warden, it will display one memory titled "dig_cooldown". However, running this same command on a warden summoned with NBT (you've gotta be fast, it will be actively digging away) will display a memory that's instead titled "sniff_cooldown". This memory appears to control when the warden can sniff, and some code relating to it may have been changed when the Sniffer was added (because the sniffer has a memory of exactly the same name that does something different).
Linked issues
Comments 4
Okay first off I did search, I do every time, and that didn't come up. So, sorry about that. But if I had found it, I'd have left a comment. They marked it as "won't fix" and never talked about the memories bug that I pointed out. I believe there's a pretty simple way to fix this as I said in the post, and if that doesn't work, they should at least address why.
I literally searched "warden summon dig" and it was the first result.
The sniffler has nothing to do with it, it's the defaulting of NBT. Providing no NBT summons an entity with the entity's default NBT, providing NBT summons it with the base field's default value.
It is WF because they do not want to put effort in fixing it, and spend it elsewhere where they believe matters more,and that's no surprise since you can just add the memory to your summon command.
Duplicate of MC-249393, please use the search function in the future.