Why not just use the object offset properties of the node to assign the values you want? <node>.objectOffsetPos <node>.objectOffsetRot …

Yeah, I contacted the Administrator to try and reset my password.

I found it posted in a thread here: …but my password to that forum is invalid so I cannot download it. :curious:

Looking forward to the next installment… is the Link constraint about to make an appearance?

Thank you! I will certainly study this.

lecopivo: I didn’t read the whole thread but I think I have solution to original problem just have a look Download: if you are interested in mat…

Malkalypse: I actually know next to nothing about character assemblies, and the first hit I got when I googled (maxscript “character assembly”) was …

So the Delete protection plugin does not work to protect your rig components from deletion? You tried it?

The source code for Max9 and Max2009 versions is included with the Max 8-2009 plugin. Here: [ protection&sort=Author]( protection&sort=Autho…

Perhaps this node “Delete Protection” Maxscript Extension plugin created by Kees Rijnen can help you achieve your goals (protecting your rig component…

Rather than punish someone for deleting a critical node or nodes (stupid or not…) could you not use a #nodePreDelete or #selectedNodesPreDelete [font=…

But are you doing anything else between the “CTRL E” operations? That’s what he is asking…

Parameter event handlers are handlers like: on … set … do on … get … do Sorry I wasn’t much help.

Look in the Maxscript help for info on parameter block event handlers. Try using the “parameters” attribute in your when construction rather than “tra…

Look in the Maxscript help for info on parameter block event handlers.