--load-filaments

--load-filaments accepts a single quoted string of semicolon-delimited file paths, one JSON filament config per extruder or AMS slot. Assignment is strictly positional: the first path becomes slot 1, the second slot 2, and so on. Each file is a JSON preset in the same format the slicer writes when exporting a filament profile. The engine validates each file on load: the JSON must have "type": "filament" and a "from" field whose value is "system", "User", or "user". Any other value in "from", or a "type" other than "filament", causes an immediate fatal exit.

When a file's "from" is "user" or "User", the engine reads its "inherits" field. If that value matches a profile name in the bundled BBL filament library, the engine pulls variant-tracked options from that parent and uses them as defaults for any variant fields the user file does not explicitly set. System-profile files (where "from" is "system") undergo no such merge; they are loaded as-is.

An empty string in the semicolon list acts as a slot placeholder. When the default-filament fill is active, the first successfully loaded profile fills in for any empty-string slots so that the slot-to-index alignment stays intact. This mode can be requested explicitly via a dedicated flag (--load-defaultfila), and the engine also enables it automatically in estimate mode.

If all entries across the list resolve to the same profile name in a BBL 3MF context (and estimate mode is not active), the engine automatically suppresses the wipe tower for the job. It can reinstate the tower, however, if the color overrides passed alongside the filament list contain more than one distinct color value, if smooth timelapse is active, or if wrapping detection is enabled and a wrapping exclude area is configured.