Classic Protocol Extension/Proposals - Revision history

imported>Rainb0wSkeppy: fix typo

2024-01-14T13:25:24Z

fix typo

← Older revision		Revision as of 13:25, 14 January 2024
Line 1,523:		Line 1,523:
	:Proposed by [[User:Rainb0wSkeppy\|Rainb0wSkeppy]] ([[User talk:Rainb0wSkeppy\|talk]]) 22:43, 20 June 2023 (UTC)		:Proposed by [[User:Rainb0wSkeppy\|Rainb0wSkeppy]] ([[User talk:Rainb0wSkeppy\|talk]]) 22:43, 20 June 2023 (UTC)
	:Allows the server to remove, insert and replace messages, set the background and foreground color of the messages, and send messages longer then 64 characters		:Allows the server to remove, insert and replace messages, set the background and foreground color of the messages, and send messages longer then 64 characters
	:'''Motivation''': To allow the server to send messages longer then 64 characters, highlight parts of chat by changing ~~thw~~ background color and to edit and delete messages after they have been sent (eg. a moderator removing messages that break the rules)		:'''Motivation''': To allow the server to send messages longer then 64 characters, highlight parts of chat by changing the background color and to edit and delete messages after they have been sent (eg. a moderator removing messages that break the rules)
	:'''Client Behavior''': The client must read 2 characters after the &, the first one is the foreground and the second one is the background, When the server sends a message, the client inserts in the correct place, When the Position field is 0xff the client should not send a message until the Position field isn't 0xff, then concatenate the messages, When the server sends a DeleteMessage packet, it deletes the specified message		:'''Client Behavior''': The client must read 2 characters after the &, the first one is the foreground and the second one is the background, When the server sends a message, the client inserts in the correct place, When the Position field is 0xff the client should not send a message until the Position field isn't 0xff, then concatenate the messages, When the server sends a DeleteMessage packet, it deletes the specified message
	:'''Server Behavior''': The server may send messages with the Position field and send DeleteMessage packets		:'''Server Behavior''': The server may send messages with the Position field and send DeleteMessage packets

imported>Rainb0wSkeppy: move ExtServerMessages Message packet to a separate packet to be compatible with MessageTypes

2024-01-14T12:27:52Z

move ExtServerMessages Message packet to a separate packet to be compatible with MessageTypes

← Older revision		Revision as of 12:27, 14 January 2024
Line 1,526:		Line 1,526:
	:'''Client Behavior''': The client must read 2 characters after the &, the first one is the foreground and the second one is the background, When the server sends a message, the client inserts in the correct place, When the Position field is 0xff the client should not send a message until the Position field isn't 0xff, then concatenate the messages, When the server sends a DeleteMessage packet, it deletes the specified message		:'''Client Behavior''': The client must read 2 characters after the &, the first one is the foreground and the second one is the background, When the server sends a message, the client inserts in the correct place, When the Position field is 0xff the client should not send a message until the Position field isn't 0xff, then concatenate the messages, When the server sends a DeleteMessage packet, it deletes the specified message
	:'''Server Behavior''': The server may send messages with the Position field and send DeleteMessage packets		:'''Server Behavior''': The server may send messages with the Position field and send DeleteMessage packets
	:<h4>~~Message~~ packet</h4>		:<h4>ExtServerMessage packet</h4>
	:''Server to client''		:''Server to client''
	:{\| class="wikitable"		:{\| class="wikitable"
Line 1,536:		Line 1,536:
	! class="col4" \| Notes		! class="col4" \| Notes
	\|- class="row1"		\|- class="row1"
	\| class="col0 centeralign" rowspan="3" \| ~~0x0d~~		\| class="col0 centeralign" rowspan="3" \| 0x??
	(13)		(??)
	\| class="col1 centeralign" \| Position		\| class="col1 centeralign" \| Position
	\| class="col2 centeralign" \| byte		\| class="col2 centeralign" \| byte
	\| class="col3 centeralign" \| 0		\| class="col3 centeralign" \| 0
	\| class="col4 centeralign" \| The position of the message. 0 is after the last message, 1 is between the last and the 2nd last message, 2 is between the 2nd last and the 3nd last message, etc. Position of 255 means the message should not be shown and be concatenated with the next ~~message~~.		\| class="col4 centeralign" \| The position of the message. 0 is after the last message, 1 is between the last and the 2nd last message, 2 is between the 2nd last and the 3nd last message, etc. Position of 255 means the message should not be shown and should be concatenated with the next ExtServerMessage packet.
	\|- class="row2"		\|- class="row2"
	\| class="col1 centeralign" \| Message		\| class="col1 centeralign" \| Message

imported>Rainb0wSkeppy: better motivation

2023-07-22T19:04:28Z

better motivation

← Older revision		Revision as of 19:04, 22 July 2023
Line 1,523:		Line 1,523:
	:Proposed by [[User:Rainb0wSkeppy\|Rainb0wSkeppy]] ([[User talk:Rainb0wSkeppy\|talk]]) 22:43, 20 June 2023 (UTC)		:Proposed by [[User:Rainb0wSkeppy\|Rainb0wSkeppy]] ([[User talk:Rainb0wSkeppy\|talk]]) 22:43, 20 June 2023 (UTC)
	:Allows the server to remove, insert and replace messages, set the background and foreground color of the messages, and send messages longer then 64 characters		:Allows the server to remove, insert and replace messages, set the background and foreground color of the messages, and send messages longer then 64 characters
	:'''Motivation''': To ~~let~~ the server ~~highlight messages~~ to ~~make them stand out,~~ send longer ~~messages~~ and ~~remove messages (eg. to allow a moderator~~ to delete messages after they have been sent) (~~and probably~~ a ~~lot of other stuff~~)		:'''Motivation''': To allow the server to send messages longer then 64 characters, highlight parts of chat by changing thw background color and to edit and delete messages after they have been sent (eg. a moderator removing messages that break the rules)
	:'''Client Behavior''': The client must read 2 characters after the &, the first one is the foreground and the second one is the background, When the server sends a message, the client inserts in the correct place, When the Position field is 0xff the client should not send a message until the Position field isn't 0xff, then concatenate the messages, When the server sends a DeleteMessage packet, it deletes the specified message		:'''Client Behavior''': The client must read 2 characters after the &, the first one is the foreground and the second one is the background, When the server sends a message, the client inserts in the correct place, When the Position field is 0xff the client should not send a message until the Position field isn't 0xff, then concatenate the messages, When the server sends a DeleteMessage packet, it deletes the specified message
	:'''Server Behavior''': The server may send messages with the Position field and send DeleteMessage packets		:'''Server Behavior''': The server may send messages with the Position field and send DeleteMessage packets

imported>Rainb0wSkeppy: swap Position and Message fields to be the same as the classic Message packet

2023-07-05T21:15:52Z

swap Position and Message fields to be the same as the classic Message packet

← Older revision		Revision as of 21:15, 5 July 2023
Line 1,538:		Line 1,538:
	\| class="col0 centeralign" rowspan="3" \| 0x0d		\| class="col0 centeralign" rowspan="3" \| 0x0d
	(13)		(13)
			\| class="col1 centeralign" \| Position
			\| class="col2 centeralign" \| byte
			\| class="col3 centeralign" \| 0
			\| class="col4 centeralign" \| The position of the message. 0 is after the last message, 1 is between the last and the 2nd last message, 2 is between the 2nd last and the 3nd last message, etc. Position of 255 means the message should not be shown and be concatenated with the next message.
			\|- class="row2"
	\| class="col1 centeralign" \| Message		\| class="col1 centeralign" \| Message
	\| class="col2 centeralign" \| string		\| class="col2 centeralign" \| string
	\| class="col3 centeralign" \| &70Rainb0wSkeppy: &f0hi		\| class="col3 centeralign" \| &70Rainb0wSkeppy: &f0hi
	\| class="col4 centeralign" \| The message to be sent		\| class="col4 centeralign" \| The message to be sent
	~~\|- class="row2"~~
	~~\| class="col1 centeralign" \| Position~~
	~~\| class="col2 centeralign" \| byte~~
	~~\| class="col3 centeralign" \| 0~~
	\| class="col4 centeralign" \| The position of the message. 0 is after the last message, 1 is between the last and the 2nd last message, 2 is between the 2nd last and the 3nd last message, etc. Position of 255 means the message should not be shown and be concatenated with the next message.
	\|- class="row3"		\|- class="row3"
	! class="col0" \| Total Size:		! class="col0" \| Total Size:

imported>Rainb0wSkeppy at 22:43, 20 June 2023

2023-06-20T22:43:43Z

← Older revision		Revision as of 22:43, 20 June 2023
Line 1,519:		Line 1,519:
	:(Comments go here, please sign them)		:(Comments go here, please sign them)
	Most of this is copy/pasted from ExtendedBlocks v1, though BulkBlockUpdate has been updated to support the new blocks. This probably also needs the ability for more than 512 textures, but that's a seperate packet. Also maybe a packet to say how many blocks server/client supports? Also also, feel free to edit this; just sign on the top too. [[User:Infernity\|Infernity]] ([[User talk:Infernity\|talk]]) 17:19, 15 June 2022 (UTC)		Most of this is copy/pasted from ExtendedBlocks v1, though BulkBlockUpdate has been updated to support the new blocks. This probably also needs the ability for more than 512 textures, but that's a seperate packet. Also maybe a packet to say how many blocks server/client supports? Also also, feel free to edit this; just sign on the top too. [[User:Infernity\|Infernity]] ([[User talk:Infernity\|talk]]) 17:19, 15 June 2022 (UTC)

			===ExtServerMessages===
			:Proposed by [[User:Rainb0wSkeppy\|Rainb0wSkeppy]] ([[User talk:Rainb0wSkeppy\|talk]]) 22:43, 20 June 2023 (UTC)
			:Allows the server to remove, insert and replace messages, set the background and foreground color of the messages, and send messages longer then 64 characters
			:'''Motivation''': To let the server highlight messages to make them stand out, send longer messages and remove messages (eg. to allow a moderator to delete messages after they have been sent) (and probably a lot of other stuff)
			:'''Client Behavior''': The client must read 2 characters after the &, the first one is the foreground and the second one is the background, When the server sends a message, the client inserts in the correct place, When the Position field is 0xff the client should not send a message until the Position field isn't 0xff, then concatenate the messages, When the server sends a DeleteMessage packet, it deletes the specified message
			:'''Server Behavior''': The server may send messages with the Position field and send DeleteMessage packets
			:<h4>Message packet</h4>
			:''Server to client''
			:{\| class="wikitable"
			\|- class="row0"
			! class="col0" \| Packet ID
			! class="col1" \| Field Name
			! class="col2" \| Field Type
			! class="col3" \| Example
			! class="col4" \| Notes
			\|- class="row1"
			\| class="col0 centeralign" rowspan="3" \| 0x0d
			(13)
			\| class="col1 centeralign" \| Message
			\| class="col2 centeralign" \| string
			\| class="col3 centeralign" \| &70Rainb0wSkeppy: &f0hi
			\| class="col4 centeralign" \| The message to be sent
			\|- class="row2"
			\| class="col1 centeralign" \| Position
			\| class="col2 centeralign" \| byte
			\| class="col3 centeralign" \| 0
			\| class="col4 centeralign" \| The position of the message. 0 is after the last message, 1 is between the last and the 2nd last message, 2 is between the 2nd last and the 3nd last message, etc. Position of 255 means the message should not be shown and be concatenated with the next message.
			\|- class="row3"
			! class="col0" \| Total Size:
			\| class="col1 rightalign" colspan="4" \| 66 bytes
			\|}
			:<h4>DeleteMessage packet</h4>
			:''Server to client''
			:{\| class="wikitable"
			\|- class="row0"
			! class="col0" \| Packet ID
			! class="col1" \| Field Name
			! class="col2" \| Field Type
			! class="col3" \| Example
			! class="col4" \| Notes
			\|- class="row1"
			\| class="col0 centeralign" rowspan="3" \| 0x??
			(??)
			\| class="col1 centeralign" \| Position
			\| class="col2 centeralign" \| byte
			\| class="col3 centeralign" \| 0
			\| class="col4 centeralign" \| The position of the message. 0 is the last message, 1 is the 2nd last message, 2 is the 3nd last message, etc.
			\|- class="row3"
			! class="col0" \| Total Size:
			\| class="col1 rightalign" colspan="4" \| 2 bytes
			\|}

			:(Comments go here, please sign them)

imported>Infernity at 17:23, 15 June 2022

2022-06-15T17:23:28Z

← Older revision		Revision as of 17:23, 15 June 2022
Line 1,518:		Line 1,518:
	* The remaining 256 bytes store the higher 8 bits of the ID for each of the 256 blocks.		* The remaining 256 bytes store the higher 8 bits of the ID for each of the 256 blocks.
	:(Comments go here, please sign them)		:(Comments go here, please sign them)
	Most of this is copy/pasted from ExtendedBlocks v1, though BulkBlockUpdate has been updated to support the new blocks. This probably also needs the ability for more than 512 textures, but that's a seperate packet. [[User:Infernity\|Infernity]] ([[User talk:Infernity\|talk]]) 17:19, 15 June 2022 (UTC)		Most of this is copy/pasted from ExtendedBlocks v1, though BulkBlockUpdate has been updated to support the new blocks. This probably also needs the ability for more than 512 textures, but that's a seperate packet. Also maybe a packet to say how many blocks server/client supports? Also also, feel free to edit this; just sign on the top too. [[User:Infernity\|Infernity]] ([[User talk:Infernity\|talk]]) 17:19, 15 June 2022 (UTC)

imported>Infernity: ExtendedBlocks specification v2 proposal

2022-06-15T17:19:32Z

ExtendedBlocks specification v2 proposal

← Older revision		Revision as of 17:19, 15 June 2022
Line 1,421:		Line 1,421:

	:(Comments go here, please sign them)		:(Comments go here, please sign them)


			===ExtendedBlocks v2===
			:Proposed by [[User:Infernity\|Infernity]] ([[User talk:Infernity\|talk]]) 17:19, 15 June 2022 (UTC)
			:Allows using more than 768 blocks.
			:'''Motivation''': Allows for ever-more-detailed maps by sending up to 65,536 blocks.
			:'''Client Behavior''': Clients must adjust how they read the map as described in the '''Affect on map sending''' section. Clients must also adjust how they read and write several fields of the packets described in the '''Affect on other packets''' section. When a client detects that the secondary map blocks array is used, it must switch from accessing blocks via <code>map.blocks[index]</code> to <code>map1.blocks[index] \| (map2.blocks[index] << 8)</code> instead.
			:'''Server Behavior''': Servers must adjust how they write the map as described in the '''Affect on map sending''' section. Servers must also adjust how they read and write several fields of the packets described in the '''Affect on other packets''' section. Ideally, servers should avoid sending a secondary map blocks array when possible to minimise client memory usage.

			:<h4>Affect on map sending</h4>
			Essentially, instead of '''LevelDataChunk''' packets just being used to send the compressed form of the map blocks array, it is repurposed to send both the compressed form of the 'main' map blocks array and optionally a secondary map blocks array.
			To accomplish this, the '''Percent Complete''' field in the '''LevelDataChunk''' packet is repurposed. A value of ''0'' indicates that this LevelDataChunk packet contains part of the compressed data for the 'main' map blocks array, while a value of ''1'' indicates this LevelDataChunk packet contains part of the compressed data for the optional secondary map blocks array.

			The client and server should treat the '''LevelDataChunk''' packets used for the 'main' map blocks array as completely separate from the secondary map blocks array, i.e. the 'main' map blocks array should be compressed and decompressed completely independently of the optional secondary map blocks array.

			'''Note:''' Even if the server only sends a 'main' map blocks array, the client must still be prepared to allocate a secondary map blocks array at any time after map load. For example:
			* Client A goes to map XYZ
			* Server sends client A just a main blocks array for map XYZ
			* A minute later, client B places a block with ID 510 on map XYZ
			* Server then broadcasts this block change to all clients on map XYZ
			Since a secondary map blocks array was not sent during map load by the server, Client A must now allocate a secondary map blocks array.

			:<h4>Affect on other packets</h4>
			Several fields in some packets are expanded in size. These are:
			:{\| class="wikitable"
			\|- class="row0"
			! class="col0" \| Packet
			! class="col1" \| Field Name
			! class="col2" \| New Type
			! class="col3" \| Direction
			\|- class="row1"
			\| class="col0 centeralign" \| Set Block (0x05)
			\| class="col1 centeralign" \| Block type
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Client -> Server
			\|- class="row2"
			\| class="col0 centeralign" \| Set Block (0x06)
			\| class="col1 centeralign" \| Block Type
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row3"
			\| class="col0 centeralign" \| Position and Orientation (0x08)
			\| class="col1 centeralign" \| Player ID
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Client -> Server
			\|- class="row4"
			\| class="col0 centeralign" \| HoldThis (0x14)
			\| class="col1 centeralign" \| BlockToHold
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row5"
			\| class="col0 centeralign" \| SetBlockPermission (0x1C)
			\| class="col1 centeralign" \| BlockType
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row6"
			\| class="col0 centeralign" \| DefineBlock (0x23)
			\| class="col1 centeralign" \| BlockID
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row7"
			\| class="col0 centeralign" \| UndefineBlock (0x24)
			\| class="col1 centeralign" \| BlockID
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row8"
			\| class="col0 centeralign" \| DefineBlockExt (0x25)
			\| class="col1 centeralign" \| BlockID
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row9"
			\| class="col0 centeralign" \| BulkBlockUpdate (0x28)
			\| class="col1 centeralign" \| Blocks
			\| class="col2 centeralign" \| byte[512]
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row10"
			\| class="col0 centeralign" \| SetInventoryOrder (0x2C)
			\| class="col1 centeralign" \| Order
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row11"
			\| class="col0 centeralign" \| SetInventoryOrder (0x2C)
			\| class="col1 centeralign" \| Block ID
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row12"
			\| class="col0 centeralign" \| SetHotbar (0x2D)
			\| class="col1 centeralign" \| BlockID
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|}

			:<h5>Affect on BulkBlockUpdate</h5>
			Although the affect on most packets is straightforward, the changes to '''BulkBlockUpdate''' requires a more thorough explanation:
			* The first 256 bytes store the lower 8 bits of the ID for each of the 256 blocks.
			* The remaining 256 bytes store the higher 8 bits of the ID for each of the 256 blocks.
			:(Comments go here, please sign them)
			Most of this is copy/pasted from ExtendedBlocks v1, though BulkBlockUpdate has been updated to support the new blocks. This probably also needs the ability for more than 512 textures, but that's a seperate packet. [[User:Infernity\|Infernity]] ([[User talk:Infernity\|talk]]) 17:19, 15 June 2022 (UTC)

imported>DT: minor spelling error

2022-03-31T05:12:09Z

minor spelling error

← Older revision		Revision as of 05:12, 31 March 2022
Line 1,417:		Line 1,417:
	\|-		\|-
	! Total Size:		! Total Size:
	\| class="rightalign" colspan="4" \| 2 ~~byte~~		\| class="rightalign" colspan="4" \| 2 bytes
	\|}		\|}

	:(Comments go here, please sign them)		:(Comments go here, please sign them)

imported>DT: /* ScreenElements */

2022-03-31T01:14:05Z

ScreenElements

← Older revision		Revision as of 01:14, 31 March 2022
Line 1,337:		Line 1,337:
	\|-		\|-
	! Total Size:		! Total Size:
	\| class="rightalign" colspan="4" \| 15 bytes		\| class="rightalign" colspan="4" \| 16 bytes
	\|}		\|}

Line 1,395:		Line 1,395:
	\|-		\|-
	! Total Size:		! Total Size:
	\| class="rightalign" colspan="4" \| 71 bytes		\| class="rightalign" colspan="4" \| 72 bytes
	\|}		\|}

Line 1,417:		Line 1,417:
	\|-		\|-
	! Total Size:		! Total Size:
	\| class="rightalign" colspan="4" \| 1 byte		\| class="rightalign" colspan="4" \| 2 byte
	\|}		\|}

	:(Comments go here, please sign them)		:(Comments go here, please sign them)

imported>DT: /* ScreenElements */

2022-03-31T01:13:30Z

ScreenElements

← Older revision		Revision as of 01:13, 31 March 2022
Line 1,337:		Line 1,337:
	\|-		\|-
	! Total Size:		! Total Size:
	\| class="rightalign" colspan="4" \| 6 bytes		\| class="rightalign" colspan="4" \| 15 bytes
	\|}		\|}

Line 1,395:		Line 1,395:
	\|-		\|-
	! Total Size:		! Total Size:
	\| class="rightalign" colspan="4" \| 6 bytes		\| class="rightalign" colspan="4" \| 71 bytes
	\|}		\|}

Line 1,417:		Line 1,417:
	\|-		\|-
	! Total Size:		! Total Size:
	\| class="rightalign" colspan="4" \| ~~6 bytes~~		\| class="rightalign" colspan="4" \| 1 byte
	\|}		\|}

	:(Comments go here, please sign them)		:(Comments go here, please sign them)

← Older revision		Revision as of 21:15, 5 July 2023
Line 1,538:		Line 1,538:
	\| class="col0 centeralign" rowspan="3" \| 0x0d		\| class="col0 centeralign" rowspan="3" \| 0x0d
	(13)		(13)
			\| class="col1 centeralign" \| Position
			\| class="col2 centeralign" \| byte
			\| class="col3 centeralign" \| 0
			\| class="col4 centeralign" \| The position of the message. 0 is after the last message, 1 is between the last and the 2nd last message, 2 is between the 2nd last and the 3nd last message, etc. Position of 255 means the message should not be shown and be concatenated with the next message.
			\|- class="row2"
	\| class="col1 centeralign" \| Message		\| class="col1 centeralign" \| Message
	\| class="col2 centeralign" \| string		\| class="col2 centeralign" \| string
	\| class="col3 centeralign" \| &70Rainb0wSkeppy: &f0hi		\| class="col3 centeralign" \| &70Rainb0wSkeppy: &f0hi
	\| class="col4 centeralign" \| The message to be sent		\| class="col4 centeralign" \| The message to be sent
	~~\|- class="row2"~~
	~~\| class="col1 centeralign" \| Position~~
	~~\| class="col2 centeralign" \| byte~~
	~~\| class="col3 centeralign" \| 0~~
	\| class="col4 centeralign" \| The position of the message. 0 is after the last message, 1 is between the last and the 2nd last message, 2 is between the 2nd last and the 3nd last message, etc. Position of 255 means the message should not be shown and be concatenated with the next message.
	\|- class="row3"		\|- class="row3"
	! class="col0" \| Total Size:		! class="col0" \| Total Size:

← Older revision		Revision as of 22:43, 20 June 2023
Line 1,519:		Line 1,519:
	:(Comments go here, please sign them)		:(Comments go here, please sign them)
	Most of this is copy/pasted from ExtendedBlocks v1, though BulkBlockUpdate has been updated to support the new blocks. This probably also needs the ability for more than 512 textures, but that's a seperate packet. Also maybe a packet to say how many blocks server/client supports? Also also, feel free to edit this; just sign on the top too. [[User:Infernity\|Infernity]] ([[User talk:Infernity\|talk]]) 17:19, 15 June 2022 (UTC)		Most of this is copy/pasted from ExtendedBlocks v1, though BulkBlockUpdate has been updated to support the new blocks. This probably also needs the ability for more than 512 textures, but that's a seperate packet. Also maybe a packet to say how many blocks server/client supports? Also also, feel free to edit this; just sign on the top too. [[User:Infernity\|Infernity]] ([[User talk:Infernity\|talk]]) 17:19, 15 June 2022 (UTC)

			===ExtServerMessages===
			:Proposed by [[User:Rainb0wSkeppy\|Rainb0wSkeppy]] ([[User talk:Rainb0wSkeppy\|talk]]) 22:43, 20 June 2023 (UTC)
			:Allows the server to remove, insert and replace messages, set the background and foreground color of the messages, and send messages longer then 64 characters
			:'''Motivation''': To let the server highlight messages to make them stand out, send longer messages and remove messages (eg. to allow a moderator to delete messages after they have been sent) (and probably a lot of other stuff)
			:'''Client Behavior''': The client must read 2 characters after the &, the first one is the foreground and the second one is the background, When the server sends a message, the client inserts in the correct place, When the Position field is 0xff the client should not send a message until the Position field isn't 0xff, then concatenate the messages, When the server sends a DeleteMessage packet, it deletes the specified message
			:'''Server Behavior''': The server may send messages with the Position field and send DeleteMessage packets
			:<h4>Message packet</h4>
			:''Server to client''
			:{\| class="wikitable"
			\|- class="row0"
			! class="col0" \| Packet ID
			! class="col1" \| Field Name
			! class="col2" \| Field Type
			! class="col3" \| Example
			! class="col4" \| Notes
			\|- class="row1"
			\| class="col0 centeralign" rowspan="3" \| 0x0d
			(13)
			\| class="col1 centeralign" \| Message
			\| class="col2 centeralign" \| string
			\| class="col3 centeralign" \| &70Rainb0wSkeppy: &f0hi
			\| class="col4 centeralign" \| The message to be sent
			\|- class="row2"
			\| class="col1 centeralign" \| Position
			\| class="col2 centeralign" \| byte
			\| class="col3 centeralign" \| 0
			\| class="col4 centeralign" \| The position of the message. 0 is after the last message, 1 is between the last and the 2nd last message, 2 is between the 2nd last and the 3nd last message, etc. Position of 255 means the message should not be shown and be concatenated with the next message.
			\|- class="row3"
			! class="col0" \| Total Size:
			\| class="col1 rightalign" colspan="4" \| 66 bytes
			\|}
			:<h4>DeleteMessage packet</h4>
			:''Server to client''
			:{\| class="wikitable"
			\|- class="row0"
			! class="col0" \| Packet ID
			! class="col1" \| Field Name
			! class="col2" \| Field Type
			! class="col3" \| Example
			! class="col4" \| Notes
			\|- class="row1"
			\| class="col0 centeralign" rowspan="3" \| 0x??
			(??)
			\| class="col1 centeralign" \| Position
			\| class="col2 centeralign" \| byte
			\| class="col3 centeralign" \| 0
			\| class="col4 centeralign" \| The position of the message. 0 is the last message, 1 is the 2nd last message, 2 is the 3nd last message, etc.
			\|- class="row3"
			! class="col0" \| Total Size:
			\| class="col1 rightalign" colspan="4" \| 2 bytes
			\|}

			:(Comments go here, please sign them)

← Older revision		Revision as of 17:19, 15 June 2022
Line 1,421:		Line 1,421:

	:(Comments go here, please sign them)		:(Comments go here, please sign them)


			===ExtendedBlocks v2===
			:Proposed by [[User:Infernity\|Infernity]] ([[User talk:Infernity\|talk]]) 17:19, 15 June 2022 (UTC)
			:Allows using more than 768 blocks.
			:'''Motivation''': Allows for ever-more-detailed maps by sending up to 65,536 blocks.
			:'''Client Behavior''': Clients must adjust how they read the map as described in the '''Affect on map sending''' section. Clients must also adjust how they read and write several fields of the packets described in the '''Affect on other packets''' section. When a client detects that the secondary map blocks array is used, it must switch from accessing blocks via <code>map.blocks[index]</code> to <code>map1.blocks[index] \| (map2.blocks[index] << 8)</code> instead.
			:'''Server Behavior''': Servers must adjust how they write the map as described in the '''Affect on map sending''' section. Servers must also adjust how they read and write several fields of the packets described in the '''Affect on other packets''' section. Ideally, servers should avoid sending a secondary map blocks array when possible to minimise client memory usage.

			:<h4>Affect on map sending</h4>
			Essentially, instead of '''LevelDataChunk''' packets just being used to send the compressed form of the map blocks array, it is repurposed to send both the compressed form of the 'main' map blocks array and optionally a secondary map blocks array.
			To accomplish this, the '''Percent Complete''' field in the '''LevelDataChunk''' packet is repurposed. A value of ''0'' indicates that this LevelDataChunk packet contains part of the compressed data for the 'main' map blocks array, while a value of ''1'' indicates this LevelDataChunk packet contains part of the compressed data for the optional secondary map blocks array.

			The client and server should treat the '''LevelDataChunk''' packets used for the 'main' map blocks array as completely separate from the secondary map blocks array, i.e. the 'main' map blocks array should be compressed and decompressed completely independently of the optional secondary map blocks array.

			'''Note:''' Even if the server only sends a 'main' map blocks array, the client must still be prepared to allocate a secondary map blocks array at any time after map load. For example:
			* Client A goes to map XYZ
			* Server sends client A just a main blocks array for map XYZ
			* A minute later, client B places a block with ID 510 on map XYZ
			* Server then broadcasts this block change to all clients on map XYZ
			Since a secondary map blocks array was not sent during map load by the server, Client A must now allocate a secondary map blocks array.

			:<h4>Affect on other packets</h4>
			Several fields in some packets are expanded in size. These are:
			:{\| class="wikitable"
			\|- class="row0"
			! class="col0" \| Packet
			! class="col1" \| Field Name
			! class="col2" \| New Type
			! class="col3" \| Direction
			\|- class="row1"
			\| class="col0 centeralign" \| Set Block (0x05)
			\| class="col1 centeralign" \| Block type
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Client -> Server
			\|- class="row2"
			\| class="col0 centeralign" \| Set Block (0x06)
			\| class="col1 centeralign" \| Block Type
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row3"
			\| class="col0 centeralign" \| Position and Orientation (0x08)
			\| class="col1 centeralign" \| Player ID
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Client -> Server
			\|- class="row4"
			\| class="col0 centeralign" \| HoldThis (0x14)
			\| class="col1 centeralign" \| BlockToHold
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row5"
			\| class="col0 centeralign" \| SetBlockPermission (0x1C)
			\| class="col1 centeralign" \| BlockType
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row6"
			\| class="col0 centeralign" \| DefineBlock (0x23)
			\| class="col1 centeralign" \| BlockID
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row7"
			\| class="col0 centeralign" \| UndefineBlock (0x24)
			\| class="col1 centeralign" \| BlockID
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row8"
			\| class="col0 centeralign" \| DefineBlockExt (0x25)
			\| class="col1 centeralign" \| BlockID
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row9"
			\| class="col0 centeralign" \| BulkBlockUpdate (0x28)
			\| class="col1 centeralign" \| Blocks
			\| class="col2 centeralign" \| byte[512]
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row10"
			\| class="col0 centeralign" \| SetInventoryOrder (0x2C)
			\| class="col1 centeralign" \| Order
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row11"
			\| class="col0 centeralign" \| SetInventoryOrder (0x2C)
			\| class="col1 centeralign" \| Block ID
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|- class="row12"
			\| class="col0 centeralign" \| SetHotbar (0x2D)
			\| class="col1 centeralign" \| BlockID
			\| class="col2 centeralign" \| short
			\| class="col3 centeralign" \| Server -> Client
			\|}

			:<h5>Affect on BulkBlockUpdate</h5>
			Although the affect on most packets is straightforward, the changes to '''BulkBlockUpdate''' requires a more thorough explanation:
			* The first 256 bytes store the lower 8 bits of the ID for each of the 256 blocks.
			* The remaining 256 bytes store the higher 8 bits of the ID for each of the 256 blocks.
			:(Comments go here, please sign them)
			Most of this is copy/pasted from ExtendedBlocks v1, though BulkBlockUpdate has been updated to support the new blocks. This probably also needs the ability for more than 512 textures, but that's a seperate packet. [[User:Infernity\|Infernity]] ([[User talk:Infernity\|talk]]) 17:19, 15 June 2022 (UTC)