This page is intended for developers. If you're looking information on for how to link servers you should refer to the spanningtree module) page instead.
ENCAP
Encapsulates a message to the specified target. If the target does not exist or the encapsulated message type is unknown then the message is non-fatally dropped.
Connection Phases
This message can be used in the following connection phases:
| Connection Phase | Usable? |
|---|---|
| Connecting outbound | ❌ |
| Authenticating outbound | ❌ |
| Authenticating inbound | ❌ |
| Fully connected | ✔️ |
Syntax
:<uuid> ENCAP <target> <message> [<parameters>]+
| Parameter | Description |
|---|---|
<uuid> | The unique identifier of the server or user that sent the message. |
<target> | A server identifier or glob pattern for a server name for the target server. |
<message> | The name of the message which is being encapsulated. |
<parameters> | The parameters for the specified message. |
Example Usage
Sends a notice to all users on server 36E:
:36DAAAAAA ENCAP 36E NOTICE $* :Hewwo!
Sends a notice to all users on servers matching *.example.com:
:36DAAAAAA ENCAP *.example.com NOTICE $* :Hewwo!