It seems that somewhere in the last Snapshots the /place feature command changed its behavior. I encountered it with the minecraft:flower_cherry feature. Before it would spread randomly around the postion of the executed command and could be used many blocks above blocks as well.
But now when you execute /place feature minecraft:flower_cherry it just places some on the exact position of the executed command and nothing else. It even overrides the block the command is executed in (for example with /execute at)
I know something did change with this kind of feature generation, especially with flowers, but the impact on /place doesn’t seem like it’s intended.
Hi!
Thank you for your report!
However, this issue is Working As Intended.
https://feedback.minecraft.net/hc/en-us/articles/44167381353869-Minecraft-Java-Edition-26-1-Pre-release-1
Flower Features
Features spawned from Bone Meal are no longer restricted to the flower feature type, and instead controlled by the #can_spawn_from_bone_meal Configured Feature Tag
The flower, flower_no_bonemeal, and random_patch feature types have been removed
Instead, patches can be expressed as a sequence of count and random_offset placement modifiers
Please note, that mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, Redstone, villagers, and animals may not work the same in current versions.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki