Remove GT Registry impl in favour of normal forge/mc registries

docs/content/Modpacks/Changes/v8.0.0.md

@@ -5,6 +5,66 @@ title: "Version 8.0.0"
 
 # Updating from `7.4.0` to `8.0.0`
 
+## Registration Changes
+
+GregTech content is now registered in standard forge/minecraft registries instead of using a custom registry implementation. 
+
+### For KJS
+
+- Find and replace `GTCEuStartupEvents.registry` with `StartupEvents.registry`
+- Register material icon types with `GTCEuStartupEvents.materialIconType`
+
+### For addons 
+
+**All content should now be registered via either your addon's registrate instance, or via a [deferred register](https://docs.minecraftforge.net/en/1.20.1/concepts/registries/#deferredregister).**
+
+The `GTCEuAPI.RegisterEvent` event has been removed, as content should now use registrate or deferred registers.
+
+#### Content registered via registrate.
+
+The following should be registered via registrate:
+- Materials - Use `REGISTRATE.material(String name)` to access the material builder.
+- Elements - Use `REGISTRATE.element(...)` to register an element.
+- Tag prefixes - Use the following methods:
+  - `REGISTRATE.tagPrefix(String name)`
+  - `REGISTRATE.tagPrefix(String name, boolean invertedName)`
+  - `REGISTRATE.oreTagPrefix(String name, TagKey<Block> miningToolTag)`
+- Material icon sets - Use the following methods:
+  - `REGISTRATE.materialIconSet(String id)`
+  - `REGISTRATE.materialIconSet(String id, MaterialIconSet parent)`
+  - `REGISTRATE.materialIconSet(String id, @Nullable MaterialIconSet parent, boolean isRoot)`
+- Recipe types - Use `REGISTRATE.recipeType(String name, String group, RecipeType<?>... proxyRecipes)`
+- Recipe categories - Use `REGISTRATE.recipeCategory(String categoryName, GTRecipeType recipeType)`
+- World gen layers - Use `REGISTRATE.simpleWorldGenLayer(...)`
+- Medical conditions - Use `REGISTRATE.medicalCondition(...)`
+
+#### Ore veins, bedrock ores and bedrock fluids
+
+TODO
+~~Ore veins, bedrock ores and bedrock fluids are  datapack content. They can be registered in JSON or KubeJS. (Datapack JSON can be generated with datagen, see `com.gregtechceu.gtceu.data.DataGenerators`)~~
+
+#### Other content
+
+All other content should be registered via deferred registers.
+Content that can be registered via registrate can also be registered via deferred registers, but registrate is recommended.
+
+An exmaple of using a deferred register is shown below.
+```java
+class AddonCovers {
+
+    private static final COVER_REGISTER = DeferredRegister.create(GTRegistries.Keys.COVER, ADDON_MOD_ID);
+
+    public static final RegistryObject<CoverDefinition> CUSTOM_COVER = COVER_REGISTER.create("addon_custom_cover", 
+        () -> new CoverDefinition(ADDON.id("addon_custom_cover"), AddonCustomCover::new))
+
+   // The init function should be called at some point during your mod's construction (e.g. in your main mod file or mod startup file)
+   public static void init(IEventBus modBus) {
+        COVER_REGISTER.register(modBus);
+   }
+}
+
+```
+
 ## New Data Save/Sync System
 
 A new system for saving and syncing object fields has been added. See [this page](../../Development/Data-Sync-System/Migrating-From-LDLib-SyncData.md) for migration instructions.
@@ -156,4 +216,6 @@ As a recipe-matching optimization, input handlers whose `getTotalContentAmount()
   - Calling the battery buffer constructor with the following args gives the same behaviour as a charger machine: `(info, tier, inventorySize, BatteryBufferMachine.AMPS_PER_BATTERY_CHARGER, 0)`
 - Refactored Jade provider code. Use the `MachineInfoProvider` class for jade providers for a specific machine type, and `MachineTraitProvider` for providers for a specific machine trait. 
 - `GTUtil.getMoltenFluid(Material)` has been moved to `Material.getHotFluid()`.
-- `ICopyable::copyConfig`'s `CompoundTag` argument should now be mutated by reference instead of a new one returned (and thus, the return type has been changed to `void`).
+- `ICopyable::copyConfig`'s `CompoundTag` argument should now be mutated by reference instead of a new one returned (and thus, the return type has been changed to `void`).
+- World gen layers now store their dimensions as `ResourceKey<Level>` rather than `ResourceLocation`
+- Dimension markers now store their dimension as a `ResourceKey<Level>` rather than `ResourceLocation`

docs/content/Modpacks/Examples/Custom-Recipe-Condition.md

@@ -15,41 +15,23 @@ They are registered using
 @Mod(ExampleMod.MOD_ID)
 public class ExampleMod {
 
-    // in 1.20.1
-    public static RecipeConditionType<ExampleCondition> EXAMPLE_CONDITION;
+    private static final DeferredRegister<RecipeConditionType<?>> RECIPE_CONDITION = DeferredRegister
+            .create(GTRegistries.Keys.RECIPE_CONDITION, ExampleMod.MOD_ID);
+
+    // On 1.21, the registry object has type DeferredHolder<RecipeConditionType<?>, RecipeConditionType<ExampleCondition>>
+    public static RegistryObject<RecipeConditionType<ExampleCondition>> EXAMPLE_CONDITION = RECIPE_CONDITION.register("example_condition", // (1)
+            () ->new RecipeConditionType<>(ExampleCondition::new, ExampleCondition.CODEC));
 
     public ExampleMod() {
         IEventBus modBus = FMLJavaModLoadingContext.get().getModEventBus();
         modBus.addGenericListener(RecipeConditionType.class, this::registerConditions);
+
+        // Register the deferred registry to the mod bus, so that the recipe condition is registered during registration.
+        RECIPE_CONDITION.register(modBus);
     }
-
-    public void registerConditions(GTCEuAPI.RegisterEvent<String, RecipeConditionType<?>> event) {
-        EXAMPLE_CONDITION = GTRegistries.RECIPE_CONDITIONS.register("example_condition", // (1)
-                new RecipeConditionType<>(ExampleCondition::new, ExampleCondition.CODEC));
-    }
-    // end 1.20.1
-
-    // in 1.21.1
-    public static final RecipeConditionType<ExampleCondition> EXAMPLE_CONDITION = GTRegistries.register(GTRegistries.RECIPE_CONDITIONS,
-            ResourceLocation.fromNamespaceAndPath(ExampleMod.MOD_ID, "example_condition"), // (2)
-            new RecipeConditionType<>(ExampleCondition::new, ExampleCondition.CODEC));
-
-    public ExampleMod(IEventBus modBus, FMLModContainer container) {
-        modBus.addListener(CommonInit::onRegister);
-        bus.addListener(RecipeConditionType.class, this::registerConditions);
-    }
-
-    public void registerConditions(GTCEuAPI.RegisterEvent<String, RecipeConditionType<?>> event) {
-        EXAMPLE_CONDITION = GTRegistries.RECIPE_CONDITIONS.register("example_condition",
-                new RecipeConditionType<>(ExampleCondition::new, ExampleCondition.CODEC));
-    }
-    // end 1.21.1
 }
 ```
 
-1. The 1.20.1 version doesn't require a namespace, so make sure you don't use the same ID as someone else!  
-2. You may use a helper method akin to `GTCEu.id` for creating the ResourceLocation, but you **must** use your own namespace for it.
-
 We will set up a condition that requires that the power buffer of the machine is above a certain Y level.
 ```java
 public class ExampleCondition extends RecipeCondition<ExampleCondition> {

docs/content/Modpacks/Examples/Example_Coil_Multiblock.md

@@ -13,7 +13,7 @@ Below is an example of a multiblock using the CoilWorkableElectricMultiblockMach
     // In order to use multiblock logic extending beyond the normal WorkableElectricMultiblockMachine, (This is the multiblock type used by default for kubejs) you need to load a class. Coil multiblocks such as the Electric Blast Furnace, Pyrolyse Oven, and the Cracker use this class.
     const CoilWorkableElectricMultiblockMachine = Java.loadClass("com.gregtechceu.gtceu.api.machine.multiblock.CoilWorkableElectricMultiblockMachine")
 
-    GTCEuStartupEvents.registry('gtceu:machine', event => {
+    StartupEvents.registry('gtceu:machine', event => {
         event.create("superheated_pyrolyzing_oven", "multiblock")
             .machine((holder) => new CoilWorkableElectricMultiblockMachine(holder))
             .rotationState(RotationState.NON_Y_AXIS)

docs/content/Modpacks/Examples/Example_Steam_Multiblock.md

@@ -15,7 +15,7 @@ Steam multiblocks such as the Steam Grinder and Steam Oven use this class.
     // In order to use multiblock logic extending beyond the default multiblock type for KJS (WorkableElectricMultiblockMachine), you need to load a class.
     const $SteamMulti = Java.loadClass('com.gregtechceu.gtceu.common.machine.multiblock.steam.SteamParallelMultiblockMachine');
 
-    GTCEuStartupEvents.registry('gtceu:machine', event => {
+    StartupEvents.registry('gtceu:machine', event => {
         event.create('large_steam_compressor', 'multiblock')
             .machine((holder) => new $SteamMulti(holder, 4))
             // The number in holder is the max amount of parallel it can use.

docs/content/Modpacks/Examples/Example_Turbine.md

@@ -13,7 +13,7 @@ Below is an example of a multiblock using the LargeTurbineMachine class for maki
     // In order to use multiblock logic extending beyond the normal WorkableElectricMultiblockMachine, (This is the multiblock type used by default for kubejs) you need to load a class. LargeTurbineMachines such as the gas, steam, and plasma turbines use this class.
     const $LargeTurbineMachine = Java.loadClass("com.gregtechceu.gtceu.common.machine.multiblock.generator.LargeTurbineMachine")
 
-    GTCEuStartupEvents.registry('gtceu:machine', event => {
+    StartupEvents.registry('gtceu:machine', event => {
         event.create('hyper_gas_turbine', 'multiblock')
             .machine((holder) => new $LargeTurbineMachine(holder, GTValues.LuV)) // The value shows one rotor holder tier above the recommended minimum rotor holder. The tier of rotor holder provides a boost based on the efficiency stat.
             .rotationState(RotationState.NON_Y_AXIS)

docs/content/Modpacks/Examples/Multiblocks/Example_Coil_Multiblock.md

@@ -13,7 +13,7 @@ Below is an example of a multiblock using the CoilWorkableElectricMultiblockMach
     // In order to use multiblock logic extending beyond the normal WorkableElectricMultiblockMachine, (This is the multiblock type used by default for kubejs) you need to load a class. Coil multiblocks such as the Electric Blast Furnace, Pyrolyse Oven, and the Cracker use this class.
     const CoilWorkableElectricMultiblockMachine = Java.loadClass("com.gregtechceu.gtceu.api.machine.multiblock.CoilWorkableElectricMultiblockMachine")
 
-    GTCEuStartupEvents.registry('gtceu:machine', event => {
+    StartupEvents.registry('gtceu:machine', event => {
         event.create("superheated_pyrolyzing_oven", "multiblock")
             .machine((holder) => new CoilWorkableElectricMultiblockMachine(holder))
             .rotationState(RotationState.NON_Y_AXIS)

docs/content/Modpacks/Examples/Multiblocks/Example_Steam_Multiblock.md

@@ -15,7 +15,7 @@ Steam multiblocks such as the Steam Grinder and Steam Oven use this class.
     // In order to use multiblock logic extending beyond the default multiblock type for KJS (WorkableElectricMultiblockMachine), you need to load a class.
     const $SteamMulti = Java.loadClass('com.gregtechceu.gtceu.common.machine.multiblock.steam.SteamParallelMultiblockMachine');
 
-    GTCEuStartupEvents.registry('gtceu:machine', event => {
+    StartupEvents.registry('gtceu:machine', event => {
         event.create('large_steam_compressor', 'multiblock')
             .machine((holder) => new $SteamMulti(holder, 4))
             // The number in holder is the max amount of parallel it can use.

docs/content/Modpacks/Examples/Multiblocks/Example_Turbine.md

@@ -13,7 +13,7 @@ Below is an example of a multiblock using the LargeTurbineMachine class for maki
     // In order to use multiblock logic extending beyond the normal WorkableElectricMultiblockMachine, (This is the multiblock type used by default for kubejs) you need to load a class. LargeTurbineMachines such as the gas, steam, and plasma turbines use this class.
     const $LargeTurbineMachine = Java.loadClass("com.gregtechceu.gtceu.common.machine.multiblock.generator.LargeTurbineMachine")
 
-    GTCEuStartupEvents.registry('gtceu:machine', event => {
+    StartupEvents.registry('gtceu:machine', event => {
         event.create('hyper_gas_turbine', 'multiblock')
             .machine((holder) => new $LargeTurbineMachine(holder, GTValues.LuV)) // The value shows one rotor holder tier above the recommended minimum rotor holder. The tier of rotor holder provides a boost based on the efficiency stat.
             .rotationState(RotationState.NON_Y_AXIS)

docs/content/Modpacks/Examples/Multiblocks/Greenhouse.md

@@ -10,7 +10,7 @@ title: "Greenhouse"
 
 === "JavaScript"
     ```js title="greenhouse_recipe_type.js"
-    GTCEuStartupEvents.registry('gtceu:recipe_type', event => {
+    StartupEvents.registry('gtceu:recipe_type', event => {
         event.create('greenhouse')
             .category('drack')
             .setEUIO('in')
@@ -35,7 +35,7 @@ title: "Greenhouse"
     const $RecipeLogic = Java.loadClass('com.gregtechceu.gtceu.api.machine.trait.RecipeLogic')
     const $List = Java.loadClass('java.util.List')
 
-    GTCEuStartupEvents.registry('gtceu:machine', event => {
+    StartupEvents.registry('gtceu:machine', event => {
         event.create('greenhouse', 'multiblock')
             .rotationState(RotationState.NON_Y_AXIS)
             .recipeType('greenhouse')

docs/content/Modpacks/Examples/Multiblocks/Ore-Processing-Plant.md

@@ -9,7 +9,7 @@ title: "Ore Processing Plant"
 
 === "JavaScript"
     ```js title="ore_processing_plant.js"
-    GTCEuStartupEvents.registry('gtceu:recipe_type', event => {
+    StartupEvents.registry('gtceu:recipe_type', event => {
         event.create('ore_processing_plant')
             .category('ore_processing_plant')
             .setEUIO('in')
@@ -30,7 +30,7 @@ title: "Ore Processing Plant"
 ## Multiblock
 === "JavaScript"
     ```js title="ore_processing_plant.js"
-    GTCEuStartupEvents.registry('gtceu:machine', event => {
+    StartupEvents.registry('gtceu:machine', event => {
         event.create('ore_processing_plant', 'multiblock')
             .rotationState(RotationState.NON_Y_AXIS)
             .recipeType('ore_processing_plant')

docs/content/Modpacks/Examples/Parallel-Hatch-Part.md

@@ -12,7 +12,7 @@ const $ParallelHatchPartMachine = Java.loadClass(
     "com.gregtechceu.gtceu.common.machine.multiblock.part.ParallelHatchPartMachine"
 ); // (1)
 
-GTCEuStartupEvents.registry("gtceu:machine", (event) => {
+StartupEvents.registry("gtceu:machine", (event) => {
   event
       .create("parallel_hatch", "custom") // (2)
       .tiers(GTValues.UHV, GTValues.UIV, GTValues.UEV, GTValues.UXV) // (3)

docs/content/Modpacks/Materials-and-Elements/01-Material-Creation.md

@@ -64,7 +64,7 @@ You can change the properties of the material by adding any combination of the f
 
 === "JavaScript"
     ```js title="ingot.js"
-    GTCEuStartupEvents.registry('gtceu:material', event => {
+    StartupEvents.registry('gtceu:material', event => {
         event.create('andesite_alloy')
             .ingot()
             .components('1x andesite', '1x iron')
@@ -76,8 +76,7 @@ You can change the properties of the material by adding any combination of the f
     ```java title="Ingot.java"
     public static Material ANDESITE_ALLOY;
     public static void register() {
-        ANDESITE_ALLOY = new Material.Builder(
-                your_mod_id.id("andesite_alloy"))
+        ANDESITE_ALLOY = REGISTRATE.material("andesite_alloy")
                 .ingot()
                 .components("1x andesite", "1x iron")
                 .color(0xFF0000).secondaryColor(0x840707).iconSet(GTMaterialIconSet.DULL)
@@ -90,7 +89,7 @@ You can change the properties of the material by adding any combination of the f
 
 === "JavaScript"
     ```js title="dust.js"
-    GTCEuStartupEvents.registry('gtceu:material', event => {
+    StartupEvents.registry('gtceu:material', event => {
         event.create('mysterious_dust')
             .dust() // The harvest level and burn time can be specified in the brackets. Example: `.dust(2, 4000)`
             .color(0x7D2DDB)
@@ -101,8 +100,7 @@ You can change the properties of the material by adding any combination of the f
     ```java title="Dust.java"
     public static Material MYSTERIOUS_DUST;
     public static void register() {
-        MYSTERIOUS_DUST = new Material.Builder(
-            your_mod_id.id("mysterious_dust"))
+        MYSTERIOUS_DUST = REGISTRATE.material("mysterious_dust")
             .dust() // The harvest level and burn time can be specified in the brackets. Example: `.dust(2, 4000)`
             .color(0x7D2DDB)
             .buildAndRegister();
@@ -113,7 +111,7 @@ You can change the properties of the material by adding any combination of the f
 
 === "JavaScript"
     ```js title="gem.js"
-    GTCEuStartupEvents.registry('gtceu:material', event => {
+    StartupEvents.registry('gtceu:material', event => {
         event.create('purple_coal')
             .gem(2, 4000) 
             .element(GTElements.C) 
@@ -127,8 +125,7 @@ You can change the properties of the material by adding any combination of the f
     ```java title="Gem.java"
     public static Material PURPLE_COAL;
     public static void register() {
-        PURPLE_COAL = new Material.Builder(
-            your_mod_id.id("purple_coal"))
+        PURPLE_COAL = REGISTRATE.material("purple_coal")
             .gem(2, 4000)
             .element(GTElements.C)
             .ore(2, 3) 
@@ -142,7 +139,7 @@ You can change the properties of the material by adding any combination of the f
 === "JavaScript"
     ```js title="fluid.js"
     // const $FluidBuilder = Java.loadClass('com.gregtechceu.gtceu.api.fluids.FluidBuilder'); Uncomment if you want to use the Fluid Builder.
-    GTCEuStartupEvents.registry('gtceu:material', event => {
+    StartupEvents.registry('gtceu:material', event => {
         event.create('mysterious_ooze')
           .fluid() // Or .liquid(Int Temperature)
           .color(0x500bbf)
@@ -153,8 +150,7 @@ You can change the properties of the material by adding any combination of the f
     ```java title="Fluid.java"
     public static Material MYSTERIOUS_OOZE;
     public static void register() {
-        MYSTERIOUS_OOZE = new Material.Builder(
-            your_mod_id.id("mysterious_ooze"))
+        MYSTERIOUS_OOZE = REGISTRATE.material("mysterious_ooze")
             .fluid() // Or .liquid(Int Temperature)
             .color(0x500bbf)
             .buildAndRegister();

docs/content/Modpacks/Materials-and-Elements/02-Element-Creation.md

@@ -10,7 +10,7 @@ title: Element Creation
 Elements are the base of GT materials. Registering an element WILL NOT add any items.
 
 ```js
-GTCEuStartupEvents.registry('gtceu:element', event => {
+StartupEvents.registry('gtceu:element', event => {
    event.create('test_element')
         .protons(27)
         .neutrons(177)
@@ -21,6 +21,15 @@ GTCEuStartupEvents.registry('gtceu:element', event => {
 })
 ```
 
+=== "Java"
+```java title="AddonElements.java"
+public static Element TEST_ELEMENT;
+public static void register() {
+    TEST_ELEMENT = REGISTRATE.element("test_element", 27, 177, -1, null, "test", false);
+}
+```
+
+
 1.  `.create(String name)` ->  The element name.
 2.  `.protons(int protons)` -> Proton Count. Use `-1` if it is an element that will not get a material.
 3.  `.neutrons(int neutrons)` -> Neutron Count. Use `-1` if it is an element that will not get a material

docs/content/Modpacks/Materials-and-Elements/Material-Flags.md

@@ -10,7 +10,7 @@ can influence how the material behaves, as well as which items are generated for
 
 === "Javascript"
     ```js
-    GTCEuStartupEvents.registry('gtceu:material', event => {
+    StartupEvents.registry('gtceu:material', event => {
         event.create('my_material')
             // ...
             .flags(GTMaterialFlags.FLAMMABLE)
@@ -20,8 +20,7 @@ can influence how the material behaves, as well as which items are generated for
     ```java
     public static Material MY_MATERIAL;
     public static void register() {
-       MY_MATERIAL = new Material.Builder(
-            your_mod_id.id('my_material'))
+       MY_MATERIAL = REGISTRATE.material('my_material')
             // ...
             .flags(GTMaterialFlags.FLAMMABLE)
             .buildAndRegister();

docs/content/Modpacks/Materials-and-Elements/Material-Icon-Sets.md

@@ -43,7 +43,7 @@ The following icon sets are available by default:
 Custom iconsets can be specified as well, using the `gtceu:matieral_icon_set` event:
 
 ```js title="custom_iconsets.js"
-GTCEuStartupEvents.registry('gtceu:material_icon_set', event => {
+StartupEvents.registry('gtceu:material_icon_set', event => {
     event.create('starry')
         .parent('shiny')
 })