Thanks for the amazing tool @ZeroScripts for Cubilink v3.
I will eventually share some plugins I used in this game when tackling some problems such as unity log (delayed or not showing scene name to bind), parameters didn’t refresh and stuck, and filler script didn’t get loaded. I will share those plugins once I also tested out perfect in other games.
When trying to connect CubiLink to intiface it keeps giving me timed out.
This is happening for all 3 of your most recent games. I’m using ws://localhost:12345 as my connection and this even works in other things (like connecting Edi to intiface via ws://localhost:12345) but it times out and fails on CubiLink
Please if you have help for this at all id really appreciate it
Hey — Thanks for your support and sorry you’re hitting this.
That timeout is almost certainly a Buttplug version mismatch, not a URL problem: CubiLink uses a newer Buttplug message spec than apps like Edi do, so an older Intiface Central never completes the handshake and CubiLink gives up after ~5s. Two ways to fix it:
Easiest / what I’d actually recommend — skip Intiface and connect over serial. If your stroker plugs in as a USB COM port (OSR2/SR6/SSR-style), you don’t need Intiface at all:
In CubiLink’s connection settings, set the output mode to Serial.
Pick your device’s COM port (find it in Windows Device Manager → Ports (COM & LPT); baud is 115200). If you choose the wrong one, CubiLink will list the available ports in its error.
That’s lower-latency and it actually preserves all the motion axes — the Intiface path averages a few of them together, so serial feels better anyway.
If you’d rather stay on Intiface (e.g. a Bluetooth-only device): update Intiface Central to the latest version — that’s the most likely fix. Also try the URL as ws://127.0.0.1:12345 instead of ws://localhost:12345, and make sure your device is scanned/connected inside Intiface Central before CubiLink connects. If you open the game’s BepInEx/LogOutput.log and search for “Intiface connection failed”, it’ll tell you the exact reason — it’ll literally say either “too old, please update,” “timed out… make sure Intiface Central is running,” or “connection refused… listening on the configured port.”
Let me know which device you’ve got and I can point you more precisely.
I have a handy, would i be able to do the Serial thing with a handy? i dont think so right?
When i tried the default ws://127.0.0.1:12345 it didnt work, didnt even do the stutter thing like it was trying to work.
I do have an older version of intiface because i think it was required for somethin a while ago. Lemme try a newer version of intiface
Edit: Cool yeah, a newer version of intfiface worked.. is there any way of having multiple installs of intiface that both work though? cos id like to go download 2.2.2 again to keep it somewhere for other things
also, for shinobi i remember people posting about it having a little different process for script swapping or something which the others dont have bcs they’re just AIO packages right?
what would i need to download for Shinobi ontop of what was included if you dont mind me asking while i have you here
yeah newer intiface sorted it, cheers — makes sense, the handy only talks through intiface anyway so the serial option was never gonna apply to it.
one thing though: can you actually have two intiface installs both working, or is it one-at-a-time? wanna grab 2.2.2 again to keep around for other stuff.
(and sorted shinobi btw — newest update has solved the problem, just drag-and-drop from the patreon file, except if you’re on the non-english version, you just skip the Game Data folder when dragging. no biggie.)
