I am working on a script to generate modular rig segments such as IK/FK chains and other such controls to drive a result skeleton. After creating a rig segment, the user can then take those controls and add space-switching parents to them to make that part of the rig constrained to whatever parents the user wants. The…
I see! I'll store it in a custom attribute, then. I appreciate the Python example, but I don't think the data I'm writing is enough to warrant writing it into its own file. Right now it's just a simple string containing the names of the parent objects and what type of constraint the space-switching system is bound to them…
I think json is still great for this. You can do something like: data = {"constraint_relationships": {"node1": "parent", "node2": "orient", "node3": "scale"}} # JSON string in the attribute
'{"constraint_relationships": {"node1": "parent", "node3": "scale", "node2": "orient"}}' Having the data this way gives you a lot of…
I recommend storing it in a custom attribute. Notes may be used for other things, so you generally don't have to worry about anybody touching your attribute. If you're writing the attributes in Python (I highly recommend doing this), then you can use a format such as json to store your data in the attributes. Example:…