Difference between revisions of "Talk:Pre-release protocol"
(Created page with "In the discussion of the removal of the Chunk Allocation Packet, it says: "To deallocate memory you need to send a MapChunk packet, which only contains biome data for plains(...") |
|||
| Line 1: | Line 1: | ||
| − | In the discussion of the removal of the Chunk Allocation Packet, | + | In the discussion of the removal of the '''Chunk Allocation Packet''', the article says: "To deallocate memory you need to send a MapChunk packet, which only contains biome data for plains(all biome bytes set to 1)." According to my testing with a vanilla Minecraft 1.3 server, when a chunk goes out of range you actually get a Chunk Data (0x33) packet ground_up_continuous=true, primary_bit_map=0, add_bit_map=0, and real actual biome data (in my case it was mostly plains and some desert). This suggests that the sentence should be edited and this part should be removed: "for plains(all biome bytes set to 1)". If someone else can confirm this, we should make that change. I think this makes more sense, and it's easier to test for in the client because you don't have to look at the compressed data at all. |
--[[User:DavidEGrayson|DavidEGrayson]] 23:33, 28 July 2012 (MST) | --[[User:DavidEGrayson|DavidEGrayson]] 23:33, 28 July 2012 (MST) | ||
Revision as of 06:36, 29 July 2012
In the discussion of the removal of the Chunk Allocation Packet, the article says: "To deallocate memory you need to send a MapChunk packet, which only contains biome data for plains(all biome bytes set to 1)." According to my testing with a vanilla Minecraft 1.3 server, when a chunk goes out of range you actually get a Chunk Data (0x33) packet ground_up_continuous=true, primary_bit_map=0, add_bit_map=0, and real actual biome data (in my case it was mostly plains and some desert). This suggests that the sentence should be edited and this part should be removed: "for plains(all biome bytes set to 1)". If someone else can confirm this, we should make that change. I think this makes more sense, and it's easier to test for in the client because you don't have to look at the compressed data at all. --DavidEGrayson 23:33, 28 July 2012 (MST)
