Add ability to programmatically create selectors #2194
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This isn't for creating new selector types (i.e.
@a
alternatives), this is simply for if you want a selector outside of commands. I chose to ditch theArgumentTypes
system because really that seemed to be a reimplementation of selectors and I'd prefer to sit on top of what Vanilla has.I did actually start trying to redo the ArgumentTypes system, but it was a rabbit hole. I'm open to doing so in the future, but for now, this should cover most (if not all) of the current options.
Also added
Range
utility. Might be useful in advancements because of the MinMaxBounds in the advancement package.