-
-
Notifications
You must be signed in to change notification settings - Fork 340
[API-8] Add missing Living value accessors #2144
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
Conversation
| * {@link Keys#ACTIVE_ITEM} | ||
| * @return The active item, such as food being eaten | ||
| */ | ||
| default Value.Mutable<ItemStackSnapshot> activeItem() { |
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.
Can you give some guidance on how the Values in these interfaces should be returned to consumers?
Like, should they always be Value.Mutable? Just Value? Does it depend on what it is returning and what you can do with it in the game?
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 am preferring they're always Mutable from entities. It does make sense that they are reflective of their Key variables, but at the end of the day, the developer is likely to want to mutate the value and maybe offer it back, or present it to another entity after mutation.
55ce942 to
b7dbd5e
Compare
Adds value accessors for the following keys to
Living:ABSORPTIONACTIVE_ITEMEYE_HEIGHTEYE_POSITIONFALL_DISTANCEMAX_AIRREMAINING_AIRSTUCK_ARROWSWALKING_SPEED