I think an important tool for data packs would be the ability to add custom block states. Custom block states would not do anything by themselves (except show up on the f3 screen). If a player wanted to make a custom block state they would have to specify the following in a JSON file within the data pack
-The name of the state (most likely as the file name),
-The block(s) it applies to,
-The possible values for it,
-The default value for it.
If the player wanted to give it a model they would have to do that separately in a resource pack and if they wanted to give it purpose they would have to use functions.
If two data packs implement a block state with the same name I see two possible solutions, either the data pack loaded later would take precedence or block states would have their namespace as a prefix.
Please sign in to leave a comment.