Skip to content

Commit

Permalink
Update docs/blocks/states.md
Browse files Browse the repository at this point in the history
Co-authored-by: ChampionAsh5357 <[email protected]>
  • Loading branch information
IchHabeHunger54 and ChampionAsh5357 authored Nov 15, 2023
1 parent a3090aa commit 27f5fd5
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/blocks/states.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
------------------------
Expand Down

1 comment on commit 27f5fd5

@neoforged-pages-deployments
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deploying with Cloudflare Pages

Name Result
Last commit: 27f5fd51fca0ae6def68742a4ba8036d6489a8e4
Status: ✅ Deploy successful!
Preview URL: https://2cdc8640.neoforged-docs-previews.pages.dev
PR Preview URL: https://pr-21.neoforged-docs-previews.pages.dev

Please sign in to comment.