<aside> ⚠️

This page documents known restrictions in Rigger Aids 5.1.1 and Blender’s current Python API. A limitation is not necessarily a defect: some behavior is constrained by Blender, the current data context, or the structure of the user’s file.

</aside>

Version and Platform Scope

<aside>

Blender 5.1 Is the Primary Target

Rigger Aids 5.1.1 officially requires Blender 5.1.0 and is primarily developed for the Blender 5.1 API.

• Blender 5.0 is not officially supported by this release.
• Registration has been verified in Blender 5.2.0 LTS, but every feature and production workflow has not been certified against every future Blender 5.x patch.
• Alpha, beta, daily, and custom Blender builds may change APIs without notice.

Operating-System Testing

Windows is the primary development and testing platform. Rigger Aids has no detected third-party Python package dependency, so macOS and Linux are expected to work with a supported Blender version, but platform-specific behavior is not tested as extensively.

</aside>

Action and Action-Slot Limitations

<aside>

Action Slots Cannot Be Reordered through Python

Blender 5.1 does not expose action-slot reordering through its Python API. Rigger Aids therefore cannot move action slots up or down and reports the operation as unavailable.

<aside> ℹ️

Sorting the displayed list does not change Blender’s underlying action-slot order.

</aside>

Multi-Step Slot Operations May Partially Complete

Some action-slot workflows copy or import data before removing a source slot or source action. Blender can accept the first step and reject the later removal.

If Rigger Aids reports that a slot was copied or imported but the source could not be removed:

1. Stop the operation.
2. Inspect both source and destination actions.
3. Remove duplicate or obsolete data manually only after verifying the result.
4. Save under a new filename.

Blender Determines Slot Compatibility

A stored action slot can become unavailable when its target type, action, owner, or related data no longer matches the current armature or object. Rigger Aids displays unavailable stored slots rather than forcing an invalid assignment.

</aside>

Shape-Key Limitations

<aside>

Vertex Counts Must Be Compatible

Copying shape keys between meshes requires compatible topology and vertex counts. Rigger Aids cannot automatically remap an incompatible shape key to a mesh with a different vertex count.

Read-Only Properties Are Not Copied

Rigger Aids skips shape-key properties that Blender marks as read-only or collection-valued. Some native data cannot be duplicated by assigning Python properties.

Embedded Third-Party Panels Depend on Context

Rigger Aids can display compatible external shape-key panels, but an external panel may depend on a specific Properties editor context or custom polling logic. When that context cannot be reproduced, the panel can appear as unavailable.

</aside>

Driver Aids Limitations

<aside>

Driver Aids Does Not Bypass Blender Driver Rules

Drivers created through Driver Aids remain standard Blender drivers. They are subject to Blender’s restrictions for:

• Valid RNA data paths
• Writable driven properties
• Supported array indexes
• Valid variable targets
• Valid scripted expressions
• Dependency-graph evaluation

Not Every Property Path Can Be Resolved

A property cannot be converted, pasted, previewed, or applied when Rigger Aids cannot identify its owner or resolve its full Blender data path. This can occur with:

• Read-only properties
• Temporary interface values
• Unsupported custom UI properties
• Renamed or deleted owners
• Invalid collection keys or array indexes
• Data that exists only in an unavailable context

Renaming Data Can Invalidate Stored Paths

Renaming objects, bones, constraints, modifiers, shape keys, custom properties, or other path components can make an existing Driver Aids node path stale. Rigger Aids does not automatically infer every renamed path across all saved node graphs.

Graph Preview Is Not a Full Production Evaluation

Preview verifies graph structure and resolvable targets, but it cannot predict every interaction with animation, constraints, dependency cycles, linked data, or other drivers. Always inspect the applied result in Blender’s Drivers Editor and test the rig across relevant frames.

Opening a Separate Drivers Editor Can Fail

Creating or focusing an additional Blender window depends on the current Blender window-manager and operating-system context. If a new Drivers Editor window cannot be opened, change an existing Blender area to the Drivers Editor manually.

</aside>

Linked and Overridden Data

<aside>

Rigger Aids cannot edit data that Blender exposes as read-only. Linked armatures, actions, meshes, shape keys, drivers, constraints, or other data may require a valid library override or a local copy.

Library overrides are controlled by Blender, and not every property or relationship is overridable. Test override-based workflows on a copy of the production file.

</aside>

Batch-Operation Limitations

<aside>

Batch Operations Are Context Dependent

Many commands depend on the active object, Blender mode, selected items, checked rows, stored source and target lists, and editable data. Rigger Aids cannot always infer the user’s intended scope.

Operations Are Not Database Transactions

A multi-item Blender operation may change earlier items before a later item fails. Blender does not provide a transactional rollback mechanism for every Python data change.

• Read every warning.
• Inspect partial results.
• Use Undo immediately when appropriate.
• Maintain versioned backups.

Name-Based Workflows Can Become Stale

Lists and mappings that refer to object, bone, constraint, action, shape-key, or vertex-group names can become invalid after data is renamed or deleted. Refresh or rebuild the affected list.

Large Rigs Can Take Time

Scanning and processing many bones, collections, constraints, actions, drivers, shape keys, or vertex groups can temporarily block Blender’s interface. Avoid clicking the same command repeatedly while an operation is running.

</aside>

Undo and File Safety

<aside>

Many Rigger Aids operators use Blender’s Undo system, but Undo behavior ultimately depends on Blender and the type of data changed.

Do not treat Undo as the only backup for:

• Batch deletion
• Batch renaming
• Driver application or removal
• Shape-key overwrite operations
• Constraint creation or removal
• Bone parenting
• Large multi-object operations

Save a versioned copy before destructive or unfamiliar workflows.

</aside>

Third-Party Add-ons

<aside>

</aside>

Script Library

<aside>

</aside>

What Is Not Considered a Limitation