Multi-Element Stroker / AI / Funscript / TCode

[Dimava]

@Arran

You’re creating new axis there. There are only 3 axis physically possible.

Say hi to contraption with two L0 axes

Imagine a Single-Axis Stroker with 2 Sliders

There are scenes where there are two sources of stimulation on the penis. Like the shaft getting a handjob whilst the tip getting a blowjob. Although scripters have workarounds for such scenario it still annoys me that you can’t get to truly replicate that with a single-slider stroker. [miku][3][Cock milked by AIM EE machine animation with sound] Whenever I look at those scenes I think about such a device wiith two sliders. They can merge into one sleeve and move together, but can also separat…

---

@Arran

The whole point of a central standard is so that things stay compatible, custom commands for particular devices don’t achieve that.

But when they change everyone who depends on them has to update
Buttplug still doesn’t support multiaxis

---

@Arran

I agree, but wanted to keep things clear for potential human editors and match current practices. I had a look at some twist funscripts and they all had “twist” in the title and no relevant metadata.

All that’s currently working is {actions, metadata: {bookmarks, chapters}} of funscripts named file.funscript and file.${axisName}.funscript because that’s what always was there
and funscript with {axes: [{id: "L1", actions: [...]}]} because SLR used it and MFP added support for that
Nothing else will work in upcoming two years
metadata.duration lies so often noone uses it
inverted and range ore not supported

---

So it all comes to one thing

• I don’t even understand what you are trying to make paint me a picture in paint