minecraft:on_player_placing |
does nothing when a player places down an experimental block
Yes I have exp toggles on, here is example block code:
{
"format_version": "1.16.100",
"minecraft:block": {
"description": {
"identifier": "5fs:example",
"register_to_creative_menu": true,
"category": "Nature"
},
"components": {
"minecraft:geometry": "geometry.example",
"minecraft:entity_collision": true,
"minecraft:block_light_absorption": 0,
"minecraft:destroy_time": 99999,
"minecraft:explosion_resistance": 100,
"minecraft:loot": "loot_tables/empty.json",
"minecraft:map_color": "#ffffff",
"minecraft:material_instances": {
"*": {
"texture": "example",
"render_method": "alpha_test"
}
},
"minecraft:ticking": { // THIS WORKS
"looping": true,
"range": [30, 60],
"on_tick": {
"event": "will_replace",
"target": "self"
}
},
"minecraft:on_player_placing": { // THIS DOES NOT WORK
"event": "player_placed"
}
},
"events": {
"will_replace": { // THIS PART WORKS
"set_block_at_pos": {
"block_type": "5fs:example1",
"block_offset": [0, 1, 0]
}
},
"player_placed": { // THIS PART DOES NOT WORK
"run_command": {
"command": ["function example"]
}
}
}
}
}
Comments 3
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
Just got off of some extensive testing and ran across this ticket... run_command WILL NOT work in on_player_placing period.
In fact there are other issues as to the order of processing in the events and the fact that it will do a few of the sequences in on_player_placing... cut over to on_placed events, do them several times in alphabetical order (never mind the order I put them in) and then come back to do the rest of on_player_placing...
Another problem it has, you can set a property but not access the new value within the scope of the event.... yeah, it is all kinds of screwed up and I made a test to prove it, in order to figure out what I need to do to get around it not doing things in the order I put then in.
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response
Could you please provide more details or/and media files. As such we have no repro of this issue.
Also, did this issue happened more than once?
Also, just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki