I improved the consistency a bit in how the Diagram script handles the interaction between morph and captureMatrix. Normally the action specified by morph (if any) prevails over the captureMatrix. The exception is when the captureMatrix specifies burning/explosion (@). In that case a promotion specified by the morph won't suppress the explosion, and both will happen.
This now even applies to explosions as in Atomic Chess (selected by setting atomicCapture > 0), which by default would cause the capturing piece to blow up itself as well, and destroy friend and foe alike in the blast. (Which makes it different from burning, which only destroys foes, ald leaves the capturing piece on the capture square.) A morph can now overrule this self-destruction of the piece, by making it morph into a piece of choice.
I improved the consistency a bit in how the Diagram script handles the interaction between morph and captureMatrix. Normally the action specified by morph (if any) prevails over the captureMatrix. The exception is when the captureMatrix specifies burning/explosion (@). In that case a promotion specified by the morph won't suppress the explosion, and both will happen.
This now even applies to explosions as in Atomic Chess (selected by setting atomicCapture > 0), which by default would cause the capturing piece to blow up itself as well, and destroy friend and foe alike in the blast. (Which makes it different from burning, which only destroys foes, ald leaves the capturing piece on the capture square.) A morph can now overrule this self-destruction of the piece, by making it morph into a piece of choice.