--makerlab-version
<version>Embed an arbitrary string as the MakerLabVersion metadata field in the output 3MF; the tag is written only when --makerlab-name is also provided.
Details
--makerlab-version accepts a free-form string and embeds it as a MakerLabVersion metadata entry inside the 3MF's primary model file. It is a companion to --makerlab-name: both values land in the same <metadata> element block, alongside other model-level fields such as designer, description, and creation date. The version string is XML-escaped before it is written, so characters that are special in XML are handled safely.
The flag has an empty-string default and imposes no format constraint on the value; any non-empty string is accepted and written verbatim. There is no semver parsing, no range check, and no enumerated list of valid versions. The slicer does not read or act on either value during slicing; it is purely a metadata annotation carried through to the output archive.
--makerlab-version is silently ignored when --makerlab-name is absent or empty. Both the name and version fields are written to the model only when the name is non-empty, so supplying a version without a name produces a 3MF with neither tag written. This is the only coupling between the two flags.
Watch out for
- ▲ --makerlab-version` is a no-op unless `--makerlab-name` is also supplied; both fields are written to the model inside a guard on the name field.
- ▲ The tag written is `MakerLabVersion`. When a 3MF is loaded, that tag is not read back into a dedicated version field; it is stored in the model's general metadata collection instead, which the 3MF writer uses as a passthrough when no CLI flag overrides the key.
- ▲ The value is XML-escaped on write but no format is enforced, so any string is accepted; there is no validation that the value conforms to a version scheme.
Sign up for free today
No credit card required. Connect unlimited printers and get production automation running in minutes.