[1.20.1] CastingEnvironment#getCasterPosition
#976
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Haven't reviewed this yet; just noting that we will not be merging large breaking changes until 1.21, and I think something like this counts. |
Author
Fair enough |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I had a slight issue with implementing Hexcasting compatibilty for Ambit and Range testing in that i couldnt cleanly get the casting position from
CastingEnvironmentThis PR's purpose is to add such a method and its base implementations to Hexcasting
This is a breaking change for those addons that make custom
CastingEnvironmentimplementations