Please have a look at the latest pre-release version 3.2.0-5: I added an option "[x] block snap field when snapping" for the player which is now enabled by default (and disabled for all older levels).
This causes gems or sand which are snapped (instead of being collected or digged) to disappear in an animated way instead of disappearing from one frame to the next. This behaviour is now closer to the original behaviour in Emerald Mine, where snapping was animated in a similar way.
What do you think of if? Does it "feel" better than before? Or should this option default to "off"?
Delayed snapping
Moderators: Flumminator, Zomis
For compatability sake it should be off by default, but its a great feature and should remain in the engine 
Also notice that some elements arnt dug correctally when snapped (mainly ones that arnt supposed to be snapped)
Try it with the Diamond caves 2 landmine graphic when applied to a CE, it removes the edges of the mine, then the mine itself vanishes.
Also with the Emerald Mines acid sand, or plant as its known as on RnD.
*Edit* ah, just read the part about it being disabled for earlyer levels, in this case being enabled by default should be fine.
Also notice that some elements arnt dug correctally when snapped (mainly ones that arnt supposed to be snapped)
Try it with the Diamond caves 2 landmine graphic when applied to a CE, it removes the edges of the mine, then the mine itself vanishes.
Also with the Emerald Mines acid sand, or plant as its known as on RnD.
*Edit* ah, just read the part about it being disabled for earlyer levels, in this case being enabled by default should be fine.
I'd set it default to off. This new feature is nice, but if one level doesn't have this and another one does have, it's confusing.
but can this be changed manually in the game?
but can this be changed manually in the game?
Visit my Boulder Dash website at:
http://www.bd-fans.com
Watch my avatar! That orange little thing is Murphy, the Supaplex star!
http://www.bd-fans.com
Watch my avatar! That orange little thing is Murphy, the Supaplex star!
I agree with Martijn. Set the default value to off.Martijn wrote:I'd set it default to off. This new feature is nice, but if one level doesn't have this and another one does have, it's confusing.
but can this be changed manually in the game?
I don't think the default value can be changed in the game, only the value for the current level. See properties for player.
> But could this effect gameplay in some other way as well?
Yes, it will (because it delays the snapping for 8 frames or so).
> For example, a rock with sand under it, I snap away the sand.
> Will it then take a few extra frames for the rock to start falling?
Yep, exactly. (Just like in the original Emerald Mine engine.)
> For compatability sake it should be off by default, but its a great feature
> and should remain in the engine
Good to know this. Of course there are no compatibility problems, as it's only enabled for newly created levels.
> Also notice that some elements arnt dug correctally when snapped
> (mainly ones that arnt supposed to be snapped)
Does this really happen with elements that either have a correctly defined digging animation or no animation at all? Should look fine in both cases.
> Try it with the Diamond caves 2 landmine graphic when applied to a CE, it
> removes the edges of the mine, then the mine itself vanishes.
> Also with the Emerald Mines acid sand, or plant as its known as on RnD.
Yes, that's because a graphic definition of a crumbled, but not diggable element is used for a diggable CE. This must go wrong! :-)
(But such things can probably constructed with other "misused" graphics, too.)
> *Edit* ah, just read the part about it being disabled for earlyer levels, in
> this case being enabled by default should be fine.
Yep, I also think this. :-)
> I'd set it default to off. This new feature is nice, but if one level doesn't
> have this and another one does have, it's confusing.
Then I would have to completely remove it. Setting the default to "off" wouldn't stop people from re-enabling it. Besides that, all EM and EMC levels use that feature, so it's probably less confusing to also use it...
> but can this be changed manually in the game?
Yes: Player settings, "[x] block snapped field when snapping".
> I agree with Martijn. Set the default value to off.
Well, see above...
Yes, it will (because it delays the snapping for 8 frames or so).
> For example, a rock with sand under it, I snap away the sand.
> Will it then take a few extra frames for the rock to start falling?
Yep, exactly. (Just like in the original Emerald Mine engine.)
> For compatability sake it should be off by default, but its a great feature
> and should remain in the engine
Good to know this. Of course there are no compatibility problems, as it's only enabled for newly created levels.
> Also notice that some elements arnt dug correctally when snapped
> (mainly ones that arnt supposed to be snapped)
Does this really happen with elements that either have a correctly defined digging animation or no animation at all? Should look fine in both cases.
> Try it with the Diamond caves 2 landmine graphic when applied to a CE, it
> removes the edges of the mine, then the mine itself vanishes.
> Also with the Emerald Mines acid sand, or plant as its known as on RnD.
Yes, that's because a graphic definition of a crumbled, but not diggable element is used for a diggable CE. This must go wrong! :-)
(But such things can probably constructed with other "misused" graphics, too.)
> *Edit* ah, just read the part about it being disabled for earlyer levels, in
> this case being enabled by default should be fine.
Yep, I also think this. :-)
> I'd set it default to off. This new feature is nice, but if one level doesn't
> have this and another one does have, it's confusing.
Then I would have to completely remove it. Setting the default to "off" wouldn't stop people from re-enabling it. Besides that, all EM and EMC levels use that feature, so it's probably less confusing to also use it...
> but can this be changed manually in the game?
Yes: Player settings, "[x] block snapped field when snapping".
> I agree with Martijn. Set the default value to off.
Well, see above...
