Skip to content

1.12.2 Configuration Guide

Jump to bottom
Nick Young edited this page Aug 2, 2020 · 3 revisions

Table of Contents

Dimension-Specific Configurability

File structure

YUNG's Law supports the ability to use different configuration settings for each dimension. To do this, create a directory called YungsLaw in your Minecraft config directory. This directory will be created for you the first time you run the mod.

In this directory (e.g. .minecraft/config/YungsLaw) you create a separate version folder for each version of Minecraft. In each version folder you can add a config file for each dimension. A version folder will be created if you have run the mod at least once for that particular version of Minecraft. For example, if you have started Minecraft with YUNG's Law 1.12.2 at least once, you will have the 1.12.2 version directory already created for you.

Version folders follow the naming convention <MAJOR>_<MINOR>_<PATCH>, e.g. 1_12_2. Dimension-specific config files within a version folder follow the convention DIM<ID>_config.cfg. For example, to add a separate config for the Nether, the file must be named DIM-1_config.cfg.

Here's an example of what your directory might look like:

  Minecraft
config folder
     |
     |--- YungsLaw
     |        |--- 1_12_2
     |              +--- DIM-1_config.cfg
     |              +--- DIM1_config.cfg
     |
     |
     |--- other mod configs...

In this example, we have setup some configurations for Minecraft 1.12.2. We have custom dimension-specific configs for The Nether (-1) and The End (1).

Note that in order for a dimension-specific config file to actually be used, you must either have that dimension whitelisted or have Global Whitelisting enabled. Either of these can be done in the base config. The base config is found directly in the Minecraft config directory, with the name yungslaw-1_12_2.cfg.

Also note that placing a dimension-specific config file directly in the YungsLaw directory will not do anything. Dimension-specific configs MUST be placed in a version folder to have any effect.

Giving dimensions their own settings

The contents of each dimension's config file follow the exact same format as an ordinary config file for Forge. This means that you could copy the base config file (YungsLaw-1_12_2.cfg, located directly in the Minecraft config directory), rename it to DIM-1_config.cfg (for the Nether), and change the values to make it work for the Nether.

However, there are some important points to note. First, you do not need the comments (in neither the base config file nor any dimension-specific file), which are lines starting with #. They don't do anything except provide information. Second, the config file for a single dimension doesn't need to have every value specified. Any values not specified will be pulled from the base config. This is especially convenient, as it means you only need to specify the values you want to override.

An important note: the whitelisting settings (Enable Global Whitelisting and Whitelisted Dimension IDs) are only valid in the base config. These values cannot be overridden in dimension-specific configs.

Clone this wiki locally