Bug introduced during a refactor in September 🤦 .
Method to add triggers to creatures was defaulting the logic source to the creature who owned it, since that was most common.
Glaceus' destroy-on-damage trigger got the override erased (Glaceus owns the logic, not the marked creature).
If the trigger is on a creature that has its own trigger handlers, it will attempt to process the Glaceus trigger reaction. If the various event payloads don't align with that said creature was expecting, null de-reference and 💥 .
Bug introduced during a refactor in September 🤦 .
Method to add triggers to creatures was defaulting the logic source to the creature who owned it, since that was most common. Glaceus' destroy-on-damage trigger got the override erased (Glaceus owns the logic, not the marked creature).
If the trigger is on a creature that has its own trigger handlers, it will attempt to process the Glaceus trigger reaction. If the various event payloads don't align with that said creature was expecting, null de-reference and 💥 .