-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
Draft changes for itemHandler #699
Conversation
@Raycoms this might probably do, but i havent tested it properly, also i have done nothing towards to double chest and alike Also this should be accompanied by changed during placement/pre-placement traversals do we require exactly once the content of BE |
@@ -264,6 +265,7 @@ public static boolean isWater(final BlockState iBlockState) | |||
return iBlockState.getBlock() == Blocks.WATER; | |||
} | |||
|
|||
@Deprecated(forRemoval = true, since = "1.21") | |||
private static Item getItem(final BlockState blockState) |
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.
we will still need solutions for this kind of things, don't just deprecate it =D
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's in blockui for two version already
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.
Should otherwise be okay, was did tested?
(Please don't deprecate the others for now)
@@ -478,7 +478,7 @@ private void updateResources() | |||
boolean handled = false; | |||
for (final IPlacementHandler handler : PlacementHandlers.handlers) | |||
{ | |||
if (handler.canHandle(world, BlockPos.ZERO, blockState)) |
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.
This was weird, especially no need to load world at zero during compute resources step
Changes proposed in this pull request
Testing
Review please