izom PropUI Rigify

izom PropUI Rigify is a Rigify feature set for authoring a clean, generated rig control UI directly from a Rigify metarig. You author the controls on a metarig bone, generate the rig normally with Rigify, and the finished controls appear on the generated rig: select the bone and open the Item tab to find them in Rigify's native "Rig Main Properties" panel.

Installation

Enable Blender's built-in Rigify feature.
Open Rigify preferences.
Install the izom_propui_rigify feature set ZIP.
Enable izom PropUI Rigify in the external feature set list.

To update an existing installation, remove the old izom_propui_rigify feature set from Rigify preferences before installing the new ZIP. Rigify does not overwrite an installed feature-set folder.

The feature set can be enabled in the same Blender profile as izom PropUI. They use separate operators, shortcuts, settings, and generated helpers.

Quick Start

Add or select a bone on your metarig.
Set the bone's Rigify Type to izom.PropUI.
Use the izom PropUI Rigify editor shown in the bone's Rigify parameters.
Add entries to the Entry List and configure their labels, values, display style, conditions, and storage.
Arrange the generated UI in the Generated Layout section.
Generate the rig with Rigify.

The generated controls appear in Rigify's native "Rig Main Properties" panel on the generated rig (select the bone, open the Item tab).

Where The Editor Lives

The editor is part of the Rigify metarig parameter UI for the izom.PropUI rig type. Select the metarig bone that owns the component to edit its setup. All authored data is stored on the metarig through Rigify parameters.

Output Setup

Output Setup controls where generated custom properties are stored and how native metarig custom properties are handled.

Use One Prop Bone stores all managed generated properties on one chosen generated bone.
One Prop Bone chooses the bone used by the One Prop Bone workflow.
Per-entry Prop Bone Override can send a specific entry to a different generated bone.
Sync to Metarig imports or refreshes supported custom properties from the metarig into the Entry List.
Move Matching moves matching metarig properties into managed PropUI entries during sync.
Clean Metarig Props removes custom properties from the metarig storage bones without changing the editor setup. Pick which bones to clean - the Host Bone, the Prop Bones, or Host + Prop Bones - and how much to remove:
Managed Only clears just the properties managed by this PropUI setup.
Unmanaged Only clears only properties that this setup does not manage.
Selected Entry clears just the active Entry List item's property.
All Custom Properties clears every custom property on the chosen bones.
Native Passthrough can preserve unmanaged native custom properties and draw them above or below the managed PropUI controls.
basic.raw_copy behavior is built into the component. The section exposes relinking constraints, parent bone selection, and widget options.

Entry List

The Entry List is the main list of controls that will be generated. Entries can be reordered, duplicated, hidden from the editor, grouped into parent/child hierarchies, and targeted by keyboard shortcuts.

New entries that use the default generated naming choose the next unused prop_N and Property N number. If an earlier default entry was deleted, the next add can reuse that open number instead of jumping to the end of the list.

Supported entry types:

Float creates a floating-point custom property with default value, min/max, soft limits, step, precision, and subtype controls.
Integer creates an integer custom property with default value, min/max, soft limits, and step controls.
Boolean creates a true/false custom property.
String creates a text custom property.
Data-Block creates a property that points at Blender data such as objects, materials, actions, images, or other ID types.
Python stores Python-literal IDProperty values such as lists, dictionaries, numbers, strings, booleans, and None.
Array creates typed float, integer, or boolean arrays with component count, subtype, defaults, and numeric limits.
Custom draws an existing Blender RNA property or an internal generated UI control.
Display Link draws an existing managed or custom entry again with its own label, tooltip, display, dynamic labels, and conditions.
Text adds text-only rows to the generated UI.
Operator Button creates a generated UI button that runs a Blender operator or feature set operator.

Array display layouts can draw all components in one row, use Blender's split main-label style, put the label above the row, stack component rows, split only the stacked main label, or give each stacked component row its own split label. Color and direction-style float arrays can use Blender's native whole-value widget when the selected layout supports it.

Custom entries follow the sensed value kind. When Blender can draw the target as a normal property, Custom paths can use the same scalar label-layout and multi-component layout controls as managed entries.

Text style controls include alignment, alert styling, and optional before/after icons. Icon Hug Text controls are available for centered text, where Blender can reliably separate detached icons from the text. Left and right aligned text always keeps icons attached to the text, so those controls are disabled.

The Hierarchy Lens helps inspect parent/child structure, group entries, ungroup entries, collapse branches, and manage hidden editor entries.

Selected Entry

Selected Entry edits the active Entry List item.

Basics sets the entry type, generated label, tooltip, property ID, parent, linked entry, operator button text, or text-row content.
Value controls defaults, limits, data-block type, array subtype and size, custom property paths, Python literal values, and operator button behavior.
Display controls how the entry is drawn, including labels, tooltips, component display, icon choices, button/operator presentation, color-style drawing, and row behavior.
Dynamic Labels can change labels or text based on the current value.
Conditions controls when an entry is visible or available in the generated UI.
Storage sets the per-entry prop-bone override and library-overridable behavior for managed generated properties.
Tools includes type defaults, copy-settings tools, Display Link tools, and entry preset import/export.

Display Links

Display Links let you draw the same source entry in more than one place without creating duplicate custom properties. A Display Link can use the source label and tooltip or provide custom text. For multi-component values, it can draw only selected components.

Dynamic Labels And Conditions

Dynamic Labels change generated labels or text rows when values match rules. They are useful for making compact controls that explain their current state. Rows act as a priority list: if more than one row matches, the row higher in the Dynamic Labels list wins. Overlapping or identical match values are allowed. Add creates a fresh default rule row for the active value kind, while Duplicate copies the selected rule when you want to start from an existing row.

Conditions control visibility and availability. You can use them to show child controls only when a parent or related entry is in the right state, or to keep a control visible but disabled until it should be edited.

Generated Layout

Generated Layout controls the shape of the UI that appears on the generated Rigify rig.

Add rows, sub-panels, text rows, Display Links, operator buttons, internal controls, and property entries.
Move entries between rows and sub-panels.
Use shared rows to place multiple controls on one line.
Use Row Boxes to frame a range of generated rows together.
Set sub-panels to start open or collapsed.
Use Safe Import when pulling Entry List items into the generated layout.

The Row Boxes list order is for organizing the editor list. Use the selected Row Box range controls to change which generated rows a box wraps.

If you leave the Generated Layout empty, the feature set can still generate a basic layout from the Entry List.

Generated UI Internal Controls

Internal controls are optional controls that can be placed in the generated UI:

Generated UI Enabled lets the rig user turn the authored PropUI section on or off.
Disable While Transforming hides the generated UI while Blender is running an active transform operation.
Disable While Playback hides the generated UI while animation playback is running.

These controls are authored on the metarig and generated into the Rigify UI.

Editor Layout

Editor Layout lets you choose which editor sections are visible and how they are ordered. You can rearrange sections such as Output Setup, Entry List, Selected Entry, Generated Layout, Editor Settings, and their subsections.

Use this when a rig needs a focused authoring layout, or when you want advanced sections hidden until they are needed.

Editor Settings

Editor Settings control how the authoring editor behaves.

Display & Precision sets editor number precision.
Shortcuts can disable all izom PropUI Rigify shortcuts and hides shortcut target controls.
Entry List controls tree hints, Entry List display, Generated Layout display, and the default type used when adding entries.
Confirmations controls which destructive or broad actions ask first.
Import / Export exports or imports a full setup, selected entry type preset, or editor settings JSON. Clipboard copy and paste are available for the same JSON data.
Saved Defaults can save editor settings, editor layout, and a full setup as reusable defaults.
Reset izom PropUI Rigify can reset the current setup, settings, saved defaults, or the full feature set data stored in the file.

Shortcuts

Shared shortcuts act on the currently selected shortcut target. Use Shortcuts Affect This List or the shortcut target menu to decide whether shortcuts affect the Entry List, Generated Layout, Row Boxes, Dynamic Labels, Display Link component subsets, or Editor Layout.

Shortcuts are scoped to the Rigify parameter editor in Blender's Properties editor, so they can be used alongside the standalone izom PropUI shortcuts in the same Blender profile.

Disable all shortcuts from Editor Settings when you prefer to work only with buttons and menus.

Import, Export, And Defaults

You can move setups between files with JSON import/export:

Full setup JSON stores the current metarig component setup.
Entry type presets store reusable settings for a selected entry type.
Editor settings JSON stores editor settings, editor section order, and open/collapsed defaults.
Saved defaults can auto-apply a preferred blank setup or editor layout to new sessions.

Diagnostics And Blend Inspection

Diagnostics appears when the feature set has warnings to show. You can clear the diagnostic list after reviewing it.

Audit Blend Data reports how many izom PropUI Rigify components, authored entries, and generated Rigify UI text blocks are present in the current file.

License Notice

The License Notice button is available from the izom PropUI Rigify entry in Rigify preferences, below the Documentation button.

Notes

Rigify owns the generated UI, so this feature set always generates through Rigify's normal rig generation flow.
Rigify still owns the generated Python UI text name, rig_ui.py.
Regenerate the Rigify rig after changing metarig PropUI settings.
UI Variants, custom generated branding, custom UI text names, and generated UI manager workflows are not part of this Rigify feature set.