Time  Nick          Message
14:13 tech_exorcist hello
14:13 tech_exorcist i'm struggling to understand TOCLIENT_BLOCKDATA
14:14 tech_exorcist TOCLIENT_ADDNODE is well-documented and the coordinates make sense, so i tried to read them the same way from TOCLIENT_BLOCKDATA
14:16 tech_exorcist but if the first 6 bytes after the TOCLIENT_BLOCKDATA command (0x0020) are a v3s16 with the coordinates as in ADDNODE, why do i get coords like (-7, 0, -3) when i'm at around -60, 2, 15?
14:16 tech_exorcist actually let me check
14:17 tech_exorcist at (-162, 14, 71) the server seemingly sent a BLOCKDATA with coords (-12, 2, 3), and render distance isn't that high
14:17 tech_exorcist it was 110
14:23 tech_exorcist both the client and the server are running 5.6.1 on debian
15:44 sfan5         tech_exorcist: a block is 16x16x16
15:44 sfan5         thus the positions are numerically smaller, they would match when you translate them to node positions
15:47 tech_exorcist i see
15:48 tech_exorcist thanks
15:48 tech_exorcist and another question
15:48 tech_exorcist what exactly is the data that follows the coordinates?
15:49 sfan5         dunno, check the protocol docs
15:49 sfan5         probably the encoded mapblock
15:50 tech_exorcist it seems to be zstd, but i can't find a zstd decompressor that will decompress it
15:50 tech_exorcist the protocol docs don't say anything about TOCLIENT_BLOCKDATA
15:50 tech_exorcist https://github.com/minetest/minetest/blob/5.6.1/src/network/networkprotocol.h#L279
15:51 tech_exorcist TOCLIENT_ADDNODE below says it's a "serialized mapnode", but it doesn't seem to match doc/world_format.txt in the "The blob" section, which is the only thing i could find about serialization
16:08 sfan5         you'll have to search the code then
16:08 sfan5         the mapblock format is documented in world_format.txt