Page 1 of 1

Nodes that are not buildable_to sometimes get replaced

PostPosted: Sat Jan 12, 2013 02:21
by 0gb.us
It happens verry rarely, but sometimes when I place a node near another node, the first replaces the second. For example, I just tried to place an apple near some cobblestone, and the apple took the place of the cobblestone.

I have no idea how to replicate the error, but this isn't the first time it has happened.

PostPosted: Sat Jan 12, 2013 02:39
by jojoa1997
This might be the problem. I saw this in the API earlier.
buildable_to = false, -- If true, placed nodes can replace this node

PostPosted: Sat Jan 12, 2013 06:00
by 0gb.us
That would in deed cause the problem, but as the title of this topic states, it happens with nodes that are NOT buildable_to. In other words, buildable_to = false. Thanks though.