ArchMageOmega
Level: Roachling
Rank Points: 9
Registered: 05-26-2005
IP: Logged

Edit: Ok, this isn't a bug...

If you have a skull with a ruby balanced on top (say, by having a ruby on either side as well) and you drop another gem on top of the ruby, it will stick to it (won't roll off).

Example:

(R-Ruby, S-Skull, #-Wall, .-Empty)

..R..
.....
.....
..R..
.RSR.
.###.

[Edited by ArchMageOmega at Local Time:06-04-2005 at 10:23 AM]

ArchMageOmega
Level: Roachling
Rank Points: 9
Registered: 05-26-2005
IP: Logged

File: xor1.SUB (445 bytes)
Downloaded 115 times.
License: Other
From: Unspecified

Here's another one that really just doesn't make much sense to me... (See attached file)

Edit: I looked at it a little closer and it seems to be caused by the laser hitting the turn-around switch. (I still have no idea why though.)

[Edited by ArchMageOmega at Local Time:06-04-2005 at 08:46 AM]

Krishh
Level: Master Delver
Rank Points: 282
Registered: 06-05-2004
IP: Logged

According to the master list of objects (accessable by F2), this is the intended behaviour. Always check that first if you have doubts about something!

ArchMageOmega
Level: Roachling
Rank Points: 9
Registered: 05-26-2005
IP: Logged

Ah, I see. I've looked through the list before, but there's a lot of info there.

Still, the second thing is surely a bug.

Radiant
Level: Moderator

Rank Points: 142
Registered: 02-05-2003
IP: Logged

The second thing is a bug, I'll see what I can do. The first thing is what I call an 'unintended consequence of complex behavior'

(to be precise, objects don't roll of an object if the latter is in motion; and a lasering ruby is considered in motion; and making an exception is not particularly easy in code)


____________________________
= Radiant =

ArchMageOmega
Level: Roachling
Rank Points: 9
Registered: 05-26-2005
IP: Logged

Unintended behaviors can be fun (as long as they don't break something). Part of what makes game programming interesting.