Bedrock stack network id protocol fix for 1.16.220 to 1.20.10 #749
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
stack_id
field inStackRequestSlotInfo
andItem
needs to bevarint
and notzigzag32
.This causes a mismatch of the
stack_id
for an item stack between theinventory_content
,inventory_slot
,inventory_transaction
,item_stack_request
anditem_stack_response
packets.The problem can be seen by using the relay to print the
inventory_content
,item_stack_request
anditem_stack_response
packets; moving an item in the inventory, then comparing thestack_id
from the packetsCode references
The change was applied and tested for for all supported (and playable 1.16.220+) versions against vanilla bedrock servers.