Timed Config

Looking to automatically adjust and reload mod configurations at specific times for creating unique game modes, maps, or modpacks? Your search is over!

Timed Config (in combination with the Configured mod, which is a mandatory requirement) allows you to set and update settings for any mods according to your preferences at precisely specified times. All you need to do is configure the Timed Config settings, specifying the desired parameters, the time for their modification, and additional information for the tool to function correctly.

The mod works in both single-player games (edits any specified configuration files) and multiplayer mode (uses server settings to modify server configurations, client-side settings are ignored). However, testing in network games has been limited, so please report any issues in the comments.

Important Limitations

The mod DOES NOT GUARANTEE compatibility with all mods. It only works correctly with:

• Mods using .toml configuration files created through Forge
• Mods that don't require game/world restart to apply changes

We recommend first testing manual editing of the required mod settings through the Configured interface. If manual modification gives the desired result without reloading, then Timed Config will likely handle this task as well. Issues may arise with mods using special characters in configuration values.

Configuration Setup

Timed Config configuration may seem complex since most parameters are interpreted as string lists and processed later. Let's examine examples from the timedconfig-common.toml file:

["Configs for TimedConfig"]

# Number of triggers causing configuration changes. Set to 0 to disable the mod.
# Requires 1 trigger per time point for each configuration value change,
# even if you want to change multiple values simultaneously.
"Num Triggers" = 0 # Timed Config disabled
"Num Triggers" = 2 # Expects all lists below to contain 2 elements

# List of trigger activation times (in ticks, 0 - server start, 12000 - first night, etc.)
"Trigger Times" = [0, 24000] # First element corresponds to tick 0, second to tick 24000

# List of target configuration files for each trigger
"Trigger Config Files" = ["modconfigdir/modconfig.toml", "justthemodconfig.toml"]

# List of paths to modified configuration parameters
"Trigger Config Paths" = ["section.key", "section can have spaces.key can have spaces"]

# Main list of configuration values to set
"Trigger Config Values Literal" = ["0.0", "1.0"] # Two elements of type Double
"Trigger Config Values Literal" = ["Hey You", "You're Finally Awake"] # Two elements of type String
"Trigger Config Values Literal" = ["[0.0, 1.0]", "[2.0, 3.0]"] # Two elements of type List<Double>

# List of data types for value interpretation
"Trigger Config Values Datatype" = ["Double", "List<String>"] # examples

# Chat messages when triggers activate
"Trigger Message" = ["Value Changed!", ""] # First element sends a message, second does not

Remember: configuration files are overwritten with each trigger activation and DO NOT REVERT automatically to previous values. Always include default values in the trigger at time 0 if you want new worlds to start with standard settings.