Skip to content

bedrock: fix BiomeChunkGeneration structure for 1.26.20+ (proto 970+)#1205

Open
killcerr wants to merge 1 commit into
PrismarineJS:masterfrom
killcerr:master
Open

bedrock: fix BiomeChunkGeneration structure for 1.26.20+ (proto 970+)#1205
killcerr wants to merge 1 commit into
PrismarineJS:masterfrom
killcerr:master

Conversation

@killcerr

@killcerr killcerr commented Jul 11, 2026

Copy link
Copy Markdown

Update BiomeChunkGeneration to match the official protocol documentation for protocol version 970+. Surface-related fields (surface_materials, has_default_overworld_surface, has_swamp_surface, has_frozen_ocean_surface, has_end_surface, mesa_surface, capped_surface) have been moved into a new BiomeSurfaceBuilderData container type, and two new optional fields (surface_builder_data, subsurface_builder_data) have been added.

Also adds the new BiomeNoiseGradientSurfaceData type referenced by BiomeSurfaceBuilderData.

This fixes parsing of biome_definition_list (0x7a) packets which caused
'Server packet parse error' in bedrock-protocol relay mode.

Update BiomeChunkGeneration to match the official protocol documentation
for protocol version 970+. Surface-related fields (surface_materials,
has_default_overworld_surface, has_swamp_surface, has_frozen_ocean_surface,
has_end_surface, mesa_surface, capped_surface) have been moved into a new
BiomeSurfaceBuilderData container type, and two new optional fields
(surface_builder_data, subsurface_builder_data) have been added.

Also adds the new BiomeNoiseGradientSurfaceData type referenced by
BiomeSurfaceBuilderData.

This fixes parsing of biome_definition_list (0x7a) packets which caused
'Server packet parse error' in bedrock-protocol relay mode.
@extremeheat

Copy link
Copy Markdown
Member

Thanks, does this apply to any older versions or only 1.26.20+ ?

@killcerr

Copy link
Copy Markdown
Author

Thanks, does this apply to any older versions or only 1.26.20+ ?

I only confirmed the fix for 1.26.20+ (proto 970+). I haven’t had time to check older versions, and I also haven’t looked into exactly which protocol version the change was introduced. So I can’t say for sure whether it affects any earlier versions or not.

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