Scripts essentially are a type of subtitling or action sequence normally made to coincide with a video or other type of playable media (audio files included) that are read by teledildonic devices to produce a change in movement, vibration or other forms of varying stimulation.
The script is read on a timescale by these devices and points are plotted with scripting software that are used to specifically change the devices settings to provide *hopefully* a specific intended sensation such as stroking the head of a penis or simulating sexual intercourse. Vibrating teledildonics are limited to only varying which nodes of vibration are active which doesn’t provide movement which is the main reason scripts came along with the advent of the REALTOUCH.
Main Compatible Devices
The three main devices that are used for experiencing funscripts are in order of images:
The Handy – Released 2019
The Keon by KIIROO – Released 2020
The Fleshlight Launch – Released 2017 – *Discontinued 2020*
To get more into the video script side of things, what we are trying to do when we script a piece of content is to map when we want a device to move or operate to synchronise with the video the script was made for. In essence it’s a mimic of the action provided by the actors on screen and when the penis of the actor is stroked, the device responds accordingly.
The reason why we have multiple points is to map specifically where the action started and ended, this provides a timestamp from point a to point b and the time/frames between those points. The more accurate the plotting of those points the more accurate the devices will replicate the action, this requires patience as mapping accurately can depend on camera angle, size of the penis, speed of the action, or even the frame rate of the video scripted.
Above is a visual reference of how you could visualise all of these markers on an object.
Length is an small issue because the devices do not have a long enough stroke length to replicate a whole stroke fully, meaning the longer the penis or object interacted with, the further away the points 0 – 10 will be. The stroke length of these devices is anywhere between 2.5 – 4 Inches and trying to stretch that stroke length to something the size of 8 inches means slower replicated action from point A to B.
We can as scripters specifically set limits on what we consider the bottom of a stroke but this will come at the cost of synchronization accuracy making the experience feel lesser for some wanting a complete replication of the scene they are watching.
Other limitations in scripting include speed of actions on screen and with any technology using moving parts, it’s hard to beat the speed of a human and because of this some scenes are not accurately replicated in movement with these devices. CAPPING of speed is indicated by red lines within the scripting software and ways to avoid capping speed involve making the stroke length shorter for the device and sticking to a solid repeating pattern instead of including the fast variation that might be displayed on screen.
Time Consumption / Spliced Points
Scripting is a time consuming process much like subtitling, there are thousands of points to map and to make sure the action isn’t too linear we need to splice strokes using different positioning and timing. For example if someone was to stroke halfway up an object from the bottom slowly but increase pace for the second half of the stroke we would need a point in the middle to anchor from.
These middle points allow us to change the pace of the second half of the stroke and we can do the opposite and have the start of a stroke be fast and the second half of the stroke be slow. This is where accuracy lies and variation of speed and stroke length makes plotting these points a tricky business.
Scripters may use a ‘On the Fly’ scripting technique to map the most basics of the script providing a low resolution replication of the action, they will then sift through the script to make sure points are mapped on time and accurately placed. On the Fly just means we script as we watch and the tools we use to script allow us to accommodate for bad reactions by adding latency.
The faster the action is the harder it is to react so we can have a buffer that will place the point a bit further back just incase we were late in pressing the desired button. This a long with a slower playback gives us a good place to practice getting used to mapping points accurately.
Alternatively we can script frame by frame which is the most time consuming of methods to scripting but provides you with the ability to jump back and forth and plot points accordingly. I would suggest starting out with slower scenes to get a sense of accuracy in scripting before you go for anything too fast. There’s nothing worse than a 30 minute scene with 15 minutes worth of fast strokes and trying to plot them frame by frame.
Fatigue is a real problem and RSI will be the main issue you run into getting into scripting but there are plenty tools and options for plotting these points with VR Controllers being one and a regular gamepad controller being another. I haven’t spent much time using these two other control methods but practice should provide you with good muscle memory if you were to take on scripting this way.
What does the Software look like?
The programs that are mainly used to script are JoyFunScripter and OpenFunScripter. Both are very similar with JFS laying the groundwork for how scripting software functions currently. OFS is a more open source piece of software that doesn’t restrict what you can do with your personally created scripts, JFS on the other hand shouldn’t be used to commercialise your scripts.
Both function fairly similarly but my time has mainly been spent scripting in JFS because it was the first piece of software to replace the horrible blender scripting that used to be used *very slow*.
Visual bars are used to aid in the scripting process. You place the bar over the object that is being interacted with on screen and it fills according to your current position plotted on the time bar.
Bad Scripting Practices
Scripting isn’t too hard to do but there’s certain things you may do out of intuition that do not end up in a good end product.
One of these is placing too many points during a stroke. Variation is good but because these devices mainly use bluetooth to sync, there’s natural latency and juttering can come with an overly complicated sequence.
Plotting too many points in a short period of time will most likely result in a good portion of those actions being dumped as the device cannot process the action. It may be because there’s too many changes in positioning happening or because the stroke speed desired in the script is too fast for the device to even perform.
Actions should be as smooth as possible but have variation where realistically needed. Finding this balance of what’s useful to add to a script sequence and what’s going to ruin the devices movement is important. If you own a device that supports funscripts, you could try littering a bunch of points around and play it back using the device to see first hand how your toy interprets the script. It may be that your device can handle the speed and alteration.
Short History of Current Scripting
Having been here since 2017 when the Launch RIP graced us with it’s attempt to do interactive porn, I’ve seen large growth of the interest in this type of experience. It took a few months but thanks to many folk such as, Qdot, FunJack and FredTungsten we got an interactive video syncing device to replace the Realtouch (Wish i could have experienced it).
The now lonely site of RealTouchScripts was the launching site of the scripting scene and whilst it was relic of message boards from the past, it fostered a community of dedicated folk all with the same goal in mind, video sync. 3 coming up 4 years later we’ve got a specific site designed for sharing scripts called EroScripts. A new household for active scripters and interactive male sex toy users with the purpose of making it easier to find scripted content and discussion on new software including tips and tutorials that the community feel like creating and sharing. As of right now at the current rate, users are producing 177 scripts a month which for a small site not too far through its life is a pretty good return.
Scripting is a new way to create sequences of actions and whether they are just custom patterns or synced sequences, they offer a good amount of utility to devices that can use them. I wouldn’t be surprised if a female variant to these types of devices arises when the mainstream audience fully notices the capability and that time cannot come soon enough.
For the benefit of everyone wanting to have intense playtime, the advancement of this field of technology will only help serve each of our sexual needs in a time of exploration and play.