From 8d5dff7d828247cc28e67289caa85ec1cd632578 Mon Sep 17 00:00:00 2001 From: gnembon Date: Sat, 20 Jun 2020 20:54:43 -0300 Subject: [PATCH] explanation of biome changes, fixes #334 --- docs/scarpet/api/BlocksAndWorldAccess.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/scarpet/api/BlocksAndWorldAccess.md b/docs/scarpet/api/BlocksAndWorldAccess.md index 6ef5f75b..14d2792d 100644 --- a/docs/scarpet/api/BlocksAndWorldAccess.md +++ b/docs/scarpet/api/BlocksAndWorldAccess.md @@ -143,6 +143,11 @@ markers for scarpet apps. `meeting` is the only one with increased max occupancy Changes the biome at that block position. if update is specified and false, then chunk will not be refreshed on the clients. Biome changes can only be send to clients with the entire data from the chunk. +Setting a biome is now (as of 1.16) dimension specific. In the overworld and the end changing the biome +is only effective if you set it at y=0, and affects the entire column of. In the nether - you have to use the +specific Y coordinate of the biome you want to change, and it affects roughly 4x4x4 area (give or take some random +noise). + ### `update(pos)` Causes a block update at position.