You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
USB's levelconfig.yml contains an undocumented option called 'additionalBlocks', which adds additional blocks to the material type configured. It took me a while to understand the exact use case for this, but I've found one today.
WOOL used to be a single Material type with a custom score and diminishingReturns value. All colors would be counted as one single type. Since MC1.13, WOOL is separated into different item id's for each color. AdditionalBlocks makes it possible to group them all together, like:
The issue here is that USB uses the name of the main item (WHITE_WOOL in this case) in outputs like /is info, like:
Feature request: make it possible to configure a custom name for the item, e.g. "Colored Wool", in this case.
The text was updated successfully, but these errors were encountered:
I made small progress, block group name is being loaded from config file(hope I didn't overlook anything). As soon as I have more time, I'll finish it. master...matobodo:6-add-group-name
USB's levelconfig.yml contains an undocumented option called 'additionalBlocks', which adds additional blocks to the material type configured. It took me a while to understand the exact use case for this, but I've found one today.
WOOL used to be a single Material type with a custom score and diminishingReturns value. All colors would be counted as one single type. Since MC1.13, WOOL is separated into different item id's for each color. AdditionalBlocks makes it possible to group them all together, like:
The issue here is that USB uses the name of the main item (WHITE_WOOL in this case) in outputs like /is info, like:
Feature request: make it possible to configure a custom name for the item, e.g. "Colored Wool", in this case.
The text was updated successfully, but these errors were encountered: