🎉 WIN a Snapmaker U1 Printer! Enter FREE now

--repetitions

<count>
Object Arrangement & Transformation Orca SlicerBambu Studio

Duplicate every object on the specified plate to produce a total of N copies and auto-arrange them; requires a non-zero --slice N plate selection and silently reduces the count if the copies do not all fit on the bed.

Details

The --repetitions <count> flag tells the slicer to duplicate every object on the target plate a total of count times before slicing. The value is an integer with a default of 1. Values of 1 or less are treated as a no-op and skipped with an informational log; the minimum meaningful value is 2. The engine computes one fewer than the requested count as the number of additional copies, then duplicates all existing (object, instance) pairs on the target plate, appending that many new model objects for each one. Each copy receives the source object's name with a _1, _2, … suffix. After duplication, arrange is unconditionally forced regardless of what the 3MF specified, so the copies are placed automatically rather than stacked at the origin.

Because the flag operates on a single plate's object list, it requires an explicit plate selection via --slice N (a non-zero, 1-based plate index). Passing --repetitions without a specific plate value — i.e., when slicing all plates via --slice 0 or with no slice option set — is a hard error that exits with CLI_INVALID_PARAMS. The plate index is also validated against the actual plate count in the 3MF; an out-of-range value is likewise fatal. The flag is also mutually exclusive with --load-slicedata: combining them exits with an error.

Two secondary interactions are worth knowing. First, when spiral_mode is enabled in the process profile and the plate is not in by-object (sequential) print mode, the duplicate count is silently reset to zero and a warning is logged — no copies are added and no error is raised. Second, the slicer does not guarantee that all requested copies will appear in the output. It runs a binary-search arrange loop: if the full set of copies does not fit on the bed, it backs off toward the largest count that does fit. The sliced_count field in the output metadata records the final actual count, not the requested one.

Watch out for

  • Must be paired with `--slice N` (a non-zero, 1-based plate index); using it with `--slice 0` or without specifying a plate is a fatal `CLI_INVALID_PARAMS` error.
  • With `spiral_mode` active on a plate that is not in by-object sequential mode, repetitions are silently dropped — the flag is ignored without a slice error.
  • The slicer may produce fewer copies than requested: if the full count does not fit after arrange it binary-searches for the maximum that does fit, and the output records only what was actually sliced.

Sign up for free today

No credit card required. Connect unlimited printers and get production automation running in minutes.