Difference between revisions of "Talk:Pre-release protocol"
m (→How does the Map Data packet work now?: formatting fix) |
|||
| (11 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
| + | ==Protocol Change 13w21a== | ||
| + | It appears there may be a new packet in 13w21a. It may be a 2C packet. Anyone have any insight into the changes for this snapshot? | ||
| + | |||
| + | Thanks | ||
| + | :[[User:vbisbest|vbisbest]] 12:39, 29 May 2013 (EST) | ||
| + | |||
| + | 0x2C is known as Spawn Global Entity, like thunderbolt | ||
| + | |||
| + | --[[User:Mct|Mct]] ([[User talk:Mct|talk]]) 23:25, 23 May 2014 (UTC) | ||
| + | |||
| + | ==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. | 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. | ||
--[[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. | ||
| + | :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) | ||
| + | |||
| + | == Spawn player has changed == | ||
| + | |||
| + | This is what I got as a spawn player packet. | ||
| + | Packet size prefix is not included here and the stream is the complete packet. | ||
| + | |||
| + | 0C-Packet ID | ||
| + | AF-7B- Entity ID varint encoded | ||
| + | 68-F1-F7-49-8B-9F-37-27-86-3A-B1-4E-EA-1C-5C-83- My guess, UUID binary, was previously a string | ||
| + | FF-FF-F1-B5- X? | ||
| + | 00-00-08-D0- Y? | ||
| + | FF-FE-AE-66- Z? | ||
| + | 6B-D5-00-35-71-00-00-00-00-00-00-10-00-21-01-2C-82-00-52-00-00-02-D5-03-00-66-41-99-99-9A-47-00-00-00-00-08-00-09-00-0A-7F-7F | ||
| + | |||
| + | == Please commit before you change old packets == | ||
| + | |||
| + | Whenever a previously existing packet has been changed please add it to this page and save the old version before you change it. | ||
| + | |||
| + | This will make it easier to see what has changed. | ||
| + | |||
| + | Thanks | ||
| + | |||
| + | == 1.15 Chunk Biome Data Changes == | ||
| + | |||
| + | It seems like the new "Biomes" field in 0x22 replaces the Biomes field in https://wiki.vg/Chunk_Format#Data_structure | ||
| + | |||
| + | Ive only done some basic testing and if anyone can confirm that, I would suggest adding that to the docs. | ||
| + | |||
| + | == How does the Map Data packet work now? == | ||
| + | |||
| + | It says that the icons cound field is only present if "Tracking Position" is true. But how does the number of icons get determined now then? By the length of the packet? ―[[User:JochCool|JochCool]] ([[User talk:JochCool|talk]]) 18:35, 12 January 2021 (UTC) | ||
Latest revision as of 18:36, 12 January 2021
Contents
Protocol Change 13w21a
It appears there may be a new packet in 13w21a. It may be a 2C packet. Anyone have any insight into the changes for this snapshot?
Thanks
- vbisbest 12:39, 29 May 2013 (EST)
0x2C is known as Spawn Global Entity, like thunderbolt
--Mct (talk) 23:25, 23 May 2014 (UTC)
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)
Spawn player has changed
This is what I got as a spawn player packet. Packet size prefix is not included here and the stream is the complete packet.
0C-Packet ID AF-7B- Entity ID varint encoded 68-F1-F7-49-8B-9F-37-27-86-3A-B1-4E-EA-1C-5C-83- My guess, UUID binary, was previously a string FF-FF-F1-B5- X? 00-00-08-D0- Y? FF-FE-AE-66- Z? 6B-D5-00-35-71-00-00-00-00-00-00-10-00-21-01-2C-82-00-52-00-00-02-D5-03-00-66-41-99-99-9A-47-00-00-00-00-08-00-09-00-0A-7F-7F
Please commit before you change old packets
Whenever a previously existing packet has been changed please add it to this page and save the old version before you change it.
This will make it easier to see what has changed.
Thanks
1.15 Chunk Biome Data Changes
It seems like the new "Biomes" field in 0x22 replaces the Biomes field in https://wiki.vg/Chunk_Format#Data_structure
Ive only done some basic testing and if anyone can confirm that, I would suggest adding that to the docs.
How does the Map Data packet work now?
It says that the icons cound field is only present if "Tracking Position" is true. But how does the number of icons get determined now then? By the length of the packet? ―JochCool (talk) 18:35, 12 January 2021 (UTC)
