X-Git-Url: https://jfr.im/git/solanum.git/blobdiff_plain/212380e3f42f585dc1ea927402252eb943f91f7b..591342826a8566c3a5426e16d63afb96f0d6e097:/doc/collision_fnc.txt

diff --git a/doc/collision_fnc.txt b/doc/collision_fnc.txt
index d8fafebe..397c0679 100644
--- a/doc/collision_fnc.txt
+++ b/doc/collision_fnc.txt
@@ -6,7 +6,8 @@ Nick collision FNC performs a forced nick change to the user's UID instead
 of a kill. The criteria for which user may keep the nick are the same as
 before. Server notices will say the clients are being "saved" instead of
 "killed". The client will get a 043 numeric, like this:
-:<server> 043 <uid> :Nick collision, forcing nick change to your unique ID
+
+:<server> 043 <nick> <uid> :Nick collision, forcing nick change to your unique ID
 
 The following conditions must be fulfilled:
 
@@ -37,5 +38,10 @@ The SAVE message is used for propagation to the target's server, and also
 in several other cases if the destination supports SAVE. In other cases, a
 normal nick change or introduction with the UID as nick is sent.
 
+The TS of the UID nick is 100. This is necessary to ensure nick TS is always
+the same on all servers for each nick-user pair, also if a user with a UID
+nick changes their nick but is collided again (the server detecting the
+collision will not propagate the nick change further).
+
 -- 
-$Id: collision_fnc.txt 276 2005-10-02 20:23:15Z jilles $
+$Id: collision_fnc.txt 3422 2007-04-22 14:35:28Z jilles $