Replies: 2 comments 2 replies
-
I wonder if the config part should then be implemented via a more complex system where you can create and switch between different "block state lists". Because changing string configs manually and often for stuff like this would be really awkward. Plus the new malilib configs would have had just a dropdown menu to select the block from for this config, instead of using string configs at all anymore. But if that dropdown would be the entire block state... it would look really messy in the dropdown due to the long block state string representation for some blocks. And it would still be pretty awkward to configure if it was just a "single config set" that you need to change every time. |
Beta Was this translation helpful? Give feedback.
-
Gosh darnit. I was looking up how to use blockstates in the blacklist, and all I found was my own post requesting the feature to be added from the last time I tried to do this (which I had forgotten about). xD |
Beta Was this translation helpful? Give feedback.
-
Hopefully a fairly small suggestion. I really hope there is a simple way to implement this:
Allow blockstates to be included in setting the allow and deny lists for blockTypeBreakRestriction.
Example: adding minecraft:nether_wart[age=2], would either allow or deny breaking specifically nether warts with an age of two.
This is the same syntax as used by minecraft, for example /setblock ~ ~ ~ minecraft:nether_wart[age=2].
And that's the whole suggestion. Mainly I see using this passively to help not break crops of the wrong age, but it could be used situationally for redstone components facing particular directions, or stairs, or whatever else where you want to break one component in a tiling, but not others of the same block type.
Beta Was this translation helpful? Give feedback.
All reactions