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.
SVSHOLD
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.
If <duration> and <reason> are specified then place a services hold on the specified nickname. The <duration> may be specified as a number of seconds or as a duration in the format 1y2w3d4h5m6s. If the duration is zero then the services hold will be permanent.
Otherwise, if just <nick> is specified, removes a services hold on a nickname.
This is similar to a Q-line only it is more suitable for nickname enforcement as:
- It can only be applied by a services server.
- It does not notify server operators.
- It can be bypassed the user of a registered account.
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>] SVSHOLD <nick>
[:<sid>] SVSHOLD <nick> <duration> :<reason>
| Parameter | Description |
|---|---|
<nick> | The nickname that a services hold is being placed on or removed from. |
<duration> | The duration of the services hold. |
<reason> | The reason the services hold was placed. |
Example Usage
Places a services hold on Sadie wth the reason "Reserved for a registered user":
:36D SVSHOLD Sadie :Reserved for a registered user
Removes a services hold on val:
:36D SVSHOLD val
History
1206
This message is now provided by the services module instead of the svshold module.