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
Describe your suggestion...
the NBT rule in random_entities.properties has multiple variations (raw: | regex: | etc.) and one of those is range: which checks for an integer value in a list. The problem is, many useful NBT values are of the "float" type, which cannot be checked by "range:".
Usage example: with Random Mob Sizes "ScaleFactor" NBT value (which is a float), textures could be applied based on entity size.
Does another mod also do this?
No.
Does OptiFine do this?
No.
The text was updated successfully, but these errors were encountered:
Describe your suggestion...
the NBT rule in random_entities.properties has multiple variations (raw: | regex: | etc.) and one of those is range: which checks for an integer value in a list. The problem is, many useful NBT values are of the "float" type, which cannot be checked by "range:".
Usage example: with Random Mob Sizes "ScaleFactor" NBT value (which is a float), textures could be applied based on entity size.
Does another mod also do this?
No.
Does OptiFine do this?
No.
The text was updated successfully, but these errors were encountered: