diafero wrote:Trylon wrote:Well, it's not that good of an age anyway. I should probably get around to remaking it. Might as well rename it and re-assign the prefix
That would make it a new age, and I would not really like to loose the old one. Recently had a lot of fun in there
Anyway, that's a different discussion. It'll be some years till ULM database reaches 16000.
Back to the PythonFileMods: Where does the plugin get the information about how the parameters are called? Does it automatically read the Python files and extract the ptAttrib* lines? That sounds greats and easy to use, especially when I think about how you set these parameters in PyPRP.
That sounds like the logical way to handle them. When I wire something for an age I always design the Python code first. During the design stage I define activators and responders etc. And by the time I start writing the Alcscripts for Blender I already know exactly what each responder should do.
For the current project I am involved in I do not even implement these Alcscripts myself but send them to the Blender modeler(s). It seems Cyan follows a similar workflow. Apparently you can simply send the complete Python files to the modeler and the plugin will find the references automatically. However, you will still need to explain what the responders should do.