-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow passing multiple BiomeTags at the same time for BiomeSelectors #3695
Conversation
Does creating a tag that references other tags not work for your use case? In most cases, |
You could do that but I feel like it's unnecessary and you'd need to make tags for every combo you do |
/** | ||
* {@return true if this biome is in any of the given {@link TagKey}s}. | ||
*/ | ||
default boolean hasTag(TagKey<Biome>... tags) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't sound obvious. I think we need to add anyTagMatch
, allTagMatch
and noneTagMatch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree I think something like this would be ideal here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
*To be clear: I'm suggesting the same thing as Stream::anyMatch
, Stream::allMatch
, Stream::noneMatch
Hmm, can't we just use |
We can, but we have convenient helper methods and the author suggests expanding it |
I'm unsure how useful this boilerplate code is, as pointed about above this is really easy to do in your own mod with |
I have run into situations where with ores for example I want to add them to more than one biomeTag biomes and have to make a separate entry, this solves that by allowing developers to pass in more than one.