Yes. A batch rename is one Undo-enabled operation. Undo and Redo of object naming were verified in a native Blender UI context on Windows with Blender 5.0.1 and 5.2.2 LTS.

Yes, renaming a shared material updates that material for every object using it. Mycel 1.0.1 processes shared data once, including repeated material slots, shared meshes and shared armature bones.

It keeps the active collection, its ancestor path and descendants visible while hiding other branches. It preserves existing collection exclusion and object hiding. Show All clears layer-collection viewport hiding; use Undo or a saved Scene State to restore a specific layout.

Yes. Save your Blender project to keep named states. They capture object visibility and layer-collection hiding/exclusion in the active view layer, not geometry or camera views. States use data names: update them after renaming or deleting objects or collections.

Scan Scene groups object names with the same base name, such as Cube and Cube.001. Select a group, review Sequential naming settings, then click Rename. There is no live before/after rename preview and no geometry, mesh-name or material-name duplicate scanner. Sequential naming processes objects alphabetically.

Linked/read-only data is skipped during renaming and reported. Local overrides follow Blender editability rules. Mycel 1.0.1 requires Blender 5.0.0 or later; Windows tests cover 5.0.1 and 5.2.2 LTS. Other versions and operating systems are unverified.