Rocks'n'Diamonds

Those are just different animation steps of Acid and Amoeba, right? If they are only animation steps, they should not added to any element list, because this handles each engine different. Eg. even the "falling" elements in LogicDeLuxe proposal are handled from most tools/engine as normal elements ...

Maybe for clarity all elements that e.g. EM adds should be named EM_... , not just the overlapping ones.

Yes, this is the best way.
Except BD elements like "DIAMOND" as LogicDeLuxe said.

Please post it when you are ready with renaming,
so we can edit or add elements.

Hm, the RND_ID can change at any time, so we should take the "element_name"!!! Like as for Dave's engine or for other. I think Dave mean this in his last post. For the (old) engines its may be usefull to have the internal id, when it is sure that nobody delelop on it. Ok the internal id is nice to h...

Hi, I just upload "rndTest325-tc8" This edition can download from Zomis-Filearchiv within the normal menue. Special thanks to Zomis , who made some special php-scripts for easy select "all" or "levels" or "group". Load "all" entries: > rndTest_jue0 -urlbase=rndfalist0: Load "level" entries: > rndTes...

Hi,
because they exists in RnD, some properties are usefull:
GraphicSet=
MusicSet=
SoundSet=

eg. GraphicSet=BD2K3
if not given default is used.

Steffest wrote: If memory serves me well, there are some EM caves that use the explosion object in designtime. E.g. it can be used to delay a falling boulder for 1 frame. But that would be an execption offcourse ... For the delay the elements have a delayed property, like "BOULDERfd" Which stands f...

Hi, I just upload "rndTest325-tc7" (NewYear-Edition) Develop on this is in progress! This edition have a BDCFF configurable native loader. File "bdcff.conf". So RND have a common readable fileformat, because you can set each RND element as item! Some levels of DX-Boulderdash01 included. This are not...

Maybe with some small changes? like "key_red" maybe is more relevant then "key_1" ? (Allthough it also would make sense that a key_1 is needed to open door_1 and that the color doesn't really matter much.) Yes, this renaming makes more readable. Ok. Hmm, this process seems to scream for a wiki page...

Hi, Hm you add some elements which not exists in EM! Can we use the RND element names instead? For all (new) elements? Than we have a BDCFF proposal which cover the RND needs. ;) This makes things and tools easier! To save compatibility we should use the old names ( maybe additional ) which already ...

(Takes a while...) -###- Printing ElementInfo -###-: 0 ; empty_space ; `000 1 ; sand ; `001 2 ; wall ; `002 3 ; wall_slippery ; `003 4 ; rock ; `004 5 ; key_obsolete ; `005 6 ; emerald ; `006 7 ; exit_closed ; `007 8 ; player_obsolete ; `008 9 ; bug ; `009 10 ; spaceship ; `010 11 ; yamyam ; `011 12...

Even I like more the '1's as the '0's: I have to post again ;) FIREFLYd should have the two-byte code "od", FIREFLYr should have "or", aso. isn't it? Question: For the BUGleft - a change to "BUGl" is not necessary? Or for the other elements, which kind of this? Seems, I get a coauthor of this propos...

Ein gesundes und gutes neues Jahr!

The element names are used in some level files.
Like the BDCFF ones from "Arno Weber's Webpage".
So they should be compatible with the old ones,
which mentioned in "LogicDeLuxe's proposal".

I changed some elements for BD-C64 support: 20;BUTTERFLYd ;c;bd; 21;BUTTERFLYl ;C;bl; 22;BUTTERFLYu ;b;bu; 23;BUTTERFLYr ;B;br; 10;FIREFLYl ;Q;ol; 11;FIREFLYd ;o;od; 12;FIREFLYu ;O;ou; 13;FIREFLYr ;q;or; 14;BOULDER ;r;rr; 15;DIAMOND ;d;dd; only checked BD-C64 elements. release BDCFF support next yea...

This is cool! Also have planned to write a editor... (with QT) Too bad that I'm late. I took a first try with the editor and it look's very good. And the feature list is great. Even a ADF support is integrated. Do you plan to make the source of the editor open source? What program language do you us...