Skip to content
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

Merged
merged 2 commits into from
Feb 8, 2025
Merged

scan tool fixes #719

merged 2 commits into from
Feb 8, 2025

Conversation

Raycoms
Copy link
Contributor

@Raycoms Raycoms commented Feb 8, 2025

Closes #
Closes #

Changes proposed in this pull request

  • Fix slab/domum handling and water handling and grass/dirt path handling and stairs handling

Testing

  • Yes I tested this before submitting it.
  • I also did a multiplayer test.

Review please

Copy link
Member

@Nightenom Nightenom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mergeable, just small questions not affecting approval

if (complete)
{
return Collections.singletonList(new ItemStack(blockState.getBlock()));
}
return new ArrayList<>();
Copy link
Member

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?

Copy link
Contributor Author

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

@@ -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);
Copy link
Member

Choose a reason for hiding this comment

The 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

Copy link
Contributor Author

Choose a reason for hiding this comment

The 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

@Raycoms Raycoms merged commit 98a9a16 into version/1.21 Feb 8, 2025
5 checks passed
@Raycoms Raycoms deleted the scantoolfixes branch February 8, 2025 20:56
Raycoms added a commit that referenced this pull request Feb 9, 2025
Fix slab/domum handling and water handling and grass/dirt path handling and stairs handling
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants