Biome Modifiers - Revision history

Gamma02: /* Biome Modifier Types */

2023-08-28T23:22:26Z

Biome Modifier Types

Commoble: Add warning about adding feature with multiple biome modifiers to best practices

2022-09-04T17:43:12Z

Add warning about adding feature with multiple biome modifiers to best practices

TelepathicGrunt at 17:57, 24 August 2022

2022-08-24T17:57:09Z

SizableShrimp at 02:16, 16 August 2022

2022-08-16T02:16:58Z

SizableShrimp: /* Biome Modifier Types */

2022-08-13T20:40:08Z

Biome Modifier Types

Nyfaria: /* Add Features */ missing comma

2022-08-02T21:38:23Z

Add Features: missing comma

Nyfaria: /* Remove Features */ added missing comma

2022-08-02T21:36:36Z

Remove Features: added missing comma

Nyfaria: /* Add Spawns */ removed bad comma

2022-08-02T21:34:00Z

Add Spawns: removed bad comma

Commoble: Add summary

2022-06-15T23:53:30Z

Add summary

SameButDifferent: Fix typo in biome modifier path

2022-06-15T03:44:57Z

Fix typo in biome modifier path

@@ Line 72: / Line 72: @@
+     }
+   }
-</syntaxhighlight></biome>
+</syntaxhighlight>
 = Biome Modifier Serializers =

← Older revision		Revision as of 17:43, 4 September 2022
Line 227:		Line 227:

	* Avoid using biome modifiers to add vanilla placed features to biomes, as this may cause a feature cycle violation (the game will crash if two biomes have the same two features in their feature lists but in different orders). Placed features can be referenced in biome jsons or added via biome modifiers, but should not be used in both.		* Avoid using biome modifiers to add vanilla placed features to biomes, as this may cause a feature cycle violation (the game will crash if two biomes have the same two features in their feature lists but in different orders). Placed features can be referenced in biome jsons or added via biome modifiers, but should not be used in both.
		+	* Avoid adding the same placed feature with more than one biome modifier, as this can cause feature cycle violations.

@@ Line 5: / Line 5: @@
 * Modifying the climate of a biome
 * Modifying a biome's client effects, such as water color
 Creating and using biome modifiers involves up to three steps:
@@ Line 12: / Line 14: @@
 # Creating [[#Biome_Modifier_JSONs|biome modifier JSONs]] to define individual biome modifier instances; each json file provides a glob of data to your serializer to produce an instance of a biome modifier type. These can be [[#Datageneration|datagenerated]] if desired.
 =Biome Modifier Types=

@@ Line 58: / Line 58: @@
 </syntaxhighlight>
-We can also accept [[Holders]] or [[HolderSets]] for other [[Registration#Data_Driven_Entries|datapack registry elements]], such as PlacedFeatures, which allows our BiomeModifier to refer to those elements, which can then be defined in their own JSON files.
+We can also accept [[Holders]] or [[HolderSets|HolderSets]] for other [[Registration#Data_Driven_Entries|datapack registry elements]], such as PlacedFeatures, which allows our BiomeModifier to refer to those elements, which can then be defined in their own JSON files.
 <syntaxhighlight lang="java">
@@ Line 132: / Line 132: @@
    "biomes": "#minecraft:is_badlands",
    "feature": "yourmod:some_feature"
+}
 </syntaxhighlight>

@@ Line 14: / Line 14: @@
 Forge provides several [[#Builtin_Biome_Modifier_Types|builtin biome modifier types]], so some basic use cases such as adding features or mob spawns to biomes can be done without registering additional serializers.
-= Biome Modifier Types =
+=Biome Modifier Types=
 To define a new type of biome modifier, begin by implementing a new class that extends <code>BiomeModifier</code>. BiomeModifiers can usually be implemented as records, to reduce boilerplate.
@@ Line 45: / Line 44: @@
 </syntaxhighlight>
-Typically we also want to restrict biome modifiers to only apply to certain biomes. We can do that by accepting a HolderSet<Biome> in our constructor:
+Typically we also want to restrict biome modifiers to only apply to certain biomes. We can do that by accepting a HolderSet<biome> in our constructor:
 <syntaxhighlight lang="java">
@@ Line 59: / Line 58: @@
 </syntaxhighlight>
-We can also accept Holders or HolderSets for other [[Registration#Data_Driven_Entries|datapack registry elements]], such as PlacedFeatures, which allows our BiomeModifier to refer to those elements, which can then be defined in their own JSON files.
+We can also accept [[Holders]] or [[HolderSets]] for other [[Registration#Data_Driven_Entries|datapack registry elements]], such as PlacedFeatures, which allows our BiomeModifier to refer to those elements, which can then be defined in their own JSON files.
 <syntaxhighlight lang="java">
@@ Line 72: / Line 71: @@
+     }
+   }
-</syntaxhighlight>
+</syntaxhighlight></biome>
 = Biome Modifier Serializers =

@@ Line 175: / Line 175: @@
+{
    "type": "forge:add_features", // required
-   "biomes": "#namespace:your_biome_tag" // accepts a biome id, [list of biome ids], or #namespace:biome_tag
+   "biomes": "#namespace:your_biome_tag", // accepts a biome id, [list of biome ids], or #namespace:biome_tag
    "features": "namespace:your_feature", // accepts a placed feature id, [list of placed feature ids], or #namespace:feature_tag
    "step": "underground_ores" // accepts a Decoration enum name

@@ Line 219: / Line 219: @@
      "weight": 100, // int, spawn weighting
      "minCount": 1, // int, minimum pack size
-     "maxCount": 4, // int, maximum pack size
+     "maxCount": 4 // int, maximum pack size
+   }
+}

@@ Line 222: / Line 222: @@
 <syntaxhighlight lang="json">
+{
-   "type": "forge:add_spawn", // Required
+   "type": "forge:remove_spawns", // Required
    "biomes": "#namespace:biome_tag", // Accepts a biome id, [list of biome ids], or #namespace:biome_tag
    "entity_types": "#namespace:entitytype_tag" // Accepts an entity type, list, or tag of entitytypes whose spawns are to be removed from the biomes