SexScripts :: View topic - Feature Request - command line support/default script change

Feature Request - command line support/default script change	Banjo [ Sun Jul 31, 2011 4:23 am ]
As far as I've tried, SexScripts can't launch scripts via the command line (or batch files)... can it? I really want to be able to type "sexscripts.exe scripts\test.groovy" or something like "sexscripts.exe -r scripts\test.groovy" and have that script open and run automatically! After much begging, this was implemented in CyberMistress and proved very useful. If not (or maybe as well as?)... is it possible to have a 'configuration' option somewhere that lets the user choose which script auto-runs (if any) when SexScripts is run (currently "intro.groovy"). Once there are some "replacement default" scripts being made (with the power of SexScripts, it would be quite possible to make a default script that acts as a complete "Mistress" as CyberMistress did by 'default'), it will be a pain to have to rename the scripts to "intro.groovy" every time we want to try that out. A quick menu configuration that lets you pick a 'starting script' would make this a lot more user friendly.

Feature Request - command line support/default script change

Banjo [ Sun Jul 31, 2011 4:23 am ]

As far as I've tried, SexScripts can't launch scripts via the command line (or batch files)... can it?

I really want to be able to type "sexscripts.exe scripts\test.groovy" or something like "sexscripts.exe -r scripts\test.groovy" and have that script open and run automatically!

After *much* begging, this was implemented in CyberMistress and proved very useful.

If not (or maybe as well as?)... is it possible to have a 'configuration' option somewhere that lets the user choose which script auto-runs (if any) when SexScripts is run (currently "intro.groovy"). Once there are some "replacement default" scripts being made (with the power of SexScripts, it would be quite possible to make a default script that acts as a complete "Mistress" as CyberMistress did by 'default'), it will be a pain to have to rename the scripts to "intro.groovy" every time we want to try that out. A quick menu configuration that lets you pick a 'starting script' would make this a lot more user friendly.

Re: Feature Request - command line support/default script ch	doti [ Sun Jul 31, 2011 11:42 am ]
Ok, this will be possible soon.

Re: Feature Request - command line support/default script ch

doti [ Sun Jul 31, 2011 11:42 am ]

Ok, this will be possible soon.

Re: Feature Request - command line support/default script ch	Banjo [ Sun Jul 31, 2011 1:38 pm ]
Thanks! No hurry, just something that proved a very useful feature.

Re: Feature Request - command line support/default script ch

Banjo [ Sun Jul 31, 2011 1:38 pm ]

Thanks! No hurry, just something that proved a very useful feature.

Re: Feature Request - command line support/default script ch	w00tz0rz4 [ Wed Aug 10, 2011 12:57 pm ]
Yea this would be very useful. I prefer to compartmentalize scripts as much as possible, it makes it easier to keep track of what the hell I'm doing. You were able to jump routines in CM I remember, but I had all sorts of problems using the feature. Is there any method to launch other scripts within a script as this program is? Thanks!

Re: Feature Request - command line support/default script ch

w00tz0rz4 [ Wed Aug 10, 2011 12:57 pm ]

Yea this would be very useful. I prefer to compartmentalize scripts as much as possible, it makes it easier to keep track of what the hell I'm doing. You were able to jump routines in CM I remember, but I had all sorts of problems using the feature. Is there any method to launch other scripts within a script as this program is?

Thanks!

Re: Feature Request - command line support/default script ch	doti [ Wed Aug 10, 2011 1:40 pm ]
3 things : 1) you can call a script from another one : Code: return "helldate" 2) you can use "sexscript.exe helldate" to start a script at the beginning 3) you can change the starting script, for the next time : Code: save("intro.start_script", "helldate")

Re: Feature Request - command line support/default script ch

doti [ Wed Aug 10, 2011 1:40 pm ]

3 things :
1) you can call a script from another one :

Code:

return "helldate"

2) you can use "sexscript.exe helldate" to start a script at the beginning
3) you can change the starting script, for the next time :

Code:

save("intro.start_script", "helldate")

Re: Feature Request - command line support/default script ch	w00tz0rz4 [ Wed Aug 10, 2011 6:11 pm ]
doti wrote: 3 things : 1) you can call a script from another one : Code: return "helldate" 2) you can use "sexscript.exe helldate" to start a script at the beginning 3) you can change the starting script, for the next time : Code: save("intro.start_script", "helldate") awesome! Thanks man!

Re: Feature Request - command line support/default script ch

w00tz0rz4 [ Wed Aug 10, 2011 6:11 pm ]

doti wrote:

3 things :
1) you can call a script from another one :

Code:

return "helldate"

2) you can use "sexscript.exe helldate" to start a script at the beginning
3) you can change the starting script, for the next time :

Code:

save("intro.start_script", "helldate")

awesome! Thanks man!

Re: Feature Request - command line support/default script ch	Banjo [ Mon Oct 28, 2013 7:10 am ]
Is it possible for SexScripts to somehow also support "sexscripts.exe helldate.groovy"from the command line too? Right now, that will fail (it only wants to receive "sexscripts.exe helldate"... no extension!). I only ask because this would allow us to associate .groovy files with SexScripts on Windows. Alternatively I'm not sure, but maybe there's a way to make double-clicking a .groovy file open as a script in SexScripts automatically that I don't know of?

Re: Feature Request - command line support/default script ch

Banjo [ Mon Oct 28, 2013 7:10 am ]

Is it possible for SexScripts to somehow also support "sexscripts.exe helldate.groovy"from the command line too?

Right now, that will fail (it only wants to receive "sexscripts.exe helldate"... no extension!).

I only ask because this would allow us to associate .groovy files with SexScripts on Windows.

Alternatively I'm not sure, but maybe there's a way to make double-clicking a .groovy file open as a script in SexScripts automatically that I don't know of?

Re: Feature Request - command line support/default script ch	doti [ Tue Oct 29, 2013 9:08 am ]
Yes, it's possible, it'll be in the next release.

Re: Feature Request - command line support/default script ch

doti [ Tue Oct 29, 2013 9:08 am ]

Yes, it's possible, it'll be in the next release.

Re: Feature Request - command line support/default script ch	Banjo [ Tue Oct 29, 2013 11:02 am ]
doti wrote: Yes, it's possible, it'll be in the next release. Thanks! having both loading methods (with and without the .groovy extension) work should fix this issue nicely. Have I told "you're a legend" again recently?

Re: Feature Request - command line support/default script ch

Banjo [ Tue Oct 29, 2013 11:02 am ]

doti wrote:

Yes, it's possible, it'll be in the next release.

Thanks! having both loading methods (with and without the .groovy extension) work should fix this issue nicely.

Have I told "you're a legend" again recently?

Re: Feature Request - command line support/default script ch	doti [ Wed Oct 30, 2013 8:20 pm ]
Not enough Never enough

Re: Feature Request - command line support/default script ch

doti [ Wed Oct 30, 2013 8:20 pm ]

Not enough
Never enough

Re: Feature Request - command line support/default script ch	Banjo [ Tue Jun 14, 2016 7:15 am ]
Just installed SexScripts on a new PC and I can't seem to get this to work. Was the feature ever actually added as above? I tried "Open With" on the file "tutorial.groovy" and chose "SexScripts.exe" to open it with... but that just opens SexScripts without loading the script. However a batch (.bat) file that runs "sexscripts.exe tutorial" works fine. How do I get "Open With" (and thus, file associations) to work?

Re: Feature Request - command line support/default script ch

Banjo [ Tue Jun 14, 2016 7:15 am ]

Just installed SexScripts on a new PC and I can't seem to get this to work. Was the feature ever actually added as above?

I tried "Open With" on the file "tutorial.groovy" and chose "SexScripts.exe" to open it with... but that just opens SexScripts without loading the script.

However a batch (.bat) file that runs "sexscripts.exe tutorial" works fine.

How do I get "Open With" (and thus, file associations) to work?

Re: Feature Request - command line support/default script ch	doti [ Tue Jun 14, 2016 3:49 pm ]
Thank you ; "Open with..." on Window was a special case that didn't to my mind ; I saw the error and it'll be corrected in the next release.

Re: Feature Request - command line support/default script ch

doti [ Tue Jun 14, 2016 3:49 pm ]

Thank you ; "Open with..." on Window was a special case that didn't to my mind ; I saw the error and it'll be corrected in the next release.

Re: Feature Request - command line support/default script ch	Banjo [ Thu Jun 16, 2016 9:11 am ]
doti wrote: Thank you ; "Open with..." on Window was a special case that didn't to my mind ; I saw the error and it'll be corrected in the next release. Thank you very much! I was going nuts trying to make it work!

Re: Feature Request - command line support/default script ch

Banjo [ Thu Jun 16, 2016 9:11 am ]

doti wrote:

Thank you ; "Open with..." on Window was a special case that didn't to my mind ; I saw the error and it'll be corrected in the next release.

Thank you very much! I was going nuts trying to make it work!


SexScripts : Feature Request - command line support/default script change - https://ss.deviatenow.com:443/viewtopic.php?f=3&t=103	Page 1 of 1