Empty shapes, colors, and Driver Controls are viewport-only and never render — Empties are non-renderable in Blender. To get renderable geometry, use Convert to Curve/Mesh.

A new Curve or Mesh object matching the Empty's displayed wireframe shape — built-in or custom. Useful when you need the shape as real, renderable geometry outside the viewport.

Both. Use any of the 85+ built-in shapes, or generate a new one from a silhouette/outline via New From Silhouette — it's saved to your shape library alongside the built-ins.

No. Each control only tracks and displays what it created itself. Manual drivers and drivers created by other controls are never listed or modified.

Yes. Any property with a copyable data path can be added via Copy Full Data Path > Add Copied Property, including properties on embedded data-blocks like a material's node tree. This isn't limited to transforms, shape keys, and custom properties.

It skips the manual expression/path setup. You pick a target, pick the property (from a list or via "Copy Full Data Path" for anything not listed), and the widget's real range is auto-mapped to your Min/Max values. No need to open the Drivers Editor or write driver expressions by hand.

Yes. EmptyKit doesn't touch your armature or rig setup — it works with Empty objects and drivers, which are independent of whatever rigging system generated your bones. You can point a Driver Control at a bone property, a shape key, or any other drivable attribute regardless of which addon created the rig.