I'm wondering if we want to change this to be {monster} rather than {creature} because monster features regularly use creature to mean the target of the ability, so using creature as the fallback may result in some confusing wording.

See Swallow:
"If the creature takes 30 damage or more on a single turn from the swallowed creature, the creature must succeed…"

vs

"If the monster takes 30 damage or more on a single turn from the swallowed creature, the monster must succeed…"

I'm wondering if we want to change this to be {monster} rather than {creature} because monster features regularly use creature to mean the target of the ability, so using creature as the fallback may result in some confusing wording.

That makes sense, yeah. I can submit an update in a little bit here.

Do the features on the monsters themselves need this fallback? I would think probably not since they should always resolve. But I suppose if new monsters are created by dragging the monster features then they would end up with these fallbacks anyway.

At the very least it would reduce the size of this diff I suppose.

I don't feel strongly either way and can make the revisions if that's what we want. Having the fallback is nice so when imported and then dragged to an actor it's more readable.

Either way - not ready for merge yet as I found a few more instances of lookups without fallbacks.

Alright. 474 more adjustments - my regex searching wasn't catching the way YAML wraps lines. ALL monsters & monster features now have a fallback. Features I think is a good choice as mentioned above.