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_dash_games_b
Level 19
(Tape was done in a way that gets rid of all the BUTTERFLIES, and removes all visible emeralds, then goes next to exit that was shown in LEVEL CREATOR with a least the number of emeralds need done before times runs out, all on a working tape)
Exit isn't opening up
Moderators: Flumminator, Zomis
-
- Posts: 248
- Joined: Mon Nov 13, 2017 4:16 pm
Exit isn't opening up
- Attachments
-
- 019.tape
- ~/.rocksndiamonds/tapes/bd_three_boulder_dash_games_b/019.tape
- (2.98 KiB) Downloaded 11 times
Strike a balance between generating new things/ideas, and being good/organized. Somewhere between a gibberish mess and nothing said/done. -
I've completed the core R'n'D levels! except for classic_emerald_mine Level 91 which needs two R'n'D brains!
I've completed the core R'n'D levels! except for classic_emerald_mine Level 91 which needs two R'n'D brains!
Re: Exit isn't opening up
I have checked this case, and you are right -- this level is indeed broken!
What happens is as follows: This is a BD style level in native GDS format (which is a GDash cave file in binary format, contrary to the many BD level files in BDCFF format, which is a text format). It is detected as being in "PLCK" format (which stands for "Peter Liepa Construction Kit" format, which is the game engine of the Boulder Dash Construction Kit, also known as Boulder Dash IV). It is (AFAIK) the only BD engine that in fact uses a mode where the first and last line of the playfield are _not scanned_, which means that all game elements on these two rows are effectively static (and usually consist solely of titan wall AKA steel wall). This also means that a closed exit in the first or last row will _never_ change to an open exit for this special cave format.
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.)
What happens is as follows: This is a BD style level in native GDS format (which is a GDash cave file in binary format, contrary to the many BD level files in BDCFF format, which is a text format). It is detected as being in "PLCK" format (which stands for "Peter Liepa Construction Kit" format, which is the game engine of the Boulder Dash Construction Kit, also known as Boulder Dash IV). It is (AFAIK) the only BD engine that in fact uses a mode where the first and last line of the playfield are _not scanned_, which means that all game elements on these two rows are effectively static (and usually consist solely of titan wall AKA steel wall). This also means that a closed exit in the first or last row will _never_ change to an open exit for this special cave format.
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.)
-
- Posts: 248
- Joined: Mon Nov 13, 2017 4:16 pm
Re: Exit isn't opening up
Wonder if originally it was in one format that worked, and then later converted to the format it's currently in.
Strike a balance between generating new things/ideas, and being good/organized. Somewhere between a gibberish mess and nothing said/done. -
I've completed the core R'n'D levels! except for classic_emerald_mine Level 91 which needs two R'n'D brains!
I've completed the core R'n'D levels! except for classic_emerald_mine Level 91 which needs two R'n'D brains!
Re: Exit isn't opening up
That's exactly the case here, yes. The original format was a C64 game, from which it was converted to GDS format, which introduced the problem. (Or, alternatively, the format is OK, but the flag to scan the first and last row is incorrectly set by the GDash GDS file format loader. I will try to find out...)BryanFRitt wrote: ↑Tue Jan 07, 2025 9:55 pm Wonder if originally it was in one format that worked, and then later converted to the format it's currently in.