Skip to content

Comments

fix: don't inflate/decompress if compressionThreshold is negative#1373

Closed
cxvqo wants to merge 1 commit intoPrismarineJS:masterfrom
cxvqo:master
Closed

fix: don't inflate/decompress if compressionThreshold is negative#1373
cxvqo wants to merge 1 commit intoPrismarineJS:masterfrom
cxvqo:master

Conversation

@cxvqo
Copy link

@cxvqo cxvqo commented Feb 12, 2025

follows the notchian client better as if the compressionThreshold is negative, it means that the packets are uncompressed, and it should treat them accordingly

If compression is enabled, all following packets are encoded in the compressed packet format. Negative values will disable compression, meaning the packet format should remain in the uncompressed packet format. However, this packet is entirely optional, and if not sent, compression will also not be enabled (the notchian server does not send the packet when compression is disabled).
@extremeheat
Copy link
Member

Is this the case on all versions 1.8+?

@cxvqo
Copy link
Author

cxvqo commented Feb 12, 2025

yes

@cxvqo cxvqo closed this Feb 12, 2025
@cxvqo cxvqo reopened this Feb 12, 2025
@cxvqo cxvqo closed this Apr 11, 2025
@extremeheat
Copy link
Member

Why close?

@cxvqo
Copy link
Author

cxvqo commented Apr 14, 2025

Why close?

Issue with my implementation of it. (I think)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants