Discovered Orca profile roots, application version, vendors, selected presets

Search profiles by type, name, vendor and source

A profile with inheritance expanded. mode: raw — file contents, resolved — effective values, traced — values with provenance. Engine defaults are excluded unless include_defaults is set

The inheritance chain to its root, with how each link was resolved

Where a key's value came from: originating link, overridden values, engine default

Profiles inheriting from this one. Check before editing shared profiles

Compare two profiles by effective values (mode=resolved) or by their stored deltas (mode=raw)

Integrity check: broken inherits, cycles, unknown keys, redundant deltas, name collisions

Verify inheritance expansion against the deltas Orca itself wrote: for every profile, the delta is recomputed and compared with the file. A mismatch means the resolver expands the parent differently than the engine did; redundant keys are reported separately and are harmless

Compare a profile against its version in the OrcaSlicer repository

Set profile values. The delta against the parent is recomputed automatically and the paired .info is updated. Editing a system or bundled profile affects every descendant and needs force=True

Create a user profile inheriting from the given one

Rename a user profile

Delete a profile; deleting outside your own profiles needs force=True, and cloud-synced ones keep a flagged .info

Drop keys whose values are identical to the parent's