From 27f5fd51fca0ae6def68742a4ba8036d6489a8e4 Mon Sep 17 00:00:00 2001 From: IchHabeHunger54 <52419336+IchHabeHunger54@users.noreply.github.com> Date: Wed, 15 Nov 2023 12:47:07 +0100 Subject: [PATCH] Update docs/blocks/states.md Co-authored-by: ChampionAsh5357 --- docs/blocks/states.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/blocks/states.md b/docs/blocks/states.md index 2caeef703..5e190f748 100644 --- a/docs/blocks/states.md +++ b/docs/blocks/states.md @@ -44,7 +44,7 @@ Here, the rule of thumb is: **if you have a finite amount of states, use a block Blockstates and block entities can be used in conjunction with one another. For example, the chest uses blockstate properties for things like the direction, whether it is opened or not, or becoming a double chest is handled by blockstate properties, while storing the inventory or interacting with hoppers is handled by a block entity. -There is no definitive answer to the question "How many states are too much for a blockstate?", but the authors recommend that if you need more than 8-9 bits of data (i.e. more than a few hundred states), you should use a block entity instead. +There is no definitive answer to the question "How many states are too much for a blockstate?", but we recommend that if you need more than 8-9 bits of data (i.e. more than a few hundred states), you should use a block entity instead. Implementing Blockstates ------------------------