Boulder Dash Forum

Thank you for the info. I haven’t thought that this would be possible…

Is this really regular behavior of the Amoeba?

https://youtu.be/x_guZQiXJrA

The remaining question is: how to extract the caves from that caves?

GDash (respectively any2gdash) can not convert games from C64 memory dumps where the title screen says "same game Y/N" and "number of screens:" - no idea which kit creates this. It simply does not find the caves in the dump.

Does anybody have a solution for this?

Is there a programmer here who could help with the problem that in OpenGL the screen is not centered but always in the lower left corner? Happens on all systems.

https://github.com/revvv/gdash-export-CrLi/issues/29

Interesting information! Now I got the confirmation that the magic wall timer was different in the original releases and changed beginning with 1stB (I suspended this already). I’m not sure if it doesn’t matter if we use 0 as infinite as I do not know a cave with time as large as 256. But if this is...

Please post an Issue at GitHub!

Hi Dustin. In my opinion, *.gds files are compressed by any2gdash.exe *.vsf emulator files. We will not do anything with these files. Gdash only saves in *.bd format I think that after correcting the incorrect *.gds files, it is worth removing them and leaving the correct *.bd file only then Regard...

I noticed that the butterfly in CLCK 3.0 behaves a little bit different than the same in GDash.

I have some troubles finding the corresponding amoeba growth probability from CLCK 3.0 to GDash. In the official Boulder Dash games and construction kit the probabilities are 3.125 % and 25 %. So only two values available. In CLCK 3.0 you have 8 different values (0, 1, 2, 3, 4, 5, 6, 7) Growth proba...

Just to mention this here in the thread, too: Development of GDash has been continued by revvv as mentioned above. Some bug fixes have been done, the editor works stable now. Best improvements yet: Automatic game controller support (bluetooth, too) Higher scaling factors for the game New optional an...

I wrote your solution in the GitHub issue: 0 is same as 999 or otherwise left alone at 0.

As I said - we need a quick and simple solution. The new maintainer of GDash, meonwax, won't dig too deep into the code, only mild not too complex changes are possible. All other things have to be done by cirix - and he doesn't have the time to continue. On a C64 the milling time is never 0 - even i...

To keep it simple I would do it that way: An additional option in the magic wall settings like „Milling time 0 is infinite“. *) if option „Milling time 0 is infinite“ is activated, value 0 should be handled the same as 999. *) if option „Milling time 0 is infinite“ is deactivated, value 0 should be ...

So the best solution would be if 0 means until the next second begins