the steel wall leveleditor bug

Found a bug in R'n'D? Report it here!

Moderators: Flumminator, Zomis

Post Reply
User avatar
RAP
Posts: 317
Joined: Sat Jun 19, 2004 6:44 pm

the steel wall leveleditor bug

Post by RAP »

Okay, set the playfield 3x3 and then draw the box around with steel walls.
When you undo it, the steel wall (leveleditor) is invisable; if you play it,
the level is completely invisable.

The bug wears off when you exit the level or go to the next level. :D

And...

Still if you cut the steel wall around by a piece and undo it, the steel wall
(leveleditor) remains visble due to the undoing with the steel walls around.

BTW: I added my own avatar for myself, check it out! It's a Grunt Tediz from the Conker game. :D
User avatar
Martijn
Posts: 794
Joined: Sat Jun 19, 2004 10:54 am
Location: the Netherlands (Holland)
Contact:

Post by Martijn »

This is by intention! At least, I used this for my Supaplex contribution levelset! Of course you can always change the border by configuring a graphicsinfo.conf (see my BD Dream levelset for example), but if that is the only thing you use the graphicsinfo.conf file for (when you are creating a classic levelset without custom graphics), this is a nice feature of the RnD level editor!
Visit my Boulder Dash website at:
http://www.bd-fans.com

Watch my avatar! That orange little thing is Murphy, the Supaplex star!
User avatar
Holger
Site Admin
Posts: 4073
Joined: Fri Jun 18, 2004 4:13 pm
Location: Germany
Contact:

Post by Holger »

No, Ryan was right (as with most of his bug reports) -- there is really a bug with displaying the steel wall level border in the level editor. Just try what he described and you will see it. This does not affect levels that are played from outside the level editor, but is (only) a graphical problem/bug when playing from inside the editor (and with displaying the level in the editor).

I just had to add the check for visible/invisible steel border to the "undo" operation in the editor to fix this.

Thanks, Ryan, for reporting this -- it's fixed now! :-)
Post Reply