@ironsoul the script is intended to be a first run kind of thing. It could run every time if added to poserStartup.py, but it can tell if it needs to do anything and avoid action if everything's in place. In that situation, it will only need one Poser exit with read only prefs to prevent overwrite. On next Poser launch, it can restore the writability of the Prefs and then do nothing. Every subsequent exit and launch of Poser will be unaffected. This will be tested, and still needs user interaction to Quit and relaunch Poser as instructed by the script.

I absolutely agree on the RPC/interprocess communication complication. I only mentioned that since I'd been browsing the Python framework within the Poser app and noticed those modules. Far better just to have sufficient, identifiable conditions to act once, repair preference permissions then remain dormant.

At the point where Poser (hopefully) eventually supports Python updates to the Runtime libraries, mucking about with preferences and filesystems (apart from folder creation) will become moot.

---

My ShareCG Stuff

Verbosity: Profusely promulgating Graham's number epics of complete and utter verbiage by the metric monkey barrel.