*"My only other concern/reason for providing those type of routines is because some of my other routines require data in that specific format, so I wanted to provide routines to format the data that way (if someone starts passing in data formatted some other way, it'll crash)."

*Yes.  I had to go through a lot of rather gruesome jiggery-pokery (if jiggery-pokery can be gruesome - who knows?) in the Geom module for just that reason.  Some lists require others as input.  In the end, it can become terribly confusing, which is why I built the "recipe" approach into Geom.  Well, that and because I had no idea what I was doing at the time - and perhaps still haven't!  Hmm.

You've been putting in more time on this in the past few days than I expected.  A big THANK YOU is appropriate, I think.  Many thanks, Spanki.  :D  Just don't neglect important stuff or, worse, burn yourself out. 

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.