--uptodate-settings

--uptodate-settings supplies the preset JSON files that --uptodate uses to refresh the machine and process configs embedded in a 3MF. It accepts a semicolon-delimited list of file paths, e.g. "machine.json;process.json". Each file is loaded individually; the slicer inspects the JSON's top-level type key to decide whether it is a "machine" or "process" config. A file whose type is anything other than "machine" or "process" (including "filament") is a fatal error. Filament presets are handled separately by --uptodate-filaments.

Each supplied JSON must carry a name field that exactly matches the system preset name the 3MF records for that config category. The 3MF stores one root system preset name per config type inside its inherits_group field; the machine system preset name occupies the last position of that array, and the process system preset name occupies the first position. Those are the values the slicer compares against each JSON's name. If the name in the supplied JSON does not match what the 3MF expects, the CLI aborts with a config-file error. Passing a renamed copy of a preset or a preset for a different printer model will always fail this check. The JSON's from field must also be present and set to "system", "User", or "user"; any other value is rejected before name matching even occurs.

When --uptodate-settings is omitted but --uptodate is active, the slicer falls back to its own bundled preset files, resolving the machine and process presets by name from the internal profiles directory. Supplying --uptodate-settings lets an automation pipeline inject presets that differ from the bundled copies -- for example, when running a slicer build that does not yet include a recently published preset, or when working with a private preset distribution that ships outside the binary.