Connecting SexLab to real world devices

[urhent]

After getting back into skyrim on a whim, I discovered how expansive and devious this mod community is and I love it. I also really like the gameplay loop of defeat - get fucked - lose stuff/status/freedom - continue a lot more over the defeat - quickload - repeat gameplay loop. So I was thinking about how to take all this to the next level.

 

In recent years, more advanced sex toys have also hit the market. I want to combine them with SexLab and other mods. I'm a developer but my only experience with modding bethesda games was briefly with Morrowind so it's been a while. I'd like to hear your thoughts and perhaps get some guidance for my idea and approach.

 

The idea

 

Have the various mods hook up to various real-life sex toys, then react to events in the game. A sex event could trigger various devices. You can configure which devices respond to various events. For instance, an automatic masturbator could get to work when intercourse plays out in general, a vibrating buttplug could trigger when your character gets fucked in the ass or has a shock plug activated, vibrating nipple clamps could activate when the in-game counterparts activate, and for the more adventurous people you could even have a fucking machine go to town on one or more of your holes. Get whipped in the game? Get whipped in real life! Get milked in the game? get milked in real life! Get amputated in the game? Get am- err let's not go there yet.

 

This adds more risk and incentives to do or not do things in-game. It creates a bond with your character because you might or might not want certain things to happen to you. Both good things and bad things. It makes you think twice exploring a bandit hideout when you're tired, hurting and you've lost your weapon. Can you endure another few minutes of continuous action if things go bad? Do you really want to have that mechanical dildo way up your ass after they belt you with plugs?

 

I'm not sure how far we can take this, both from a practical perspective (you still have to be able to play the game when two or three fucking machines are blasting you) and from a dear god why would you want that perspective but there's only one way to find out! I think it'll be very interesting and fun to see how this changes the way you play the game.

 

Development

 

I've discovered the buttplug.io project, which seems to support a variety of devices. Mostly vibrators, but also some masturbators. I have no idea how well this works but I've ordered something to try it out with and it'll be here in a few days. Going from my code to the device seems to be easy to do, so that's not the problem. Going from the mods to my code is a problem. My very first approach will be to just read the SexLab log file in real time and hook into the scene stage events. However, I don't get any other information such as which animation is running, or even which holes are used and how, etc. It's good enough to get started with but later on I want more advanced stuff like that, but also when plugs, piercings and shock collars are active, etc.

 

 

How far can I get developing this without making a SKSE plugin? I don't think I can keep relying on default modlogs so I either have to log events via my own plugin, or create a SKSE plugin/program that does that plus a lot more. Either way, then I can pick it up in my own application that uses the buttplug API to control any devices connected. I'll have to research this by myself but if there's anyone that can push me in the right direction it's much appreciated! For the basics, I should have something somewhat functional soon after I receive my package.

 

Has anything like this been done before? Is anyone interested in something like this? Perhaps even willing to push me in the right direction with modding? 

 

I'd love to hear your thoughts! Thanks for reading!

 

[Ed86]

 

[Ed86]

you will probably need to rewrite whole DD vibration script

 

sexlab:

SexLabFramework Property SexLab Auto
 

Event OnInit()
    RegisterForModEvent("AnimationStart", "OnSexLabStart")
    RegisterForModEvent("AnimationEnd", "OnSexLabEnd")

EndEvent
 

 

Event OnSexLabStart(String _eventName, String _args, Float _argc, Form _sender)
    Actor[] actorList = SexLab.HookActors(argString)
    sslThreadController controller = SexLab.HookController(argString)
    sslBaseAnimation anim = SexLab.HookAnimation(argString)
    
    if (anim.HasTag("Vaginal") || (anim.HasTag("Anal")))
        do stuff

EndEvent
 

 

[urhent]

Oh wow you've helped me a ton by showing me that mod, it seems to have a bunch of things that I need! I'll try it out. Also it seems other people have already started working on integrating it with buttplug.io in that thread, that's really cool to see! Don't know why I didn't find that when I did a quick search before posting this today.

 

Skybutt's source code seems similar to what I have created so far (except I named my project skyplug lol), but my approach would be more flexible with devices. I'm gonna try the controller mod to see what's logged and continue from there. Thanks a lot!

[WaxenFigure]

Check out this thread: There's a lot more to it than the title indicates.

 

 

[urhent]

Thanks to the logging of the controller mod I've managed to create a very rough prototype of my tool!

 

Right now it should be able to support any number of physical devices simultaneously, where each device can have its own prioritized ruleset and actions based on in-game events. It supports vibrations, rotations, linear motion and the fleshlight launch, but they are untested or not working exactly as expected/intended so it still needs some work.

 

So far the only game events supported are when a scene takes place, whether you are wearing any plugs/piercings/strapon, and when an orgasm takes place. I've got a bunch of other events ready to go but for most of them I'll need more logs. I also haven't added dynamic support for specific scenes or stages (but I do keep track of them), right now it only has support for a scene that is happening and if it's vaginal or anal, but in the future I might look into supporting detailed custom actions for specific animations.

 

In short, most of the work on the external program is done and it only needs some more polish and a few extensions. I still have to work on extending the in-game log output to support all possible events and then it's pretty much feature complete for a first release. I'll quietly keep working on it until it's ready.

 

If there's anyone that wants to help me test it, please let me know! Prerequisites for testing are that you have at least one buttplug.io compatible device, you know how to set up a local intiface server (for now), and you don't mind having to deal with a functional but unfriendly user interface.