Something I've noticed that's confused me:

Although recommended for changing SexScripts' "runs on startup" script (rather than replacing 'intro.groovy' completely), 'intro.start_script' in 'data.properties' doesn't seem to always work correctly.

Even though I have it set to a different script (in my case, 'welcome.groovy'), occasionally (seemingly at random) the old 'intro.groovy' loads instead when I start SexScripts. Checking the data.properties file reveals that intro.start_script is correct ('intro.start_script=welcome') so it's not like it got reset unknowingly. It just seems like SexScripts "decides" to use intro.groovy every so often!

Any idea what's causing this bug or why it might happen? Is there a way to make SURE that 'intro.start_script' works 100% of the time unless changed on purpose?

This this a bug. I didn't know about and could not reproduce (if I remember well, it is used in Jewell). What is your platform, and may it be related to something like this ?
- starting it more than one time at the same time
- computer very slow
- editing (with another editor) the data.properties file during this start/stop
- using a special file (other than sexscripts.exe) to run SexScripts ?

It seems to be very random. My intro.start_script is set to "system/welcome" (actual script is "welcome.groovy"). What's odd is that it doesn't happen ALL the time, just when it feels like it. The script runs fine when opened normally, but only sometimes opens when I load SexScripts.

I just tried opening multiple instances of SexScripts, and the first one used the wrong intro.groovy (ignoring intro.start_script completely) while the second instance of the program loaded the right script on launch!

So, I tried closing both instances and opening the program again. Loaded welcome.groovy. Tried again... worked correctly again. Tried again... loaded intro.groovy. I checked data.properties, and intro.start_script was still set to "system/welcome" though, so it's not changing that line, just ignoring it sometimes.

(tried three more times: 1st=intro.groovy, 2nd=intro.groovy, 3rd=welcome.groovy)

Very odd bug! I was at first wondering if it was like CyberMistress and was programmed to do certain stuff after counting how many times you ran the program. But what you said makes me sure this isn't intended behavior at all.

Manually editing data.properties or doing so via a script works, but again only "at random". It's still not consistent.

It also makes no difference if I'm rendering a huge scene in Poser and slowing the computer to a crawl, or running nothing else. Same "chance" of the right script being loaded, it seems.

Using a batch file, one that just contains: loads the right script every single time... so surely it has to be something to do with "intro.start_script" then?

Oh, and if it makes any difference, I'm on Windows 7 x64.

Ok, I saw it, and it'll be corrected very soon

Thanks! I'm just glad I'm not going crazy and it was an actual bug! One of those things where I wasn't sure if I was doing something to cause it or even imagining it!

Is the fix available for this?

As I know, the last releases are working well, about this.