Contents (3)
Placing a Configured Feature Directly
Configured features (trees, ore blobs, vegetation patches) normally generate through biome placement, which makes them slow to test. /spawnfeature <feature_id> places a configured feature at your position immediately, so you can see exactly what it produces without flying around looking for natural examples. The feature ID is the namespaced identifier from your datapack, such as mymod:crystal_tree.
Controlling Placement Context
Many configured features behave differently depending on what block they are placed on and the surrounding space. Stand on the block type the feature expects — for example, place a tree feature on dirt or grass, not stone — because the feature's placement modifiers and valid-position rules still apply. If nothing appears, the feature may have failed its placement check rather than being broken. Try a flatter, clearer area and re-run the command.
Debugging Feature Output
If the feature spawns but looks wrong, the issue is usually in the configured feature's block state providers, height providers, or decorators. Adjust those values in the JSON, reload the datapack, and re-run /spawnfeature at the same spot to compare. Because the command bypasses biome and chunk-generation timing, you get instant feedback on each edit.
