Avatar and contact configuration

Connect OSC and use the incoming message log to identify the addresses and values that your avatar sends. Parameter names come from the avatar; the plugin does not create them for you.

Avatar parameter changes

Use Avatar Parameter Changed to react to an avatar parameter. Copy the parameter name from the received address, then set the node's filter and matching properties. Use its typed value outputs in comparisons or conditions before continuing to a device action.

If you need an address outside the avatar parameter pattern, use OSC Message Received and configure its address filter instead.

Contacts and PhysBones

Use Contact / PhysBone Touched for the parameter emitted by the contact or PhysBone. Set Parameter Name, Threshold, and Fire On according to the values shown in the incoming log. Check both the active and inactive values before connecting an action, so the flow reacts to the intended edge or state.

Start the flow after saving it. If raw messages arrive but this trigger does not fire, compare the parameter name and threshold with the actual incoming values. See the node reference for its matching rules.

Send messages back to VRChat

Send OSC Message sends a configured address and arguments. Match the argument type expected by the destination: a boolean, number, and string are different OSC values.

Send Chatbox Message formats a chatbox message. Inspect action result outputs and avoid a flow that repeatedly sends messages in response to its own outgoing changes.

Contributors

Thank you to everyone who has helped improve this documentation.