Eelt: /* Biome modifiers */

2023-01-31T02:07:03Z

Biome modifiers

← Older revision		Revision as of 22:07, 30 January 2023
Line 8:		Line 8:

	=== Biome modifiers ===		=== Biome modifiers ===
			{\| class="wikitable sortable" style="font-size: 1.15em; width=100%"
			! JSON entry
			! Whitelisted Biome tag
			! Blacklisted Biome tag
			! Triangular placement
			! Count
			! Bottom Anchor
			! Top Anchor
			! Rarity
			\|-
			\| <code>bauxite_ore_beach</code>
			\| <code>minecraft:is_beach</code>
			\| {{unknown\|None}}
			\| {{Yes}}
			\| 8
			\| 62
			\| 92
			\| 0
			\|-
			\| <code>bauxite_ore_mountain_high</code>
			\| <code>minecraft:is_mountain</code>
			\| <code>forge:is_snowy</code>
			\| {{Yes}}
			\| 9
			\| 208
			\| 256
			\| 0
			\|-
			\| <code>bauxite_ore_mountain_medium</code>
			\| <code>minecraft:is_mountain</code>
			\| <code>forge:is_snowy</code>
			\| {{Yes}}
			\| 6
			\| 144
			\| 196
			\| 0
			\|-
			\| <code>bauxite_ore_mountain_low</code>
			\| <code>minecraft:is_mountain</code>
			\| <code>forge:is_snowy</code>
			\| {{Yes}}
			\| 10
			\| 96
			\| 140
			\| 0
			\|-
			\| <code>bauxite_ore_overworld</code>
			\| <code>minecraft:is_overworld</code>
			\| {{Unknown\|None}}
			\| {{No}}
			\| 10
			\| 10
			\| 60
			\| 0
			\|-
			\| <code>cinnabar_ore_beach</code>
			\| <code>minecraft:is_beach</code>
			\| {{Unknown\|None}}
			\| {{Yes}}
			\| 2
			\| 62
			\| 92
			\| 1
			\|-
			\| <code>cinnabar_ore_mountains</code>
			\| <code>minecraft:is_mountain</code>
			\| {{Unknown\|None}}
			\| {{Yes}}
			\| 7
			\| 102
			\| 292
			\| 0
			\|-
			\| <code>cinnabar_ore_overworld</code>
			\| <code>minecraft:is_overworld</code>
			\| {{Unknown\|None}}
			\| {{No}}
			\| 9
			\| -64
			\| 320
			\| 0
			\|-
			\| <code>eighzo_ore_end</code>
			\| <code>minecraft:is_end</code>
			\| {{Unknown\|None}}
			\| {{No}}
			\| 3
			\| 10
			\| 36
			\| 0
			\|-
			\| <code>galena_ore_overworld</code>
			\| <code>minecraft:is_overworld</code>
			\| {{Unknown\|None}}
			\| {{No}}
			\| 3
			\| -48
			\| 12
			\| 0
			\|-
			\| <code>rutile_ore_overworld</code>
			\| <code>minecraft:is_overworld</code>
			\| {{Unknown\|None}}
			\| {{No}}
			\| 3
			\| -64
			\| -32
			\| 0
			\|-
			\| <code>saltpeter_ore_badlands</code>
			\| <code>minecraft:is_badlands</code>
			\| <code>minecraft:is_beach</code><br><code>forge:is_water</code>
			\| {{Yes}}
			\| 1
			\| 55
			\| 77
			\| 10
			\|-
			\| <code>saltpeter_ore_hot_sandy</code>
			\| <code>forge:is_hot</code><br><code>forge:is_sandy</code>
			\| <code>minecraft:is_beach</code><br><code>forge:is_water</code>
			\| {{No}}
			\| 4
			\| 55
			\| 320
			\| 0
			\|}

	=== Feature configuration ===		=== Feature configuration ===

Eelt: Created page with " == Technical background == Starting in 1.19.3 [https://gist.github.com/ChampionAsh5357/c21724bafbc630da2ed8899fe0c1d226#no-in-code-entries-in-dynamic-registries 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 fi..."

2023-01-31T00:25:56Z

Created page with " == Technical background == Starting in 1.19.3 [https://gist.github.com/ChampionAsh5357/c21724bafbc630da2ed8899fe0c1d226#no-in-code-entries-in-dynamic-registries 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 <code>ConfiguredFeature<?,?></code> or <code>PlacedFeature</code> objects anymore as a part of their codebase as it should be done data-driven in JSON fi..."

New page

== Technical background ==
Starting in 1.19.3 [https://gist.github.com/ChampionAsh5357/c21724bafbc630da2ed8899fe0c1d226#no-in-code-entries-in-dynamic-registries 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 <code>ConfiguredFeature<?,?></code> or <code>PlacedFeature</code> objects anymore as a part of their codebase as it should be done data-driven in JSON files.

Voluminous Energy has [https://github.com/MikeTheShadow/VoluminousEnergy/tree/1.19.3-exp/src/main/resources/data/voluminousenergy/worldgen/configured_feature moved] all it's configured features to JSON files under <code>/worldgen/configured_feature</code>. While placed features should similarly go under their respective folder in worldgen, Voluminous Energy exclusively relies on its <code>VEAndedMultiBiomeModifier</code> to dynamically generate <code>PlacedFeature</code> 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 ==

=== Biome modifiers ===

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

{| class="wikitable sortable" style="font-size: 1.15em; width=100%"
|+ Ore blob configuration data
|-
! JSON entry
! Targets
! Size
! Discard
|-
| <code>saltpeter_ore_blob</code>
| <code>forge:ore_bearing_ground/sand/colorless_sand</code><br><code>forge:ore_bearing_ground/sand/red_sand</code>
| 33
| rowspan="4" | 0
|-
| <code>bauxite_ore_blob</code>
| rowspan="4" | <code>minecraft:stone_ore_replaceables</code><br><code>minecraft:deepslate_ore_replaceables</code>
| 8
|-
| <code>cinnabar_ore_blob</code>
| rowspan="2" | 6
|-
| <code>galena_ore_blob</code>
|-
| <code>rutile_ore_blob</code>
| rowspan="2" | 4
| 0.75
|-
| <code>eighzo_ore_blob</code>
| <code>forge:ore_bearing_ground/end_stone</code>
| 0.5
|}

[[Category:Feature generation]]

Feature generation/1.19.3-0.3 - Revision history

Eelt: /* Biome modifiers */