Snappy compression causes "Locating Server" hang with high block permutations

When running a Bedrock Dedicated Server with compression-algorithm=snappy in server.properties, clients hang indefinitely on "Locating Server" if the world has a high number of block permutations (~96,000). The server logs show the player as connected and spawned, but the client never finishes loading. This configuration worked without issues on previous BDS versions prior to 1.26.30.

Steps to reproduce:

1. Set up a BDS 1.26.31.1 server with multiple addons that register a large number of custom blocks (approximately 96,000 total block permutations)

2. Set compression-algorithm=snappy in server.properties (any compression-threshold value)

3. Start the server and attempt to connect from a client

4. Client hangs on "Locating Server" indefinitely

5. Server console shows "Player connected" and "Player Spawned" despite the client never loading

Expected result:
Client should connect and load into the world, as it did on BDS versions prior to 1.26.30 with the same configuration and addons.

Actual result:
Client hangs on "Locating Server." The server believes the player has spawned, but the client never receives or processes the block palette data. Switching to compression-algorithm=zlib immediately resolves the issue with no other changes. The same world loads fine as a local/singleplayer world with all addons active.

Additional notes:

• The server warning [Blocks] World with over 65536 block permutations may degrade performance. Current world has 96194 permutations. is displayed, but this is a performance warning, not a hard limit

• At ~93,761 permutations with snappy, the issue also occurs — it is not strictly tied to the 65,536 threshold

• compression-algorithm=zlib with compression-threshold=512 works reliably at 96,194 permutations

• Transport is raknet

• Same addons and permutation count worked on previous BDS releases with snappy