Updated Krissz BD package
Posted: Sun Jan 11, 2026 5:52 pm
If you are interested in caves for the new Krissz BD engine, you might like to read this post in the BD forum. Especially the solution for that "Mona Lisa" cave is worth watching! 
A few questions about those Krissz-on-RnD packages (you may already have answered or explained some of this, this does not mean the answers stuck to my Swiss cheese^W^Wbrain...)
I know that you did not actually create the levels (you might possibly have created a few, as ones of the many members of the Krissz site...) -- but what is/was your role in creating the for-RnD subset packages? I think I understand that you did the repackaging, but it is only a guess.
The files (I mean the large Krissz-on-RnD package + the single 'Mona Lisa cave' package) do not appear to be on artsoft.org at all. They exist only as long gibberish names on mega.nz. Those sorts of URLs always bother me -- they can't be humanly remembered or communicated except by electronic copying (e.g. cut & paste); they can't be identified, understood, loosely 'trusted' at a glance. Are you not storing them here out of respect for copyright? But if you in fact created the collection (even if not the individual content) -- creating it and storing it somewhere 'not yours' seems like a tiny corner of the overall content situation, I don't really understand why it would matter...
But ok, let us suppose there's a good reason not to store the actual bits on artsoft.org. You are nevertheless pointing to them, albeit indirectly (pointer to post on boulder-dash.nl, which in turn points to mega.nz).
Given that, can I ask / recommend that a write-up and set of pointers also be added to the main RnD Levels & Artwork page?
Can I also ask, can those Krissz-on-RnD-at-mega.nz files be granted downloadable filenames on artsoft.org -- where they can be presumed to have a stable long-term name, even if it is just a redirect (and a future-patchable redirect, of course) to mega.nz? Or would that come too close to whatever issue causes you not to directly store the files?
Actually on a related matter, I wonder if your own files with embedded version numbers, like Emerald_Mine_Club-3.2.0.7z, could also have version-less endpoint names (Emerald_Mine_Club.7z & Emerald_Mine_Club.zip, in the example case). That would make it easier for someone to script up 'download RnD and all associated level materials, at their up to the moment current editions', without needing to constantly update.
Of course my request for a machine readable metadata for that would also cover that need. Then the script only needs to download the one master 'all recommended downloads metadata' file, then follow its instructions. (I imagine this would contain metadata like: url; human readable name; short description; author(s); copyright or license info; download size; unpacked size; sha256-or-similar integrity verificator... and I should dredge up that other thread and put this part there...)