From 72eb04ebc6d087c90139c3a9e679b35bc1ab1289 Mon Sep 17 00:00:00 2001 From: James Lu Date: Wed, 13 Jul 2016 18:53:51 -0700 Subject: [PATCH] docs/t: add SVSNICK to hooks reference --- docs/technical/hooks-reference.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/technical/hooks-reference.md b/docs/technical/hooks-reference.md index 6bb307b..72d5c00 100644 --- a/docs/technical/hooks-reference.md +++ b/docs/technical/hooks-reference.md @@ -130,6 +130,10 @@ The following hooks represent regular IRC commands sent between servers. - **SAVE**: `{'target': 'UID8', 'ts': 1234567892, 'oldnick': 'Abracadabra'}` - For protocols that use TS6-style nick saving. During nick collisions, instead of killing the losing client, servers that support SAVE will send such a command targeting the losing client, which forces that user's nick to their UID. +- **SVSNICK**: `{'target': 'UID1', 'newnick': 'abcd'}` + - PyLink does not comply with SVSNICK requests, but instead forwards it to plugins that listen for it. + - Relay, for example, treats SVSNICK as a cue to force tag nicks. + - **VERSION**: `{}` - This is used for protocols that send VERSION requests between servers when a client requests it (e.g. `/raw version pylink.local`). - `coreplugin` automatically handles this by responding with a 351 numeric, with the data being the output of `utils.fullVersion(irc)`.