Boulder Dash Forum

Old GDash is here and goes back to 2015: https://bitbucket.org/czirkoszoltan/gdash/src/master/ My archived version is even a bit older, from 2013. But any2gdash was already lost at that point. It used to be available at http://jutas.eet.bme.hu/~cirix/gdash but it is gone. The page is in on archive.o...

Most, if not all of them should be right here in the database: https://www.boulder-dash.nl/bdgb/index.php Apparently, butterflies are not the only issue here. Some month ago, CWS noticed that my Crazy Dream 8+9 have the amoeba set far too fast in the current .BD files. Checking the .GDS file of Craz...

Clocks were designed that way by Prof. Knibble for the First Boulder series. I guess, you're not supposed to collect them while running away. Maybe you even need that piece of dirt in certain situations.

Probably one of those caves not thoroughly tested by the authors. It was most likely distributed with this bug at the time and never fixed. Unfortunately, with the masses of fan made caves combined with the inexperience we all started with, things like this happened every now and then. Some authors ...

No1 completely turned over to the Amiga scene early on. On that platform, Emerald Mine had a much more active scene than Boulder Dash, thus a bunch of games can be found here: https://www.emeraldmines.net/

According to the cave scan algorithm, it probably has to work that way -- Rockford enters the exit tile and wins the game, but is then (next tile to the right is handled) killed by the enemy (but has already won the game). Exactly as on any C64 version. The win flag is set immediately when picking ...

I would have to take a look at the engines code. Unlike modern engines, the original engines don't have a scanned flag. The scanned property is a separate element which gets reset to the regular element according to the effect table. The effect table is also used for explosion sequences. Elements wi...

For detecting duplicates, you should probably exclude the colors. Several C64 tools offer an option to color the caves automatically, which either depends on the cave slot or is completely random. Pretty sure, there are quite a few cases where such duplicate caves have different colors. There are se...

I can see now why in BD1, that some caves with a lot of elements (I, K, any cave with amoeba overgrowing) tend to result in slow movements. Does this problem persist in BD2, or is the routine fleshed out to effectively eliminate this? Most of the time, BD2 indeed eliminated speed variations and pre...

The biggest difference on classic scheduling is between BD1 and BD2. In BD1, there is just a delay loop wasting a predetermined number of cycles, depending on the level, thus it is very dependent on what's going on in the cave. This is also the reason, intermissions are significantly faster, since t...

I messed up that time with BDKIT, which had random placement, as well While BD1 uses the pseudo random generator with a seed. PLCK uses real random. As far as I understand, there were no division between the random elements and constant ones there. Indeed, while BD1 has those drawing instructions t...

https://i.ibb.co/Qj6hHNG/Screenshot-2024-08-03-at-13-43-55.png In RnD Gdash player would collect the 2nd, 4th and 6th. While missing the 1st, 3rd and 5th. Is it like in original? This is expected behavior and might be a good candidate for those Cave Scanning Order threads: https://www.boulder-dash....

You could easily check this out in GDash. Load BD1 to see how the caves are set up, and you can play with the random settings, if you want.
Of course, Gdash has much more possibilities than the original BD1, including placing anything on a per level basis, which BD1 can't.

I don't know what happened to that site.
I know that is indeed archived, though: https://web.archive.org/web/20240504193 ... -fans.com/

Just checked: <=0 values work like I said in Gdash, thus negative values should be allowed indeed.