Anyone know what it might take to make a software bridge for lovense?

[TheScriptBunny]

I’m curious if there exists, or interest to create a bridge between Lovense remote and Buttplug.io (seems the simplest option) or MFP? I’d love to use my OSR2 for the games that only use lovense integration instead of having to pull out a whole separate device.

In terms of creation, I’m not sure if it would be easier to generate a dummy device to pull the signals, or something that mimics Lovense Remote’s way of connecting to a game.

Anyone interested?

[Ratattack15]

Best bet would be to ask on the buttplug discourse site as there’s a thread on there about app/game support requesting along with a list of what has gotten support via buttplug or modding. (Presuming you haven’t already checked there first)

[sentinel]

Not exactly sure what you are asking for but it sounds very similar to what is already done.

Have a look at Intiface Central

Compatible Lovense toys IoST Index

List of Intiface Central compatible games GitHub - buttplugio/awesome-buttplug: A list of awesome projects that use the Buttplug Sex Toy Control Library

[Dimava]

@TheScriptBunny

use my OSR2 for the games that only use lovense

So you are looking for Lovence device emulator?
Is “Lovence” integration via Intiface/Buttplug or device specific?

[TheScriptBunny]

Ya, that’s the software I want to recieve the signals from lovense remote integrated games.

Games like Karryns Prison, Third Crisis, etc. These have lovense integration, but you can’t connect with things outside of that ecosystem. Im hoping for something that allows the use of OSR2 or any toy that can connect with Intiface to be used on Lovense only games by somehow hooking that response system or creating a dummy toy that sends the signals to intiface instead

[Dimava]

@Grok 4

How Games That Support Lovense Work

Games with Lovense support integrate interactive sex toys from the Lovense brand (such as the Lush, Hush, or Max) to provide haptic feedback synchronized with in-game events. This is typically achieved through Lovense’s developer tools, which allow game creators to send commands like vibrations, rotations, or contractions to the toys based on actions like character movements, encounters, or rhythm-based mechanics. Here’s a breakdown of how it generally functions:

• Integration Methods:

  • SDK and Plugins: Lovense provides free plugins for popular game engines like Unity, Unreal Engine, Godot, and others. Developers add these to their game code to enable toy discovery, connection, and control. For example, the plugin allows the game to scan for nearby Lovense toys via Bluetooth, pair them, and trigger specific patterns (e.g., intensity levels from 0-20) in response to events like jumps, hits, or intimate scenes.
  • Connection Types:
    • Direct Bluetooth: The game connects straight to the toy using the device’s Bluetooth (often requiring a Lovense USB Bluetooth dongle for better reliability on PC, though standard Bluetooth 4.0+ can work).
    • Via Lovense Remote App: Many games use the Lovense Remote app (available on iOS, Android, Windows, and Mac) as an intermediary. You pair the toy to the app first, then the game connects to the app (often via a QR code scan or local network). The app forwards commands from the game to the toy. This is common in games like 3DXChat or Wild Life.
    • Game Mode in Lovense Remote: Some games activate “Game Mode” in the Lovense Remote app, where the app runs in the background and listens for game signals over a local network or Bluetooth, translating them into toy actions.
  • Synchronization: Commands are event-driven. For instance, in rhythm games like Beat Banger, the toy vibrates in sync with beats or notes. In adult-themed games like Breeders of the Nephelym or Treasures of Nadia, it reacts to animations or player inputs. The Lovense API handles simple commands (e.g., vibrate at level 10 for 5 seconds), keeping latency low for immersion.

• Examples of Supported Games:

  • Beat Banger: Enables Lovense mode in settings to sync vibrations with music beats.
  • Wild Life: Uses Lovense for real-time feedback during scenes.
  • Other titles like The Genesis Order, Pure Onyx, or Unreal Lust Theory often add support via updates or mods, sponsored by Lovense for promotion.

This setup is brand-specific, as Lovense sponsors integrations to promote their toys, limiting compatibility to their ecosystem without additional work.

Can You Make Them Work with Intiface Without Patching the Game?

Intiface (the user interface for the open-source Buttplug.io library) is a hub that supports a wide range of sex toys from various brands, allowing centralized control and protocol translation. However, based on available information from developer forums, documentation, and community discussions, it is not possible to make Lovense-supported games work with Intiface (and thus non-Lovense toys) without patching or modifying the game itself. Here’s why, along with explored alternatives:

• Challenges with Emulation or Bridging:

  • Lovense integrations are proprietary and use a closed API/command set that’s not easily interceptable or spoofable. Games send commands directly to Lovense hardware or via the Remote app, which doesn’t have a public bridge to Buttplug.io protocols.
  • Developers of Buttplug.io/Intiface have explicitly stated that Intiface cannot emulate or pretend to be the Lovense Remote app in “Game Mode” due to the complexity of the Lovense ecosystem and its limited commands. For example, in a Buttplug.io forum thread, the response to this exact idea was “Nope… this isn’t something that Intiface will ever [support].”<grok:render card_id=“c317a3” card_type=“citation_card” type=“render_inline_citation”>
    47
    </grok:render>
  • No universal device emulator exists that can spoof a Lovense toy or API endpoint for games to connect to Intiface instead. Community attempts (e.g., on EroScripts or F95zone) discuss theoretical “hijacking” of the Lovense API to reroute signals, but no working tools were identified.<grok:render card_id=“2a5e78” card_type=“citation_card” type=“render_inline_citation”>
    46
    </grok:render> Such solutions would likely require reverse-engineering, which isn’t available as a simple emulator.

• Why Not Via Existing Tools?

  • **Intiface Game Haptics Router (GHR reroutes gamepad rumble to toys via Intiface doesn’t help here, as Lovense commands aren’t rumble-based and aren’t routed through gamepad APIs.
  • Lovense Connect Support in Intiface: This allows Intiface to control Lovense toys, but it’s the opposite of what’s needed—it lets Intiface act as the controller, not the receiver for Lovense-specific game signals.<grok:render card_id=“937ca0” card_type=“citation_card” type=“render_inline_citation”>
    57
    </grok:render>
  • Mods and Plugins: Compatibility often requires game-specific mods (e.g., for Koikatsu or Honey Select 2), which count as patching. For instance, LoveMachine or GameInterfaceForToys add Buttplug support to certain games but modify files or inject code.<grok:render card_id=“7ea612” card_type=“citation_card” type=“render_inline_citation”>
    4
    </grok:render> Communities like EroScripts.com list such mods, but they violate your no-patching condition.<grok:render card_id=“17b29d” card_type=“citation_card” type=“render_inline_citation”>
    46
    </grok:render>
  • App-Based Workarounds: If the game uses the Lovense Remote app (e.g., via QR or LAN), there’s no bridge to redirect those commands to Intiface. Tools like BuzzyBody emulate Lovense toys within Intiface for other apps, but this doesn’t let games connect to Intiface as if it were Lovense.<grok:render card_id=“686671” card_type=“citation_card” type=“render_inline_citation”>
    64
    </grok:render>

• What If the Toy Is Lovense?: If you’re using a Lovense toy with Intiface, yes—you can connect the toy to Intiface directly (via Bluetooth or Lovense Connect app forwarding), but the game would need to support Buttplug protocol, which Lovense games don’t. This doesn’t help for using non-Lovense toys.

In essence, while Intiface is powerful for multi-brand control, Lovense’s closed design prevents seamless bridging without game alterations. If a specific game has community Buttplug integration mods, that’s the most common workaround, but it involves patching. For native cross-compatibility, you’d need developers to add Buttplug support directly. If this doesn’t cover your setup (e.g., a particular game), provide more details for further checks.

So one needs to hack into their api so see what it does

[VladTheImplier]

You could use wireshark to watch the API calls and attempt to reverse engineer it.

The issue is that it’s probably TLS encrypted which means needing to hack your device and then try to reverse engineer it.

I explored that idea with the handy to try and reverse engineer the API so I could write a locally hosted API but I never got around to it.

[TheScriptBunny]

Thanks @Dimava for the great source. Guess I’ll need to focus more on learning to mod to support EDI and Buttplug.io.

[Dimava]

Start with getting the dnspy Install dnSpy with winget - winstall and opening Assemblu-CSharp in it and look into what are you looking for (probably lovense library calls) (with search tool ofc)

Also you can tell me the game some chance my games independent tools do work with it already

[TheScriptBunny]

Specifically looking into Karryns Prison and Third Crisis. I know there’s a thread here for KP working on Buttplug.io. its not finished though

[diglet]

I think there used to be code for an esp32 lovense device emulator on github, but I can’t find it anymore. From what I gather lovense logs the device ID of every device that uses their service, so they can shut down any such efforts fast.

[sentinel]

@diglet

From what I gather lovense logs the device ID of every device that uses their service, so they can shut down any such efforts fast.

That sucks
It’s insane that it isn’t enough that you pay for a product. I can’t even see that Lovense has monetized their remote control app. I assume they are just another protectionist that refuse fair use of their products. Soon we need laws for integration similar to rights to repair laws. I wonder if EU Data Act is applicable in some way. The issue is that we need control, not only data.

[pjp40003]

You would have to edit the hosts file to intercept the API connection (handshake) and have a reverse proxy decrypt the commands coming from the server and translating them to intiface. The problem is you would also need to find the decryption key in the device’s memory like @VladTheImplier mentioned.

So I think it would be easier to just mod the game itself to also send commands to intiface

[pjp40003]

I’ve taken a quick look at Karryns Prison and it looks like the whole Lovense logic is implemented inside the www/js/plugins/RemtairyLovense.js where you could translate the lovense api commands to intiface. For Third Crisis you’d have to modify the LovenseRemote.dll

[TheScriptBunny]

Looks like Karryn’s Prison has Mod Progress, but nothing mentioned in almost a month

[ajtrader23]

I’d like to ping this. I have a Handy, and I thought that I could use it with Unreal Lust Theory. But it’s all Lovesense, and how STUPID that such a niche market to begin with has an incompatible mac/pc coke/pepsi split.

Has anyone figured out yet how to use a handy in Lovesense-only games?

[Bella]

I’m tired of vendor’s proprietary lock-in games, so it will be a bit before I drop another $100 or so on another Lovense device. Their software largely sucks, too, so until they’re willing to let others write decent apps that include not just their devices, I’ll pass. It’s bad enough that they demand their own Bluetooth dongle for their apps, refusing to work with embedded Bluetooth, yet Intiface works just fine with a generic Bluetooth interface. Lovense: Why you so … Sony?

FWIW: There’s a Lovense dev channel on discord. If I wasn’t swamped, I’d look into doing more with what I can glean there, but it seems that either you patch the Lovense only game to use Intiface, someone makes a Lovense device emulator that fools Lovense Remote, or someone hacks the API in Lovense Remote and comes up with a replacement that works like Intiface Central to apps that are hunting for Lovense Remote.

Maybe the people at Buttplug.io can make a similar drop-in code to make modding games to include Intiface in parallel to Lovense considerably easier. It would be nice to see mods to add Intiface functionality that worked with mod managers like Vortex. Hell, it would be nice if the guy who wrote ‘Playful Plugins’ to incorporate Intiface Central to his work, too.

[pabr]

As far as I know Lovense games will typically implement integration in one of two ways:

1. “Game Mode” through the Lovense Remote app (ex: Karyn’s Prison, Third Crisis)
2. Cloud Mode through the Lovense Remote app (ex: Treasures of Nadia, the crappy nutakku idle games)

I honestly don’t know a lot about the cloud mode because it’s proprietary BS as others have already stated. But the Game Mode seems to be a relatively straightforward REST API.

“Game Mode”

Game Mode in the Lovense Remote app starts a basic HTTP(S) server with a REST API for controlling the toys. The game then sends REST commands over LAN to your phone. This REST API is documented in Standard API/Step 3 Standard API | Developer.

All games programmed using this method that I’ve run into have an IP address and port settings for connecting to your phone. Most games programmed using this method seem to have a toggle for HTTP vs HTTPS.

So what one could do is write a conversion HTTP server that implements the Lovense REST API. The easiest thing I could think of doing would then be to convert the Lovense REST API commands into calls to Intiface Central using one of their libraries that wrap the web socket protocol (this is a very basic example from the buttplug io documentation Example Application | buttplug.io). This HTTP server would also need to handle converting the Intiface Central toy definitions into something that the Lovense apps would understand. So special care would need to be taken on the GetToys command for sure, but a similar problem probably exists for other endpoints where there aren’t 1-to-1 conversions.

If this theoretical conversion HTTP server existed that handled doing all of these conversions then in any application that has Lovense integration and prompts for an IP Address and port number you could instead point it at this conversion server running locally on your PC.

I haven’t had the time to do much with this information, but hopefully its helpful if someone else chooses to embark on this journey

[Furimanejo]

Hi, Playful Plugins’ dev here

The Lovense game mode API that most games use is very spoofable, any developer could do it by sniffing the HTTP messages with Wireshark

Dunno how legal that would be tho and Lovense is known to be litigious about their IP/patents

[TheScriptBunny]

Ideally I’d grab the handshake that shows something like the Solace Pro connected, then route it into MFP or whatever is needed to interface with the OSR2.