[SPIGOT-5772] Block .setBiome() and World.setBiome(x, y, z, biome) are broken Created: 11/Jun/20  Updated: 12/Jun/20  Resolved: 11/Jun/20

Status: Closed
Project: Spigot
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: tastybento Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: API, biomes

Attachments: File BiomePlugin-1.0.jar     PNG File Screen Shot 2020-06-10 at 8.09.59 PM.png    
Issue Links:
Cloners
clones SPIGOT-5556 Block .setBiome() and World.setBiome(... Resolved
Version: This server is running CraftBukkit version git-Spigot-a99063f-fad2494 (MC: 1.15.2) (Implementing API version 1.15.2-R0.1-SNAPSHOT)
Guidelines Read: Yes

 Description   

When using block.setBiome() or World.setBiome(x, y, z, biome) the blocks that are updated are far more than the expected 4x4 area based on the location specified.

I used the same code and JAR as in the cloned bug:

Block block = event.getClickedBlock();
Location loc = block.getLocation(); 
loc.setY(0); // Set Y to 0 so it appears/updates in-game
loc.getBlock().setBiome(Biome.JUNGLE);

I clicked the block and a large area of the chunk changes biome. For example, when clicking the gold block in the attached image, the biome changes for every dirt block shown. This was from just one setBiome call on the gold block.

The attached plugin is the same as the cloned Jira - if you right-click the ground with a stick it will change the biome to Jungle.

Is it vanilla operation now that the biome is indeterminate or randomized?



 Comments   
Comment by tastybento [ 12/Jun/20 ]

Okay, thanks! BTW, you guys are great! Thanks for your hard work.

Comment by Black Hole [ 11/Jun/20 ]

Biomes are stored for a 4*4*4 cube. Minecraft then blends those biomes together. So it's technically stored for that cube, but might appear larger depending on surrounding biomes.
There is nothing that could be done on the Spigot side. If you think you know a better solution to biome blending, please use the Mojang bug tracker.

Generated at Tue Apr 22 04:20:16 UTC 2025 using Jira 10.3.5#10030005-sha1:190c783f2bd6c69cd5accdb70f97e48812a78d14.