Holger, does this mean anything for the RnD engine? I think that the status quo is that yam yams eat only gems in their direct path. Will that continue to be the case? Or would you like to add a checkbox flag to yam yams in RnD, 'eat diamonds to the left and to the right of the direction they are moving towards'?Holger wrote: ↑Tue Sep 22, 2026 8:29 pm That's true! I wasn't aware of this so far, but have just checked with the original Emerald Mine and the original Diamond Caves on the Amiga (emulator). And indeed, it is just as you described it: In EM, the yams can eat diamonds to the left and to the right of the direction they are moving towards, while in DC they can only eat diamonds in the direction they are moving to.
I have just fixed this in the EM engine, using the DC compatibility flag. The change was clean and simple, as expected.![]()
Test version 1 of Rocks'n'Diamonds 4.4.3.0 available!
Moderators: Flumminator, Zomis
Re: Test version 1 of Rocks'n'Diamonds 4.4.3.0 available!
Re: Test version 1 of Rocks'n'Diamonds 4.4.3.0 available!
Very nice solution -- well done!
No, the R'n'D engine is not affected by this change in any way -- it will behave just as before.BrownSky wrote: ↑Wed Sep 23, 2026 3:42 amHolger, does this mean anything for the RnD engine? I think that the status quo is that yam yams eat only gems in their direct path. Will that continue to be the case? Or would you like to add a checkbox flag to yam yams in RnD, 'eat diamonds to the left and to the right of the direction they are moving towards'?Holger wrote: ↑Tue Sep 22, 2026 8:29 pm That's true! I wasn't aware of this so far, but have just checked with the original Emerald Mine and the original Diamond Caves on the Amiga (emulator). And indeed, it is just as you described it: In EM, the yams can eat diamonds to the left and to the right of the direction they are moving towards, while in DC they can only eat diamonds in the direction they are moving to.
I have just fixed this in the EM engine, using the DC compatibility flag. The change was clean and simple, as expected.![]()
And even better: The R'n'D engine (which is currently used for the DC levels) behaves just the same as the newly fixed EM/DC engine (that will be used for the DC levels starting with the next R'n'D version).
So yes, both the R'n'D engine and the EM engine in DC mode will allow yams to only eat diamonds in their direct path.
Only the EM engine in default mode (as used by the classic EM/EMC levels) will allow this (just as the original EMC games did) -- R'n'D levels and DC levels will stay with the well-known behavior of yams only eating diamonds in their direction of movement.
Re: Test version 1 of Rocks'n'Diamonds 4.4.3.0 available!
after a while i might've found some bugs
1. in the DC levelset, the switch gates use default RnD "pass through door" sfx instead of diamond caves's version
2. weird: if you walk into a switch gate switch from more than 1 tile away, (e.g. you're aligned with a switch and you walk toward the switch and never release that direction key) it does not activate, you have to walk toward it while you're already on a neighboring tile. this isn't how magic wheels work so i thought it beared mentioning
3. if you go into an open exit while you have a shield active, your character phases through the exit and can still walk around, but the timer starts ticking down and the game enters the "won level" state anyway
4. non-deadly shields are still accessible in the level editor in EM/DC mode, but appear as a "?" when the level is played. i suppose they should be in the "DC2" section instead of the "DC" section
1. in the DC levelset, the switch gates use default RnD "pass through door" sfx instead of diamond caves's version
2. weird: if you walk into a switch gate switch from more than 1 tile away, (e.g. you're aligned with a switch and you walk toward the switch and never release that direction key) it does not activate, you have to walk toward it while you're already on a neighboring tile. this isn't how magic wheels work so i thought it beared mentioning
3. if you go into an open exit while you have a shield active, your character phases through the exit and can still walk around, but the timer starts ticking down and the game enters the "won level" state anyway
4. non-deadly shields are still accessible in the level editor in EM/DC mode, but appear as a "?" when the level is played. i suppose they should be in the "DC2" section instead of the "DC" section
Re: Test version 1 of Rocks'n'Diamonds 4.4.3.0 available!
additionally:
5. if you're playing a DC level with default RnD graphics, and you pick up a shield, there is no visual difference between a player who is currently shielded and a player who is not. ideally tihs would just reuse the code to draw shields in the RnD engine, and have the custom artwork for the DC levelset disable that somehow in favor of a different player graphic (like it currently does).
6. "Magic wall (DC style)" tile should be in the DC2 category, not DC; if you place it in a DC level in the EM/DC engine it shows as a question mark.
7. in levels with two players where the players start adjacent to each other, (e.g Tutorial Levels 07 - It's Magic!), players are considered nonsolid to each other on the very first move, and so you can make them overlap if you immediately move them as soon as the level begins. i'm not sure if this is intended behavior or not. although if this is a bug then it is a bug with the EM engine and not just the DC compatibility version, e.g. level 41 of Emerald Mine (Kingsoft) in the EMC collection.
5. if you're playing a DC level with default RnD graphics, and you pick up a shield, there is no visual difference between a player who is currently shielded and a player who is not. ideally tihs would just reuse the code to draw shields in the RnD engine, and have the custom artwork for the DC levelset disable that somehow in favor of a different player graphic (like it currently does).
6. "Magic wall (DC style)" tile should be in the DC2 category, not DC; if you place it in a DC level in the EM/DC engine it shows as a question mark.
7. in levels with two players where the players start adjacent to each other, (e.g Tutorial Levels 07 - It's Magic!), players are considered nonsolid to each other on the very first move, and so you can make them overlap if you immediately move them as soon as the level begins. i'm not sure if this is intended behavior or not. although if this is a bug then it is a bug with the EM engine and not just the DC compatibility version, e.g. level 41 of Emerald Mine (Kingsoft) in the EMC collection.
Re: Test version 1 of Rocks'n'Diamonds 4.4.3.0 available!
Indeed -- fixed (in the sound set of the DC level set)!
I have just tested this with level 15 of the "Tutorial Levels" level set of the Diamond Caves level package, but was unable to reproduce this bug. When running towards that switch on the right, starting from the left, only using the "cursor right" key (after bringing the player to the same row as the switch), the switch always switches immediately when reaching it.2. weird: if you walk into a switch gate switch from more than 1 tile away, (e.g. you're aligned with a switch and you walk toward the switch and never release that direction key) it does not activate, you have to walk toward it while you're already on a neighboring tile. this isn't how magic wheels work so i thought it beared mentioning
Anything I am doing wrong here?
Oops, shield handling was indeed broken here -- should be fixed now!3. if you go into an open exit while you have a shield active, your character phases through the exit and can still walk around, but the timer starts ticking down and the game enters the "won level" state anyway
P.S.: Oops, forgot your other bug report -- will have a look at that one, too!
You're right -- moved that game element to the "DC2" section for now. (Although it should probably better be moved to the "RND" section, as this is in fact neither a DC not a DC2 game element...)4. non-deadly shields are still accessible in the level editor in EM/DC mode, but appear as a "?" when the level is played. i suppose they should be in the "DC2" section instead of the "DC" section
Good point. Although re-using code from the R'n'D engine is not possible here (it must be separately handled in the EM/DC engine, in a different way), I have added support for it now. The DC level set already disables these additional shield graphics, as you could already use the DC graphics for R'n'D level sets (with "shielded player" graphicss, but without separate shield graphics).ncrecc wrote: ↑Fri Nov 13, 2026 4:54 pm additionally:
5. if you're playing a DC level with default RnD graphics, and you pick up a shield, there is no visual difference between a player who is currently shielded and a player who is not. ideally tihs would just reuse the code to draw shields in the RnD engine, and have the custom artwork for the DC levelset disable that somehow in favor of a different player graphic (like it currently does).
That's right. Done!6. "Magic wall (DC style)" tile should be in the DC2 category, not DC; if you place it in a DC level in the EM/DC engine it shows as a question mark.
Yes, this works the same in plain EM and EM/DC engine mode. I think this is by intention, to prevent two adjacent players from blocking each others (that is, let both players do the same initial steps, without having to wait that the other player moves out of the way first).7. in levels with two players where the players start adjacent to each other, (e.g Tutorial Levels 07 - It's Magic!), players are considered nonsolid to each other on the very first move, and so you can make them overlap if you immediately move them as soon as the level begins. i'm not sure if this is intended behavior or not. although if this is a bug then it is a bug with the EM engine and not just the DC compatibility version, e.g. level 41 of Emerald Mine (Kingsoft) in the EMC collection.
Thanks a lot for your bug list, and for testing the test build of the upcoming version! As soon as bug #2 is sorted out, I will package a new test version so you can have a look again!
P.S.: Oops, forgot your other bug report -- will have a look at that one, too!
Re: Test version 1 of Rocks'n'Diamonds 4.4.3.0 available!
hm... here is a tape i recorded that consistently shows this issue when replayed (and, to be clear, was also something i experienced while i was recording it).Holger wrote: ↑Sat Nov 14, 2026 4:00 pmI have just tested this with level 15 of the "Tutorial Levels" level set of the Diamond Caves level package, but was unable to reproduce this bug. When running towards that switch on the right, starting from the left, only using the "cursor right" key (after bringing the player to the same row as the switch), the switch always switches immediately when reaching it.2. weird: if you walk into a switch gate switch from more than 1 tile away, (e.g. you're aligned with a switch and you walk toward the switch and never release that direction key) it does not activate, you have to walk toward it while you're already on a neighboring tile. this isn't how magic wheels work so i thought it beared mentioning
Anything I am doing wrong here?
when you actually try to play the level it's not consistent; for instance the previous time i tried this level both switches worked just fine, and the bug didn't happen until i went underneath the second switch and tried to walk into it.
i thought for a second this might be an issue with "zig-zag diagonal movement" setting but i disabled that and it's still going on.
Re: Test version 1 of Rocks'n'Diamonds 4.4.3.0 available!
Thanks a lot for the tape -- now I've got it, and it's fixed now! (The tape actually works now as expected.)
The problem was that the engine waits for "no movement input" after switching to be able to switch again (to prevent constant pressing against a switch resulting in permanent toggling of the switch, which is also not possible in the original game). Unfortunately, in the provided tape, the player was always moving before trying to switch again, which therefore did not work. The simple solution is to allow switching again after each successful movement.
The problem was that the engine waits for "no movement input" after switching to be able to switch again (to prevent constant pressing against a switch resulting in permanent toggling of the switch, which is also not possible in the original game). Unfortunately, in the provided tape, the player was always moving before trying to switch again, which therefore did not work. The simple solution is to allow switching again after each successful movement.