Time  Nick   Message
20:28 luk3yx Mod storage appears to write multiple keys atomically if I set two keys without giving control back to C++ (i.e. storage:set_string("key1", "value1"); storage:set_string("key2", "value2")). Can I rely on this behaviour or is it an implementation detail that might change in the future?
20:43 Krock  luk3yx: huh? l_set_string is a C++ function that's called
20:44 Krock  or does the "storage" object refer to a Lua-only implementation of some sort?
20:45 luk3yx Sorry, that wasn't a great way of explaining it, the C++ code that saves mod storage is saved in Server::AsyncRunStep, so if I call storage:set_string twice without returning from my function the saving code won't ever get run.
20:45 luk3yx s/ever get run/get run until after both values are changed/
20:47 Krock  that's correct. I'll be in memory but not written to disk until later
20:48 Krock  the time when it will be written is afaik not specified, but it eventually will be written, just like the changed mapblocks.
20:55 luk3yx Okay, thanks
21:06 Krock  You're welcome.