Quote:
I really do like estim! SexScripts tends to emphasize punishment, so I copied the files from Hurrah for School and the card games (Baccarat and Strip Jack Naked). These used estim as a forfeit, but I agree that this script should be mote fun. There should be a fun side to SexScripts!
I don't think Sexscripts itself is emphasizing anything, it just happens to be the initial creators for estim Sexscripts wanted a CBT creation. I think file availability is the biggest reason why we don't have anything pleasurable. It's difficult to create files, which is why so many authors share filesets between scripts and if I can get some pleasurable files out there, I think they will be used by other scripts. I agree with you, a fun side has a place here. It just hasn't been done yet. We'll create our things and it will attract an audience and other creators to see what can be done and build off of it. I'm working on my own scripts(mostly idea phase and testing small programming components) a little bit here and there and I have a few ideas that I got from playing other Sexscripts and Milovana teases but programming is a slow process for me. I'm going to try to put together the memory game that MissEshock2002 started the programming for(Thank you!) and I'm working on audio file selection.
I find it a little tricky not having a volume control for the audio on this platform because it means that punishment intensities are more difficult to dish out without a stack of files. I personally think a reasonable shortcut so less files need to be created and published, it's best to add more of the pain by having an escalating file that is run longer(more pain deeper into the file) when more pain is desired and is cut short to limit the pain. I think if the goal is to complete a task in a short period, a file starts at a non-painful level(or maybe pleasurable) and gradually changes to painful, and then raises more suddenly as the time limit is reached. That way you've got more variety to the signals instead of how hard they are being jammed through.
It seems there are some pain files that work on many devices(at least DIY, BTstim, 3rdH, 2B, and ET-312B) that don't have a blast of sound. I'm working on putting some of those together and also putting together some pleasurable stuff into a resource pack that can be used by other scripts. There is a struggle with the 2B in that it has limits to creating pain, it seems it needs a much higher volume file when used together with pleasurable files, the pleasurable files need to be at 40% of the volume of a pain file and for almost all other devices pleasurable files would be about 70-80% of a pain file. So if you design for the 2B, the others get left out because the volume difference is substantial and if designing for everything else, the 2B gets left out. I use a DIY device because it's compatible with the most stuff(including pain, tri-phase effects, short pulses without filtering or ignoring them), but it will play what you give it because it's a bookshelf amplifier with a few extra components added for safety to limit the current, boost the volume, and smooth the signal) and the biggest no-no is low frequency files, anything that sounds like bass through headphones stings because nerves don't like to operate off of DC or anything close to it. Some devices convert low frequency audio to something else or ignore it. My thoughts for the 2B are that if I create something with a mix of fun and pain, either the pain files are there and they don't feel strong and it's mostly a pleasurable script. ..or I put in a function to disable the pleasurable stuff so the volume can be calibrated for the pain. I suppose there is always the option for 2B users to make their own compatible swap-in resource pack to replace the files with a set that works well for the 2B.
What device do you use again?
Quote:
I conceived this script do have a variety of actions, so it doesn't seem tight to me to add estim to everything.
That's fair, it's your script after all. I was only trying to modify my own 'version' and forwarded the idea. I should really putting my effort into creating something of my own instead of trying to fork what's already here. If anything, I could just run a sound file outside Sexscripts during the edge sequence with a file of my choice and add a button to end the edge sequence because my edges aren't clockwork, some are slow and some take awhile.