Talk:OsslEnable.ini

Under development: changing from [XEngine] to [OSSL] and its consequences
Just a friendly warning (for those who, like me, had the surprise of their lives): OpenSimulator, as of mid-2018, has a new script engine (YEngine) under development, which will use the same permission directives. This forced the developers to change what used to be the [XEngine] section to [OSSL], and, similarly, the names of the macros have changed as well. Unfortunately, there seem to be some annoying additional differences, because it's not merely a question to do a search & replace to get things working again; in my case, for instance, even if I wanted to run XEngine, the new configuration simple broke down permissions, and I was left with a non-working configuration (which I managed to tweak until at least the simulator was able to start without crashing when parsing osslEnable.ini), which basically means that the permissions were set to the default, i. e., no OS functions whatsoever. Getting back to what I had before (and reverting to the latest stable configuration) has been quite painful, so, caveat utilitor.

Gwyneth Llewelyn (talk) 12:56, 12 September 2018 (PDT)