Rocks'n'Diamonds

Ok, not sure if this should be classed as a bug or a new idea, but...
When an element is set to dig various elements, if you have it set to leave behind the "element triggering change" It leaves behind a element triggering change, not the element it dug last

This "should" enable elements to seemingly travel fluidly over objects, as if it was empty space (or at least this is the behaviour i was expecting)

sure, its not a problem if you only have one element set because you can easly make so it changes the dug space to the same thing, but if you have several objects to be dug within a group element, you cant really do this without it looking wierd.

This is definitely a bug! :-o

Thanks for reporting it -- I'll have a look at it.
Should (hopefully) be easy to fix.

*edit*

When looking at this again now: I simply overlooked the fact that this isn't a "CE change" at all. So it's not really a bug.

But you might be right that one could probably expect the behaviour you described. So I'll see if this could be added that way. It would then be more something like a hidden feature, as the "element triggering change" would be "misused" as a kind of "last involved element" here. But I think it could be useful...

*edit*

Added this feature now. (It still has to go through the tape tests, though.)

OK, tape tests are just successfully finished.

This little new feature will then be available in 3.1.1.

(This could indeed work for creating "Dig Dug ghosts"...! :-) )

Or working pacman ghosts