Had a curious thing happen last night while I was playing dead.
Seems a companion-maker decided to, rather than simply use NCCS as a master, fold the entire mod into his companion plugin.
Now, this isn't going to be a "stole my stuff, con sarnit!" rant. I listed NCCS as freely reusable on the Nexus, so long as attribution is given. He kept it to the Nexus, and gave credit, so I'm not pissed off or anything.
What I am is wondering.
See, the whole concept behind NCCS, much like CM and RR before it, is that I as the system author, cannot know the RefIDs of the companions made with the system. So, all scripting has to be done in a roundabout fashion to account for this fact.
NCCS was folded into EVE-900 though, to drive one single companion. Now, maybe I've been writing my own systems too long, but it seems to me that writing a new framework from scratch to drive a single companion would be far less trouble in the long run, than trying to keep a create-your-own system updated inside your plugin.
Conversely, wouldn't it have been easier to just flag NCCS as a master? I mean, the master archive is less than a hundred kilobytes. Is it really that big a deal to download?
I realize NCCS looks super cool and spiffy and all to most of you guys who use it, but copying the entire mod to run one standalone companion is like using a 12 gauge to kill a field mouse - sure, you can do it... but it's hardly the optimal tool for the job.
But, hell, what do I know?
I nonetheless wish our intrepid modder much success with his creepy robot companion, regardless of what ends up under the hood.