I have seen a similar report, but that one did not specify the "entity" field, so I decided to report this separately. Here is the similar report: MC-307438
When using the "minecraft:entity_properties" condition in a predicate and setting the "entity" field to "interacting_entity" or "attacker", the predicate fails when it is ran by a "minecraft:interaction" entity.
Here is the predicate in question:
{
"condition": "minecraft:entity_properties",
"entity": "interacting_entity",
"predicate": {
"minecraft:entity_type": "minecraft:player"
}
}
And here is the command being run by the command block:
execute as @e[type=minecraft:interaction] run execute as @s at @s run execute if predicate <predicate name> run particle minecraft:flame ~ ~ ~ 0.2 0.2 0.2 0 1 forceLinked issues
Comments 3
I can confirm that I have interacted with the “minecraft:interaction“ entity. The “interaction.player“ and “interaction.timestamp“ data are present.
Thank you for your report!
After consideration, the issue is being closed as Invalid.
You have posted a feature request or a suggestion. This site is for bug reports only.
For suggestions, please visit The official Minecraft feedback site or visit the Minecraft Feedback Discord server.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
I believe this is intended because at the moment the command runs, there is no interacting entity. It’s only available at the moment an interaction causes a loot table to be invoked.