Difference between revisions of "Talk:Pre-release protocol"
(Response) |
m |
||
| Line 3: | Line 3: | ||
--[[User:DavidEGrayson|DavidEGrayson]] 23:33, 28 July 2012 (MST) | --[[User:DavidEGrayson|DavidEGrayson]] 23:33, 28 July 2012 (MST) | ||
:In my client I check for the ground_up_continuous=true, primary_bit_map=0, add_bit_map=0. The biome data is sent because it is always sent. | :In my client I check for the ground_up_continuous=true, primary_bit_map=0, add_bit_map=0. The biome data is sent because it is always sent. | ||
| − | I don't know if it's real or not, but you don't need to check it | + | :I don't know if it's real or not, but you don't need to check it |
| − | [[User:Shoghicp|Shoghicp]] 12:15, 30 July 2012 (MST) | + | :[[User:Shoghicp|Shoghicp]] 12:15, 30 July 2012 (MST) |
Revision as of 19:15, 30 July 2012
Chunk Deallocation
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 of a custom client with a vanilla Minecraft 1.3 server, when a chunk goes out of range the server actually sends 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 to: "To deallocate memory you need to send a Chunk Data (0x33) packet which only contains biome data.". If someone else can confirm this, please post here. 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)
- In my client I check for the ground_up_continuous=true, primary_bit_map=0, add_bit_map=0. The biome data is sent because it is always sent.
- I don't know if it's real or not, but you don't need to check it
- Shoghicp 12:15, 30 July 2012 (MST)
