Feature generation/1.19.3-0.3

Technical background

Starting in 1.19.3 dynamic registries are no longer conventionally done in code and must be done in JSON files (ignoring datagen). This means that mods shouldn't really have ConfiguredFeature<?,?> or PlacedFeature objects anymore as a part of their codebase as it should be done data-driven in JSON files.

Voluminous Energy has moved all it's configured features to JSON files under /worldgen/configured_feature. While placed features should similarly go under their respective folder in worldgen, Voluminous Energy exclusively relies on its VEAndedMultiBiomeModifier to dynamically generate PlacedFeature objects at runtime. Though, this may be considered bad practice since these placement objects aren't registered. Despite this, they still work when injected into biomes when Forge runs Biome Modifiers.

Ore blob features

Feature configuration

As mentioned in the technical background, configured features are now defined in JSON files.

Ore blob configuration data

JSON entry	Targets	Size	Discard
saltpeter_ore_blob	forge:ore_bearing_ground/sand/colorless_sand forge:ore_bearing_ground/sand/red_sand	33	0
bauxite_ore_blob	minecraft:stone_ore_replaceables minecraft:deepslate_ore_replaceables	8
cinnabar_ore_blob		6
galena_ore_blob
rutile_ore_blob		4	0.75
eighzo_ore_blob	forge:ore_bearing_ground/end_stone		0.5