If the {index} is removed from the Controls Naming Rule, then {description} will behave incorrectly, adding “Control” to the name of any controls which do not generate from a chain or have a special function (fk, ik, over, loc, etc).
This includes any “control_01” components, shoulder, meta, etc.
Example with a fresh file and “shoulder_02” component:
With {index}_{description}: shoulder_L0_ctl
Without {index}: shoulder_L_control_ctl
Without {description}: shoulder_L0_ctl
If the {index} is removed from the Controls Naming Rule, then {description} will behave incorrectly, adding “Control” to the name of any controls which do not generate from a chain or have a special function (fk, ik, over, loc, etc).
This includes any “control_01” components, shoulder, meta, etc.
Example with a fresh file and “shoulder_02” component:
With {index}_{description}: shoulder_L0_ctl Without {index}: shoulder_L_control_ctl Without {description}: shoulder_L0_ctl
reported in forum http://forum.mgear-framework.com/t/control-names-breaking-when-changing-rules/3377