Rocks'n'Diamonds

Questions/Thoughts/Ponderings (before I forget) Extra movement happens at points saved during future playbacks. Is it not terminating the run at the right time the right way? Status of keyboard at save spots, key down / key up? Does paused status at this point have any effect? Does changing frame sp...

roughly PAL is 50 half frames per second, NTSC is 60 half frames per second. More exact ≈ to lesser exact ≈ to even lesser exact 24×1000÷1001 ≈ 119.88/5=23.976 ≈ 24 ...? ≈ 50/2=25 (?is this 119.88×5/24=24.975?) 30000÷1001 ≈ 119.88/4=29.97 ≈ 60/2=30 https://en.wikipedia.org/wiki/List_of_broadcast_vid...

MAIN MENU > LEVELSET > BOULDER DASH > VARIOUS > BOULDER DASH 3 ATARI > 10: INTERMISSION 2 /1 ~/.rocksndiamonds/tapes/bd_boulder_dash_3_atari/010.tape This level seems like it needs another second(or so?) to be able to complete in time. (same goes for level 030: INTERMISSION 2 / 2 , ...?)

As far as I was able to find out, this bug apparently already existed in the original C64 version of this level set. Whatever might have been the true cause for this level being unsolvable, I have now manually fixed it and re-released the BD level collection package. So after updating the level col...

When in paused in 'START GAME IN PAUSE MODE', when a tape is quick loaded, the status data(Emeralds remaining, tape time, ...) is the initial level load data instead of current data of the newly loaded tape.

MAIN MENU > SETUP > GAME & MENU > START GAME IN PAUSE MODE

I will ask the experts in the Boulder Dash forum if anybody is aware of this (type of) problem, and how a solution might look like. (Which could be just converting the cave set to BDCFF format and then simply manually changing that flag for that level.) Wonder if originally it was in one format tha...

For this level LEVEL CREATOR shows it as having an exit, but even when getting enough EMERALDS the exit doesn't open. "BOULDER DASH" > "THE BREMER TOWN MUSICUS" >"THREE BOULDER DASH GAMES B" ~/.rocksndiamonds/levels/Boulder_Dash/The_Bremer_Town_Musicus/bd_three_boulder_...

Bad tape. When I load this, tape it says it's 4:00, then when I then click on stop [] the time goes to 2:32. BOULDER DASH > ACHIM HAERTEL > ACHIM HAERTEL > 014: CAVE 14 ~/.rocksndiamonds/tapes/bd_achim_haertel/014.tape weird... Not sure what I changed if anything, but tested again right before submi...

[Not exactly what you're asking for, but maybe this will help...]

Try compiling Rocks'n'diamonds with `make --debug`,
The debug compile version has options that can change speed on demand
viewtopic.php?t=3591

The solved Boulder_Dash levels don't seem to be showing up in https://api.artsoft.org, Is this intentional since this is 'pre-release' version? Will they show up in later builds? Regarding the new "Classic Boulder Dash (native engine)": I just forgot to add this set to the high score serv...

The solved Boulder_Dash levels don't seem to be showing up in https://api.artsoft.org, Is this intentional since this is 'pre-release' version? Will they show up in later builds?

Also, It seems Boulder_Dash is more likely to produce bad tapes than other levels.

In playing with settings some more, it seems this must be 'TEAMS' made for local play issue only happens if 'PREFERRED NETWORK PLAYER:' is anything other than 'player_1' (Yellow), even though this is a local one player game. MAIN MENU > SETUP > GAME & MENU > PREFERRED NETWORK PLAYER: > 'network_...

That's the crash bug as described by ncrecc, and it's fixed now. Thanks Very strange. Could you please try if this also happens if you temporarily rename your ~/.rocksndiamonds/setup.conf file (that contains the setup settings), that is, test this case with all setup settings completely reset to de...

Currently in a 'debug' compile there's a feature that can change game speed via a keyboard shortcut. This could be put in non-debug version too. Although, there could be some changes to make it easier to mess with like: Change shortcuts to be a switch to speed, instead of the current toggle between ...

It seems that the [] STOP |> PLAY restore has a tiny bit of extra time right after the cut stopping point that it shouldn't have, and that's why doing this making sure not moving at same point for cut point for both types of restores works around the issue. Also that it seems this work around doesn'...