$Supports

From NMDC Protocol

$Supports

Syntax

$Supports <feature1>[ <feature2>[ <featureN>]]|

Extension
Supported By: DC++ 0.17+ (Client to Client), DC++ 0.300 (Hub to Client)

Description

This command is used to negotiate protocol extensions. To indicate that the client or hub has at least one protocol extension available, it must send a $Lock that begins with EXTENDEDPROTOCOL. If the remote side also supports protocol extensions, it may send $Supports. It must, however, precede $Key.

Notes:

• EXTENDEDPROTOCOL should not be sent if the hub/client supports no extensions
• A blank $Supports is not permitted
• Spaces aren't allowed in feature names
• For client extensions, the name of the feature should be the same as the command.
• Hubs usually want to receive Supports before answering the Lock challenge with a key. So first packet to hub should be: $Supports ..|$Key ..|$ValidateNick ..|

Known Extensions

Client to Hub
NoGetINFO
NoHello
UserIP2
UserCommand
TTHSearch
OpPlus
Feed
MCTo
HubTopic
ZPipe0
ZLine
BotList
QuickList
ClientID
IN

Client to Client
BZList
MiniSlots
GetZBlock
XmlBZList
ADCGet
TTHL
TTHF
ZLIG
ClientID
CHUNK
GetTestZBlock
GetCID