Connection modes
Why Vfinity offers two ways to read your TikTok room, and which one to use.
The TikTok LIVE card has a Connection Type choice. Both options end with the same events reaching your mappings; they differ in who does the talking to TikTok.
Built-in bridge
Vfinity ships a small background process that connects to TikTok itself. You give it your username, it finds your room, and it forwards what happens there.
Use this unless you have a reason not to. It needs nothing else installed and nothing else running.
Custom WebSocket
Vfinity connects to a connector you are already running, at a host and port you give it. The default is localhost:21213, which is where TikFinity listens.
Use it when:
- You already run TikFinity and would rather have one connection to TikTok than two.
- You wrote your own connector.
- The built-in bridge cannot reach TikTok on your network but another tool can.
Custom mode does not start the built-in bridge. If your connector is not running, nothing arrives, and Vfinity will sit there connected to nothing.
What differs downstream
Nothing, on Vfinity's side. Mappings, throwing and the widgets behave identically.
What can differ is what arrives. The built-in bridge forwards a known set of events. A third-party connector forwards whatever it forwards, so if it does not send shares, you have no shares to react to.
Changing between them
Disconnect first. Vfinity refuses to change the connection type while connected, because switching mid-flight would leave a bridge process running with nothing reading it.
Your username and your custom host and port are stored separately, so switching back and forth does not lose either.
The trigger API is not a connection mode
The Trigger API card is a third connection, and it is unrelated. It carries events from your own tools, not from TikTok, and it runs alongside whichever TikTok mode you chose. See Trigger Vfinity from your own app.