Just Enough Dimensions

# Description Just Enough Dimensions (after this referred to as JED) is a mod that allows registering new custom dimensions to the game, **or** it can also be used to just tweak and configure some properties of existing dimensions. A few examples of tweaks that can be done to existing dimensions: * Use per-dimension World Borders (i.e. all dimensions would not be forced to have the same border as the overworld) * Use per-dimension difficulty(\*), Game Rules, day time, day length, world seed, sky and/or fog and/or cloud colors or the cloud render height \* Per-dimension difficulty is problematic in single player due to how some of the vanilla code works. But it should work no problem on a multiplayer server. As of version `1.6.0-dev.???` it's also possible to use JED to force certain settings for the world when the world is first being created. These include for example the WorldType of generator settings (for example making a superflat world or a void world \), or setting some Game Rules. (This did work before `1.6.0` as well, but not quite the same way and not as cleanly.) **Note:** Due to the way that dimension IDs (and WorldProviders) are handled in vanilla and Forge, and also due to the rendering related customization options, this mod is also required on the client side and not only on the server. # Config file locations All dimension registration and configuration is done via a simple(?) JSON config file located at `config/justenoughdimensions/dimensions.json`. There are also a number of "global" configs and toggle options to enable certain functionality, these are configured via the config file located at `config/justenoughdimensions/justenoughdimensions.cfg`, which will be referred to as the `JED main config` from now on. There is also support for per-world-save configs (to allow using different settings in different worlds within the same game instance or mod pack). In that case the config files would be inside the world, at `<worlddirectory>/justenoughdimensions/dimensions.json` and `<worlddirectory>/justenoughdimensions/justenoughdimensions.cfg`. If these files exist, and the per-world configs are enabled in the "global" JED main config (inside the normal config directory), then these ones take precedence over the normal configs inside the config directory. # Config file structure overview This section describes the rough overview of the config file structure. More detailed descriptions are further down. Tip: There are **a lot** of various different example configs on my pastebin, here: (https://pastebin.com/u/masa-). ## JED main config `justenoughdimensions.cfg` The JED main config has a few toggle options to enable certain functionality and overrides, some of which (like `B:enableOverrideWorldProvider=true`) are very important for many of the configuration options the mod has to actually work. Another important (or at least extremely useful) option is `B:enableLoggingInfo=true`. I would recommend you to **always enable this during mod pack development or JED config testing**. With this option enabled JED will be printing lots of (not super spammy though...) useful debug information to the game console/log, which will help you see what JED is doing (or not doing) and when and using what values. The main config also has the options to enable the per-world-save config functionality. These need to be enabled in the "global" JED main config for the mod to try to read the configs from the per-world location. ## Dimension config `dimensions.json` The `dimensions.json` config file is the (only) config file JED uses to know what to do with dimensions and how. Every dimension you want to register or configure in some way needs to be defined and described in this config. The main structure of this config is that there is just one JSON array of dimension definitions, called `dimensions`, plus the optional `config_version` object which is related to the per-world-save config handling, and which you can ignore and leave out in most cases. Each entry in the `dimensions` array should be a JSON object, which describes what to do for that given dimension. The most common and most important keys (config value names) inside each dimension entry are: * `dim` (int) - the (Forge) dimension ID this entry is fo * `dimensiontype` (object) - This defines what type of dimension **to register**. * `override` (boolean) - Enable overriding an existing dimension * `worldinfo` (object) - All the values stored in the `level.dat` file * `worldinfo_onetime` (object) - Same as `worldinfo`, but only applied once on the first load of the dimension * **Note:** In most cases you want to use `worldinfo_onetime` instead of `worldinfo`! * `jed` (object) - This object holds most JED-specific options See below for more detailed descriptions, and a full list of the rest of the options. # Detailed config descriptions <details> <summary>dimensions.json top l