Template talk:Block state table

Sprites column
Instead of having the sprites column sometimes blank, what if there was no sprites column and you just added a sprite to the description when appropriate? &mdash;munin &middot;  &middot; 22:59, 6 September 2014 (UTC)


 * That would work, although be a little more code on the user's side. I'll try it to see how it looks. --KnightMiner  (t 03:23, 7 September 2014 (UTC)


 * Comparison view. You could really use blocklink and alike there if desired too. --KnightMiner  (t 03:36, 7 September 2014 (UTC)


 * Yep, I prefer no sprites column. BlockLink is easy, it shouldn't be a problem. &mdash;munin &middot; Grid_Book_and_Quill.png Grid_Stone_Pickaxe.png &middot; 05:39, 7 September 2014 (UTC)

Multiple values per row
Would it be okay to suggest/permit multiple values per row, where the values can be more-easily described with a single description? You would do it by only providing a single value-description pair, but provide multiple values in the value part (delineating by BR probably). I think that would make some state fields easier to discuss as a whole, rather than being limited to discussing each individual value separately. For example:

Of course you can still have separate lines for each value where it makes sense (like ). &mdash;munin &middot;  &middot; 23:39, 7 September 2014 (UTC)


 * For redstone dust and maybe others, it may even make sense to put multiple fields in a single row, rather than repeat the same information multiple times:


 * {| class="wikitable"

! Name ! Value ! Description ! rowspan=3 | !
 * + Redstone Dust
 * || Not configured to point in this direction.
 * || Configured to point in this direction.
 * || Configured to point in this direction, linking diagonally vertically.
 * || Configured to point in this direction, linking diagonally vertically.
 * || Configured to point in this direction, linking diagonally vertically.
 * 0 to 15
 * Redstone power level.
 * }
 * &mdash;munin &middot; Grid_Book_and_Quill.png Grid_Stone_Pickaxe.png &middot; 00:08, 8 September 2014 (UTC)

State field types
Is there a way to determine a state field's type (string, byte, etc.) from the F3 screen, or is it just an educated guess (true/false and numeric values below 256 are bytes, white text is string, etc.) or you have to look at the code? &mdash;munin &middot;  &middot; 23:57, 7 September 2014 (UTC)