Feature Placement Modifier Reference

One of the most frequent frustrations for Minecraft world creators is when their meticulously designed custom trees or ore veins refuse to appear where they should, or worse, generate in absurd quantities. This often stems from a misunderstanding of Minecraft’s powerful yet intricate “Feature Placement Modifier” system. This sophisticated framework is the unseen architect behind the natural elements of your Minecraft world, dictating the generation and distribution of everything from individual plants to complex ore deposits.

The Unseen Architects of Your World

Minecraft’s dynamic world generation is a marvel, and at its core lies a system that precisely controls how natural elements are scattered across biomes. This system, centered around Feature Placement Modifiers, is absolutely crucial for anyone looking to customize their world generation, whether for data packs, modding, or simply understanding the game’s internal workings. It allows for granular control over the quantity, location, and conditions under which these features appear.

Features vs. Structures: A Fundamental Distinction

Before diving into the specifics of placement, it’s vital to differentiate between Features and Structures, as their generation rules vary significantly:

• Features: These are generally smaller elements, typically less than 16×16 blocks in size. They are designed to appear multiple times per chunk and require specific placement parameters to define their layout. Examples include individual trees, patches of grass, or small ore veins.
• Structures: In contrast, structures are larger, often spanning beyond a 16×16 block area. They can be located using the /locate command, are designed to adapt to terrain, and typically appear at most once per chunk. Examples include villages, strongholds, or ocean monuments. Our focus here, however, is on the smaller, more numerous “features.”

The Three-Part Harmony of Feature Generation

The generation of features in Minecraft is a meticulously organized process, broken down into three interconnected components:

• Configured Features: This is the blueprint of what a feature actually is. Defined in JSON files (e.g., in data//worldgen/configured_feature), a configured feature specifies the block arrangement, shape, and composition of the element. For instance, it might define a specific type of tree, or the pattern of an ore vein.
• Placed Features: Once a feature’s blueprint is established, a placed feature defines how and where it should be laid out in the world. This component combines a configured feature with a crucial list of placement modifiers. These modifiers are the core of our discussion, dictating frequency, Y-level, and spread. Placed features are also defined in JSON files (e.g., in data//worldgen/placed_feature).
• Biome Modifications: Finally, biome modifications tie placed features to specific biomes. This step defines which biomes a feature is allowed to generate in, ensuring that deserts don’t sprout oak trees and oceans aren’t filled with mountains. This is often handled through the Biome Modification API or similar systems for data packs, typically within feature_rules subfolders.

Unpacking Placement Modifiers: Your Control Panel

Placement modifiers are the granular controls that allow you to fine-tune every aspect of feature spawning. They are specified as a list within a placed feature’s definition, offering immense flexibility. Here are some of the most common and powerful modifiers:

• CountPlacement: This modifier controls the approximate number of feature instances that attempt to generate per chunk. A higher count means more attempts, leading to a denser distribution.
• BiomeFilter: An essential modifier, BiomeFilter explicitly determines which biomes or even dimensions a feature is permitted to spawn within. It works in conjunction with biome modifications to narrow down specific generation locations.
• InSquarePlacement: This modifier spreads features pseudo-randomly across the X and Z coordinates within a given chunk, ensuring a natural-looking, non-grid-aligned distribution.
• HeightRangePlacement: Critical for vertical positioning, this modifier specifies the exact range of Y-coordinates where a feature can spawn. It offers various options:
  • Uniform: Spreads features evenly across a defined Y-range.
  • Trapezoid: Concentrates features towards the middle of a Y-range, with fewer at the top and bottom.
  • BiasedToBottom: Favors spawning features at lower Y-levels within the specified range.
• Heightmap: Instead of a fixed Y-range, this modifier takes an input position and sets the Y-coordinate to one block above a specified heightmap type. Useful types include WORLD_SURFACE_WG (for the top solid block during world generation) and OCEAN_FLOOR_WG (for the highest solid block below water).
• RarityFilter: This modifier assigns a specific chance for a feature to generate. For example, a rarity of 10 would mean a 1-in-10 chance of spawning, making features more scarce.
• RandomOffset: Adds a random integer offset to the X and Z coordinates of a feature’s placement. This can help break up repetitive patterns and make generation look more organic.
• BlockPredicateFilter: This advanced modifier filters placement based on specific block conditions at the target location. For example, it could ensure a feature only spawns on dirt blocks, or only if a certain block is NOT present.

Crafting Your Own World: A Modder’s Blueprint

For those looking to implement custom features via data packs or mods, the process generally follows these steps:

1. Define Configured Features: Start by creating JSON files in data//worldgen/configured_feature. These files will detail the block structure and properties of your custom element. Think of this as designing the feature itself.
2. Define Placed Features: Next, create JSON files in data//worldgen/placed_feature. Each of these files will reference one of your configured features and, crucially, contain the list of placement modifiers that dictate its spawning behavior. This is where you specify frequency, height, and other conditions.
3. Integrate with Biomes: The final step involves telling Minecraft which biomes should host your placed features. This is typically done by defining feature rules in JSON files located within the feature_rules subfolder of your behavior packs, or through the Biome Modification API for more complex mods.
4. World Generation Passes: Understand that feature placement isn’t a single event. It occurs in multiple passes during world generation, such as first_pass, underground_pass, and surface_pass. This sequential generation order can sometimes influence how features interact with each other and the terrain.

Refining Your Creations: Expert Tips for Success

Optimizing your feature placement can save countless hours of troubleshooting. Here are some invaluable tips:

• Surface Structures: For features intended to spawn directly on the surface, like trees or surface rocks, utilize PlacedFeatures.WORLD_SURFACE_WG_HEIGHTMAP. This ensures correct placement on the highest solid block during world generation, preventing issues with features floating or being buried.
• Modularity is Key: Separating your configured features from your placed features offers significant benefits. It allows for easier modification of placement rules without altering the fundamental feature definition, and the same configured feature can be used in multiple placed features with different spawning conditions.
• Leverage Tools: Tools like bridge. can greatly assist in creating custom biome files and generating example files for reference, streamlining the development process.
• Testing with /placefeature: Minecraft 1.18.2+ snapshots introduced the invaluable /placefeature command. This command allows you to directly place a configured feature into the world at your current location, which is incredibly useful for rapid testing, visualization, and debugging your feature designs.

Navigating the Treacherous Terrain: Common Pitfalls

Even with a solid understanding, mistakes can happen. Being aware of common issues can help you diagnose problems quickly:

• Biome Specificity: Features are highly biome-dependent. If a feature isn’t appearing, double-check that it’s correctly configured for the biome you’re testing in. Attempting to place a feature in an unconfigured biome will simply result in failure.
• Incorrect Y-level Configuration: Misconfiguring HeightRangePlacement or other height-related modifiers is a frequent culprit for features generating too high (floating), too low (buried), or not at all if the range is too narrow or outside valid world limits.
• Mod Conflicts: In environments with multiple mods or data packs, feature placement errors can lead to server crashes or unexpected behavior, especially if mods are outdated or have conflicting world generation rules. Always check compatibility.
• y_spread Behavior: When combined with RandomOffset, the y_spread property can sometimes behave unexpectedly, particularly when you’re trying to place features below heightmaps. Careful testing is required to achieve the desired vertical distribution.
• Count Multiplier Overload: Be extremely mindful of CountPlacement modifiers. If not carefully configured, especially when combined with other frequency modifiers, they can multiply excessively, leading to an overwhelming number of features and significant performance issues. Always test your counts in a controlled environment.

Mastering the Feature Placement Modifier system unlocks an unparalleled level of control over Minecraft’s world generation. By understanding the interplay between configured features, placed features, and their modifiers, creators can craft truly unique and immersive environments, ensuring every tree, flower, and ore vein appears exactly where it’s meant to be.