Rocks'n'Diamonds

Found and fixed it! The problem was the recursive flood fill function, which went too deep and exploded the stack on a 128x128 sized level! :shock: (Did not happen on Linux with its 8 MB stack size, while it blew up the 1 MB stack on Windows. :cry: ) I've replaced the recursive function with an iter...

Yeah, right. That's because when moving players, there's a loop over all four players, starting with the first one (that's the yellow one). If he successfully started moving, the tile he is leaving is immediately marked as "free", so the second player can immediately start moving, too. Tha...

Thank you, Eizzoux, for helping out here!

Thank you for mentioning your observation -- this should indeed not happen, and should be treated as a graphical bug that should be fixed.

The "acid" element sort of violates the "unwritten law" that two elements cannot be at the same tile, in that a movable element can move towards a tile that is already occupied by the "acid" elements (causing the moving element to be absorbed). That is, the "acid&q...

The phenomen you just encountered is called "event queue", and it's not a bug, but a feature. ;-) But seriously: Yes, I already changed this behaviour once (and I still use a function "ClearEventQueue()" here and there, for example when customizing the keyboard and joystick contr...

Argh, that's horrible!

Indeed I was able to reproduce this inside a Windows 10 VM (while having no problems and no crashes on my Linux box and on my Mac)!

I will try to debug and fix this!

Hi mat, it seems that I am either not able to reproduce the described behaviour, or that I did not understand it correctly. I will describe what I just tested, so you may correct me if I did something differently than you had done it. Regarding "change a levelset after running the game", I...

Can't remember anymore, but I think you are right!

Well, that sounds strange ... I have to check this before I can say something about it, but I'm almost sure that you encountered something buggy.

Great to hear this, and thank you for this feedback! :-) When looking at some of your stack traces again, I have the suspicion that the problem (although it never happened on any of my systems, mainly Linux and Mac) could be this one: commit f5b65dacd63ac8767720f317ed227291a286e306 Date: Fri Feb 19 ...

Should all be fixed now with the latest version 4.2.3.1 (just released)!

Thanks again for quickly reporting these show-stopper bugs!

This patch release fixes two nasty bugs in the last minor release version:

• fixed horrible crash bug when using “last played level set” menu
• fixed unneeded reloading of artwork when using “last played level set” menu

Now available on the download page!

Since 4.2.3.0, the R'n'D Emscripten port (at https://www.artsoft.org/rocksndiamonds/play ) now also supports storing local data in the browser, so things like tapes, scores, edited levels, game progress and general settings are persisted between invocations of the game.

This is really a horrible bug! :oops: I've never encountered this when testing on my Linux box, but immediately (and reproducibly) get crashes when running on the Mac. I have no idea why this bug does not show up on my Linux system (which it should). :roll: The unneeded reloading of custom artwork w...