Difference between revisions of "Talk:Chunk Format"
Jump to navigation
Jump to search
(Started discussion on 0x33 single chunk packet still seen in 1.4.6) |
Barneygale (talk | contribs) |
||
| Line 1: | Line 1: | ||
Actually the 0x33 Map chunk is still used by vanilla 1.4.6 server to send individual chunks; I'm seeing this packet in the protocol disassembly when the player is moving across chunk boundaries. I personally think the server sends 0x38 only when entering a world (start of session or transition to / from the Nether / End) and otherwise it sends 0x33 for each individual chunk that's coming into player's viewdistance. | Actually the 0x33 Map chunk is still used by vanilla 1.4.6 server to send individual chunks; I'm seeing this packet in the protocol disassembly when the player is moving across chunk boundaries. I personally think the server sends 0x38 only when entering a world (start of session or transition to / from the Nether / End) and otherwise it sends 0x33 for each individual chunk that's coming into player's viewdistance. | ||
[[User:Xoft|Xoft]] ([[User talk:Xoft|talk]]) 09:51, 27 December 2012 (MST) | [[User:Xoft|Xoft]] ([[User talk:Xoft|talk]]) 09:51, 27 December 2012 (MST) | ||
| + | :Fixed! [[User:Barneygale|Barneygale]] ([[User talk:Barneygale|talk]]) 08:03, 8 January 2013 (MST) | ||
Revision as of 15:03, 8 January 2013
Actually the 0x33 Map chunk is still used by vanilla 1.4.6 server to send individual chunks; I'm seeing this packet in the protocol disassembly when the player is moving across chunk boundaries. I personally think the server sends 0x38 only when entering a world (start of session or transition to / from the Nether / End) and otherwise it sends 0x33 for each individual chunk that's coming into player's viewdistance. Xoft (talk) 09:51, 27 December 2012 (MST)
- Fixed! Barneygale (talk) 08:03, 8 January 2013 (MST)
