When making a block with custom block states, attempting to use them in places such as commands or feature placement, an error will occur saying the custom block state is not a valid block state.

We also can't use any vanilla block states except for the direction block state.

Steps To Reproduce:

1. Download, install and start a new world with the supplied pack (experimental features and content log on)
2. When loading the world you'll get an error saying that the vanilla_state block was unable to register engine Block Property
   1. This block is trying to use the vanilla state 'minecraft:pillar_axis' but the only vanilla state that works is 'minecraft:direction'
3. Give yourself the grunt:direction_state block
4. Note that placing the block against any surface orients the block as if it were a log
5. Get another account in the world
6. The client will only see the block in two directions
   1. Up and Down as this doesn't rely on the minecraft:direction state
   2. One horizontal direction
      1. It's as if clients register the minecraft:direction block state equal to 0 no matter what state the block is actually in
7. Run the following commands

   /setblock ~ ~ ~ grunt:direction_state ["grunt:directional": 2]
   
   /setblock ~ ~ ~ grunt:direction_state ["directional": 2]
   
   /setblock ~ ~ ~ grunt:direction_state ["direction": 2]

1. Only the last command will work as custom block states can't be used by commands (with or without the identifier)

Expected Results:

• Custom block states can be used in commands and features and we can use more vanilla block states than just direction

Actual Behavior:

• Custom block states return errors when used outside of the block itself and using other vanilla block states makes the block fail to load