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.
FOSS gamedev and creative worlds
This is a mostly frozen copy of the Minetest forums through 2017. If you know phpBB3 and would like to host any G-rated forum here, you can email: me@minetest.org If the email doesn't work, find out who's taken over Final Minetest from OldCoder and email them to get write access or an admin account.
I should have set this up years ago. But it's no tale of woe.
Whether the temperature is high or low, regardless of cold winds blow,
away we go like Edgar Allan Poe, on now with the show. BTW rhymes are welcome.
Nodes that are not buildable_to sometimes get replaced
3 posts
• Page 1 of 1
-
0gb.us - Member
- Posts: 841
- Joined: Sun Sep 16, 2012 01:55
-
jojoa1997 - Member
- Posts: 2890
- Joined: Thu Dec 13, 2012 05:11
This might be the problem. I saw this in the API earlier.
buildable_to = false, -- If true, placed nodes can replace this node
buildable_to = false, -- If true, placed nodes can replace this node
Coding;
1X coding
3X debugging
12X tweaking to be just right
1X coding
3X debugging
12X tweaking to be just right
-
0gb.us - Member
- Posts: 841
- Joined: Sun Sep 16, 2012 01:55
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.
3 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 12 guests