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

[1.16.5 Bug] Blocks placed by Reacharound Placing are not consider as player placing #5085

Open
GoldenTotem opened this issue Oct 30, 2024 · 0 comments

Comments

@GoldenTotem
Copy link

Minecraft 1.16.5 Forge 36.2.35 Quark r2.4-322

As the title, if you place blocks using "Reacharound Placing", those blocks will be considered as placed by system, instead of player.

There are some methods to prove this.

I. Install crafttwekaer and use this script.

CTEventManager.register<crafttweaker.api.event.block.MCBlockPlaceEvent>(event => {
    event.getEntity().getWorld().asServerWorld().server.executeCommand("say "+ event.getEntity().getName()+" has placed a block");
});

Every time you place a block, a message will be sent, but Reacharound Placing does not.

II. Open Statistics / Items, "Times used" shows how many blocks you have placed, but Reacharound Placing will not add this value.

What are the consequences of this.
This may cause incompatibility with other mods.
For example,

I. if players are not allow to place blocks in a certain structure. Reacharound Placing may help them bypass this restriction.

II. {CanPlaceOn} nbt will not work. Run command /give @s dirt{CanPlaceOn:[grass_block]}. This dirt can not be placed by Reacharound Placing in advanture mode although there is a grass block below.

III. Trigger minecraft:placed_block in advancement may not be fired.

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

No branches or pull requests

1 participant