Chain

Config chains explains how a chain loads. These report what happened.

config_chain#

Every openmw.cfg the loader tried, in the order it tried them: the root first, then depth first through the config= entries, as OpenMW walks them. Configs a replace=config later dropped are still listed, because they were read. A directory already tried is not listed again. A configuration from new_empty() has none.

use openmw_config::{ConfigChainStatus, ConfigError, OpenMWConfiguration};

fn main() -> Result<(), ConfigError> {
    let config = OpenMWConfiguration::from_env_or_user_config()?;
    for entry in config.config_chain() {
        let status = match entry.status() {
            ConfigChainStatus::Loaded => "loaded",
            ConfigChainStatus::SkippedMissing => "skipped",
        };
        println!("{:indent$}{status} {}", "", entry.path().display(), indent = entry.depth() * 2);
    }
    Ok(())
}

sub_configs#

The config= entries still in effect, as directories: file by file in the order the files loaded, each file’s in its own order. Entries naming a directory without an openmw.cfg are here, as OpenMW keeps those directories in the chain; entries naming a config a replace=config dropped are not. The chain loads depth first, so the last entry need not be the user’s config: user_config_path() is.

ConfigChainEntry#

One file the loader tried. Clone, Debug, Eq.

ConfigChainStatus#

Loaded: the file was read. SkippedMissing: a config= entry named a directory without an openmw.cfg, and the loader moved on. Clone, Debug, Eq.