This page is intended for developers. If you're looking information on for how to link servers you should refer to the spanningtree module (v4 docs, v3 docs) page instead.
SVSJOIN
This message is provided by the services module. Before sending it you should do one of the following:
- Check that the services message is present in
CAPAB MODULESorCAPAB MODSUPPORT. - Encapsulate it with
ENCAPif the message being dropped is tolerable.
Forces the specified user to join a channel. If an empty key is specified then override any modes which might prevent the join.
Connection Phases
This message can be used in the following connection phases:
| Connection Phase | Usable? |
|---|---|
| Connecting outbound | ❌ |
| Authenticating outbound | ❌ |
| Authenticating inbound | ❌ |
| Fully connected | ✔️ |
Syntax
[:<sid>] SVSJOIN <uid> <channel> [<key>]
| Parameter | Description |
|---|---|
<uid> | The UUID of the user to join to the specified channel. |
<channel> | The channel which the user is being joined to. |
<key> | The secret key used for joining the channel. |
Example Usage
Joins user 36EAAAAAA to #wibble:
:36D SVSJOIN 36EAAAAAA #wibble
Joins user 36EAAAAAA to #wibble with a channel key:
:36D SVSJOIN 36EAAAAAA #wibble :secret
Joins user 36EAAAAAA to #wibble overriding any modes:
:36D SVSJOIN 36EAAAAAA #wibble :
History
1206
This message is now provided by the services module instead of the spanningtree module. You should check this module is loaded before sending. If this message is received from a link using the 1205 protocol it will be encapsulated before being forwarded to the target.