I’m not entirely sure whether this is a feature request or a bug, but I would like to have underscores in the name of a controller.
I’ve tried with “control_01” and underscores are removed once finished editing the name.
That is done by design. Right now the naming structure is kind of hard-coded.
I would like to implement something where the user can edit his own naming patterns, but is not a priority for us. Provably will never be done, unless some one else wants to tackle this 
Why particularly exclude underscores from the name? Is it to force a naming convention?
Also have you had any thoughts for a naming pattern framework?
Maybe someone can get a head start on this, if we lay out a rough plan.
yes that is what I was trying to say in the previous post.
the current naming convention is hard-coded, But I would like to have something more flexible.But it is not a priority
I’ll add a vote for a naming template that can be customized. 
It’d probably be a ton of work to go in and rename everything… but it would make it very handy to integrate into an existing pipeline!
1 Like
taking note of this https://github.com/mgear-dev/shifter/issues/83
I didn’t announce this officially but I will work in a new pack of shifter components for Games (in specific following Unreal Engine Mannequin pattern but will work also in Unity and other engines of course) and I guess I will need this feature.
2 Likes
@Toke_Stuart_Jepsen @Jason_Schleifer @Jerome
I am working now to implement a system to support custom naming templates, I would like to have your feedback and advice to do this.
For the moment I am watching this https://www.youtube.com/playlist?list=PLYcUacEjhPL-40O1ca6n1A0AAnco5CMzH from Cesar Saez and also I have merged this nice update https://github.com/mgear-dev/shifter/pull/85 from Ruuttu
can you provide some samples of naming templates and ideal functionality?
is it needed for all nodes? or only controls and joints?
thanks,
Miquel
Cesar’s naming template seems pretty solid. You could get inspiration from https://lucidity.readthedocs.io/en/stable/guide/introduction.html and possibly https://github.com/getavalon/core/tree/master/avalon/tools/workfiles#templates
Personally I think only controls and joints. Those are the nodes users dont have naming control over, that is also often used outside of Maya.
1 Like
Following up on this as I’m seeing even “Rig Name” doesn’t actually keep underscores. Is there a reason for this or is it just something that needs a quick bug fix?
It seems like a fault of the guide settings window as I can manually set the Rig Name no problem in the Attribute Editor.
EDIT:
Looks like a quick fix. In guide.py line 1686 change self.updateLineEdit to updateLineEdit2
1 Like