FOSS gamedev and creative worlds

hello,

i got some problems with my furnace and chest on a map here:
0.3.0 src downloaded, compiled under linux.
anyhow, my furnace and chest are "frozen":
when i start my local server, the furnace has some iron and rats in it, always the same, the chest is empty.
during a game-session i can add stuff and so on, but as soon as i restart my server, the furnace shows again iron and rats and the chest is empty...
so it worked in the beginning but now i can't change the contents anymore.
the only thing i changed was, that i installed the cisouns texture pack v6, but i can't say exactly wether the error occured directly after the installation of the texpack, but i think so.
how can i help you find that bug? what logs/files do you need?
anyway, great work, i really like minetest:)

greetings,
tank

HIYA TANK! Do you wanna build with me?

Lol what :D ??

do you want to build with me staffs?

btw: if i build a new chest, it's also broken..:)

what do i have to delete/move to try it with a new world?

tank wrote:what do i have to delete/move to try it with a new world?

If you want to delete your world you must just delete the world directory

i moved the world dir, created a new world, and the chest seems to work there

I have redownloaded MineTest 0.3.1 (Stable), joined the local server, collected enough leaves and wood to craft a chest, and placed the remaining wood into the chest. Afterwards, after disconnecting and reconnecting, the chest becomes empty. Here are the contents of debug.txt:

Pastebin

I'm guessing it has something to do with "17:31:09: INFO[main]: Client: ignoring player item for non-existing peer id 2", but I can't be sure.

I could reproduce this bug.

myself in #minetest-delta wrote:05:48 < kahrl_> http://celeron.55.lt/~celeron55/minetest/forum/viewtopic.php?id=363
05:48 < kahrl_> is there a bug that a node metadata change doesn't raise the
modified flag of the block?
05:52 < kahrl_> ... just tested, i can reproduce the bug
05:52 < kahrl_> 1) start a local game (i used creative mode, shouldn't matter
though)
05:52 < kahrl_> 2) place a chest, put something in it
05:52 < kahrl_> 3) disconnect and connect again => thing is still there
05:53 < kahrl_> 4) put something else in it, immediately disconnect and connect
again => thing isn't there

I currently suspect that the problem is (as I said in that quote) that moving something in or out a chest (aka a "node metadata change") doesn't mark the block as modified, therefore it will not be saved upon exit. (However, if something else causes the block to be marked as modified, such as placing a chest, it will be saved.)

EDIT: Seems that was right. This fixes at the least the case I have seen: patchset