-
-
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
scan tool fixes #719
scan tool fixes #719
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -553,6 +553,7 @@ else if (item instanceof BlockItem) | |
// place | ||
world.setBlock(here, Blocks.COBBLESTONE.defaultBlockState(), Block.UPDATE_CLIENTS); | ||
world.setBlock(here, newState, Constants.UPDATE_FLAG); | ||
world.getBlockEntity(here).applyComponentsFromItemStack(stackToPlace); | ||
targetBlock.setPlacedBy(world, here, newState, fakePlayer, stackToPlace); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this entire branch should honestly use just the Item#useOn(...), wonder if it is even safe these days to perform blockentity-ignore blockstate update, w/e for now There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It's not so easy to even use-on without messy blockstates =D |
||
} | ||
else if (item instanceof BucketItem) | ||
|
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.
shouldn't this always be the block?
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.
No, this is when the world block matches