should mention "Note that functions will be dumped to bytecode by this function but will always error upon attempting to deserialize them (unless mod security is disabled), so this is not useful for that purpose."

This feels a little _too_ opinionated to me. I think that the configuration interface is fine if used properly, and is likely a lot faster for the simple k/v storage it's supposed to be than serialization. Noting that the `minetest.settings` object is global is good, even separating that part out into something like `CAUTION: This sets global settings, don't set global settings.` might be good.

```suggestion Userdata objects (like `ItemStack` for example) aren't supported. Threads (coroutines) aren't supported either. ```

This isn't super clear on what kind of function serialization is supported. Both bytecode and non-bytecode versions of functions can be deserialized (assuming the safe flag is false), but only non-bytecode functions can be serialized (iirc).

```suggestion Minetest alternatively offers a serializer implemented in Lua, which serializes to Lua source code, available as `minetest.serialize` and `minetest.deserialize`. The following values are supported: ```

Can you give an example of one which solves the issues presented by the Minetest implementation?