I        This condition is triggered when a client blasts a text message to their peer (another client) via a channel.

It takes one parameter, which is the subchannel to filter this event for.


The channel the message was sent on and the sending client are auto-selected for you at the start of the event.


This condition is not enabled by default

In both server variants, this condition is disabled by default, and will not trigger. Peer messages will be passed through, just Fusion won't be notified. This is faster than triggering them.


In Relay Server, you must enable the condition using the Enable/disable conditions > On message to peer. Once the action is run, triggering of channel message conditions cannot be disabled again.

If the condition is triggered, you can drop the message using On interactive condition > Drop message (for on message to channel/peer).


With Blue Server, during this event, the receiving peer can be selected by the Client > Select receiver (for "on message to peer") action, but in Relay that action is broken and selects the sender.

Dropping by action will only work in Blue Server if you set peer messages to wait for Fusion events to handle them, using the Enable/disable conditions > On message from client to peer action. You can also drop all peer message types by setting the handling to an auto-deny mode.

Blue Server also uses a "received by client" Unicode allowlist, set by the (Advanced) Set Unicode allowlist action, and regardless of the handling mode, channel/peer text messages that do not match the allowlist will be dropped automatically, without Fusion message events being triggered.