Changes

Creating configs in Forge is fairly simple as Forge provides a ton of tools for configs. In addition, Forge will automatically update their values as the config files are edited and cache the values so you do not need to do so.

Creating configs in Forge is fairly simple as Forge provides a ton of tools for configs. In addition, Forge will automatically update their values as the config files are edited and cache the values so you do not need to do so.

To begin, create a new class file and add this:

To begin, create a new class file and add this:

```java

<syntaxhighlight lang="java>

    public static final ForgeConfigSpec GENERAL_SPEC;

public static final ForgeConfigSpec GENERAL_SPEC;

      

      

    static {

static {

        ForgeConfigSpec.Builder configBuilder = new ForgeConfigSpec.Builder();

    ForgeConfigSpec.Builder configBuilder = new ForgeConfigSpec.Builder();

        setupConfig(configBuilder);

    setupConfig(configBuilder);

        GENERAL_SPEC = configBuilder.build();

    GENERAL_SPEC = configBuilder.build();

    }

}

    private static void setupConfig(ForgeConfigSpec.Builder builder) {  

private static void setupConfig(ForgeConfigSpec.Builder builder) {  

    }

}

ForgeConfigSpec is what will ultimately hold all the data and info about how to make and read your config file. We will be registering this later. In the static block, this will create the builder for ForgeConfigSpec, pass it into setupConfig where we will add all the config entries we want, and then we build the final ForgeConfigSpec to store into GENERAL_SPEC.

ForgeConfigSpec is what will ultimately hold all the data and info about how to make and read your config file. We will be registering this later. In the static block, this will create the builder for ForgeConfigSpec, pass it into setupConfig where we will add all the config entries we want, and then we build the final ForgeConfigSpec to store into GENERAL_SPEC.

   

   

Now for creating config entries, lets add an integer config entry by creating a public static field for it and use builder.defineInRange to define it.  

Now for creating config entries, lets add an integer config entry by creating a public static field for it and use builder.defineInRange to define it.  

    private static void setupConfig(ForgeConfigSpec.Builder builder) {

        exampleIntConfigEntry = builder.defineInRange("example_int_config_entry", 5, 2, 50);

    }

 

private static void setupConfig(ForgeConfigSpec.Builder builder) {

    exampleIntConfigEntry = builder.defineInRange("example_int_config_entry", 5, 2, 50);

}

Here, setupConfig method will add to the builder that there should be a "example_int_config_entry" entry in the toml file, it has a default value of 5, and will only accept a user-entered value between 2 and 50. The it assigns that resultant ForgeConfigSpec.DoubleValue to the exampleIntConfigEntry field. Now the exampleIntConfigEntry field can be call with `.get()` anywhere in our code to get the current config value for that config entry at the time.

Here, setupConfig method will add to the builder that there should be a "example_int_config_entry" entry in the toml file, it has a default value of 5, and will only accept a user-entered value between 2 and 50. The it assigns that resultant ForgeConfigSpec.DoubleValue to the exampleIntConfigEntry field. Now the exampleIntConfigEntry field can be call with <code>.get()</code> anywhere in our code to get the current config value for that config entry at the time.

There are many kinds of config entries you can make. Some of the more commonly used ones are:

There are many kinds of config entries you can make. Some of the more commonly used ones are:

ForgeConfigSpec.IntValue - uses defineInRange

* ForgeConfigSpec.IntValue - uses defineInRange

ForgeConfigSpec.DoubleValue - uses defineInRange

* ForgeConfigSpec.DoubleValue - uses defineInRange

ForgeConfigSpec.LongValue - uses defineInRange

* ForgeConfigSpec.LongValue - uses defineInRange

ForgeConfigSpec.BooleanValue - uses define

* ForgeConfigSpec.BooleanValue - uses define

ForgeConfigSpec.ConfigValue<String> - uses define

* ForgeConfigSpec.ConfigValue<String> - uses define

ForgeConfigSpec.ConfigValue<List<? extends String>> - uses defineList (IMPORTANT, do not use .define for lists. Always .defineList)

* ForgeConfigSpec.ConfigValue<List<? extends String>> - uses defineList ('''IMPORTANT''', do not use .define for lists. Always .defineList)

As for the methods you can use for each of these config types:

As for the methods you can use for each of these config types:

.define - takes the default config value.

* .define - takes the default config value.

.defineInRange - takes the default, the minimum, and maximum config values in that order.

* .defineInRange - takes the default, the minimum, and maximum config values in that order.

.defineList - takes the default list to use and a validator to run on each list entry when the user tries to change the config file to make sure it is correctly edited by user.

* .defineList - takes the default list to use and a validator to run on each list entry when the user tries * to change the config file to make sure it is correctly edited by user.

Furthermore, you may attach a comment or translation key to your builder that is creating the config entries. And using `builder.push("...")` and `builder.pop();` before and after some config entries will put them into a category (comments can be attached to categories as well). Here is a large example of all this:

Furthermore, you may attach a comment or translation key to your builder that is creating the config entries. And using <code>builder.push("...")</code> and <code>builder.pop();</code> before and after some config entries will put them into a category (comments can be attached to categories as well). Here is a large example of all this:

```java

<syntaxhighlight lang="java">

    public static ForgeConfigSpec.IntValue exampleIntConfigEntry;

public static ForgeConfigSpec.IntValue exampleIntConfigEntry;

    public static ForgeConfigSpec.DoubleValue exampleDoubleConfigEntry;

public static ForgeConfigSpec.DoubleValue exampleDoubleConfigEntry;

    public static ForgeConfigSpec.ConfigValue<Double> exampleUnboundedDoubleConfigEntry;

public static ForgeConfigSpec.ConfigValue<Double> exampleUnboundedDoubleConfigEntry;

    public static ForgeConfigSpec.LongValue exampleLongConfigEntry;

public static ForgeConfigSpec.LongValue exampleLongConfigEntry;

    public static ForgeConfigSpec.BooleanValue exampleBooleanConfigEntry;

public static ForgeConfigSpec.BooleanValue exampleBooleanConfigEntry;

    public static ForgeConfigSpec.ConfigValue<String> exampleStringConfigEntry;

public static ForgeConfigSpec.ConfigValue<String> exampleStringConfigEntry;

    public static ForgeConfigSpec.ConfigValue<List<? extends String>> exampleStringListConfigEntry;

public static ForgeConfigSpec.ConfigValue<List<? extends String>> exampleStringListConfigEntry;

    private static void setupConfig(ForgeConfigSpec.Builder builder) {

private static void setupConfig(ForgeConfigSpec.Builder builder) {

        builder.comment(" This category holds configs that uses numbers.")

    builder.comment(" This category holds configs that uses numbers.")

        builder.push("Numeric Config Options");

    builder.push("Numeric Config Options");

          exampleIntConfigEntry = builder.defineInRange("example_int_config_entry", 5, 2, 50);

      exampleIntConfigEntry = builder.defineInRange("example_int_config_entry", 5, 2, 50);

          exampleDoubleConfigEntry = builder.defineInRange("example_double_config_entry", 10D, 0D, 100D);

      exampleDoubleConfigEntry = builder.defineInRange("example_double_config_entry", 10D, 0D, 100D);

          exampleUnboundedDoubleConfigEntry = builder

      exampleUnboundedDoubleConfigEntry = builder

            .comment("This comment will be attached to example_unbounded_double_config_entry in the config file.")

        .comment("This comment will be attached to example_unbounded_double_config_entry in the config file.")

            .define("example_unbounded_double_config_entry", 1000D);

        .define("example_unbounded_double_config_entry", 1000D);

          exampleLongConfigEntry = builder.defineInRange("example_long_config_entry", 4L, -900L, 900L);

      exampleLongConfigEntry = builder.defineInRange("example_long_config_entry", 4L, -900L, 900L);

        builder.pop();

    builder.pop();

        builder.comment(" This category holds configs that uses numbers.")

    builder.comment(" This category holds configs that uses numbers.")

        builder.push("String Config Options");

    builder.push("String Config Options");

          exampleStringConfigEntry = builder

      exampleStringConfigEntry = builder

            .comment("This config holds a single string.")

        .comment("This config holds a single string.")

            .define("example_string_config_entry", "player444");

        .define("example_string_config_entry", "player444");

          builder.comment(" This category will be nested inside the String Config Options category.")

      builder.comment(" This category will be nested inside the String Config Options category.")

          builder.push("Nested Category");

      builder.push("Nested Category");

            exampleStringListConfigEntry = builder

        exampleStringListConfigEntry = builder

              .comment("This config entry will hold a list of strings.")

          .comment("This config entry will hold a list of strings.")

              .defineList("example_string_list_config_entry", Arrays.asList("pie", "trains"), entry -> true);

          .defineList("example_string_list_config_entry", Arrays.asList("pie", "trains"), entry -> true);

          builder.pop();

      builder.pop();

        builder.pop();

    builder.pop();

    }

}

Now it is time to register your config file so that Forge can create and read the config file. Doing do, you simply call `ModLoadingContext.get().registerConfig` and pass in, the `ModConfig.Type`, the `GENERAL_SPEC` from your config file, and the name of the config file (make sure you include `.toml` as well. Like so:

Now it is time to register your config file so that Forge can create and read the config file. Doing do, you simply call <code>ModLoadingContext.get().registerConfig</code> and pass in, the <code>ModConfig.Type</code>, the <code>GENERAL_SPEC</code> from your config file, and the name of the config file (make sure you include <code>.toml</code> as well. Like so:

`ModLoadingContext.get().registerConfig(ModConfig.Type.COMMON, ModConfig.GENERAL_SPEC, "modconfig.toml");`

<code>ModLoadingContext.get().registerConfig(ModConfig.Type.COMMON, ModConfig.GENERAL_SPEC, "modconfig.toml");</code>

NOTE: Forge will only update the values of your config fields in code after the registry events are finished. Therefore, only attempt to read the config values after the registry events are completed. (FMLCommonSetupEvent and later is safe)

NOTE: Forge will only update the values of your config fields in code after the registry events are finished. Therefore, only attempt to read the config values after the registry events are completed. (FMLCommonSetupEvent and later is safe)

The ModConfig.Type determines where your config files goes and its behavior. While COMMON is generally used the most, the other config types do have specific uses. A simple summary is:

The ModConfig.Type determines where your config files goes and its behavior. While COMMON is generally used the most, the other config types do have specific uses. A simple summary is:

ModConfig.Type.COMMON - Exists in the config folder above the mods folder and will apply to all worlds created. (Works for both client and servers)

* ModConfig.Type.COMMON - Exists in the config folder above the mods folder and will apply to all worlds created. (Works for both client and servers)

ModConfig.Type.CLIENT - Same as COMMON except the config file is only ever loaded on the client. Never on server.

* ModConfig.Type.CLIENT - Same as COMMON except the config file is only ever loaded on the client. Never on server.

ModConfig.Type.SERVER - Exists only in a world's own config folder ona per-world basis. This is read on both server and on single player as well.  

* ModConfig.Type.SERVER - Exists only in a world's own config folder ona per-world basis. This is read on both server and on single player as well.  

 

<syntaxhighlight lang="java">

```java

FileUtils.getOrCreateDirectory(FMLPaths.CONFIGDIR.get().resolve("modid"), "modid");

FileUtils.getOrCreateDirectory(FMLPaths.CONFIGDIR.get().resolve("modid"), "modid");

ModLoadingContext.get().registerConfig(ModConfig.Type.COMMON, ModIdConfigs.GENERAL_SPEC, "modid/blocks.toml");

ModLoadingContext.get().registerConfig(ModConfig.Type.COMMON, ModIdConfigs.GENERAL_SPEC, "modid/blocks.toml");

ModLoadingContext.get().registerConfig(ModConfig.Type.COMMON, ModIdConfigs.GENERAL_SPEC, "modid/entities.toml");

ModLoadingContext.get().registerConfig(ModConfig.Type.COMMON, ModIdConfigs.GENERAL_SPEC, "modid/entities.toml");

Now your configs are setup, you know a decent chunk of how you can utilize Forge configs, and you are ready to go!

Now your configs are setup, you know a decent chunk of how you can utilize Forge configs, and you are ready to go!