Not sure if this is an intended consequence of the rules, but it seems strange enough to post.
If _Explosion is set to a value less than 100, or to a negative value that is less than the health of the produces tarstuff babies, then when the explosion removes tarstuff, any babies produced during the square-by-square removal procedure will survive the explosion.
Square-by-square removal is done from the top-left corner of the explosion and works down each column in turn. As a result, the babies left by the explosion are always from those squares that have an empty square to their S, E or SE. So a Tar Blob that looks like this:
TTTTTTTT
TTTTTTTT
TTTTTTTT
TTTTTTTT
TTTTTTTT
O~~~
...may end up looking like this:
TTTTTTTT
TTTTTTTT
TTTTT b
TTTTT b
TTTTTbbb
This is, of course, a natural consequence of the described code, but the resultant 'baby patterns' seem unintuitive.
I can think of three possibilities for dealing with this:
(1) Leave as is.
(2) Delay baby generation until *after* the explosion is done.
(3) Cause any tar hit by an explosion to become a damaged baby instead.
I'll note that tarstuff destruction occurs even if it was part of a Tar Mother -- if a bomb explodes a square that the Mother itself was on, then the tarstuff underneath is removed and the Mother gets damaged as normal.
Anyways, comments and opinions welcome.
/dy
