Rocks'n'Diamonds

Bug Report: Player is not killed when an indestructible non-walkable element is placed on top

• Versions: This bug is new in either 3.2.0, 3.2.1, or 3.2.2.
  Bug Type: Game Engine
  Example Level: http://www.zomis.net/rnd/download.php?id=575 (no longer works)
  Location: Level Play
  Repaired: Yes
  Repair Released: Yes
  Repair Released In: 3.2.3

Comments:
In 3.1.x and earlier versions of Rocks 'n' Diamonds, the player could be killed by placing a non-walkable element on top of it through a CE change with "use extended change target." This action will no longer kill the player.

Before CE actions, this was the only way to kill a player besides making elements smash the player or making them kill the player using the "Deadly when..." option.

This breaks many older levels.

I have checked this with 3.1.2 and 3.2.2, and I cannot find any difference so far. Could you please describe it in more detail?

The point that is a bit vague here is the "replace when" setting -- when you set it to "destructible" (both in 3.1.2 and 3.2.2), the player will be killed when the extended change area includes the tile with the player.

Did you miss this setting? Or what do I have to do to trigger a different behaviour in 3.1.2 and 3.2.2 here?

> This breaks many older levels.

Any example here would also help a lot -- at least those levels covered by my automated tape checks show no difference or failures here... :-/

Daniel (maybe you missed my reply), do you have an example level for your bug report?

Yes, it can be found here. (Sorry for the late reply.)

It's only indestructible elements which causes this, normal destructible but non walkable elements does kill the player. (You can try this by placing CE 1 at the position where the player stands to touch CE 2 in Daniel's level)

Thanks for the bug demonstration level -- just found and fixed that bug!

Zomis wrote:It's only indestructible elements which causes this, normal destructible but non walkable elements does kill the player.

Right. I made this clear in the level, but I did not make it clear here in the bug report.