Block State Properties Multiply Variants
Each independent block-state property multiplies the number of possible states, so adding a seemingly small property can cause large state tables, model or resource coverage gaps, or loader-specific limits. Before adding one, estimate the Cartesian product of property values and ask whether the distinction belongs in block state at all; when failures appear, inspect the declared property domains and identify which combination is missing or rejected. Limits and exact failure behavior can vary by Minecraft version, loader, and mappings.
Every state combination needs coverage in the blockstate file, either as a
variantsentry or amultipartcase. A new property left out of that file renders missing models for the new states. Got a different fix? Post it in the comments.