From d2cf0cf8a648ca74a77f55028bbf9b0e81148c64 Mon Sep 17 00:00:00 2001
From: Nicolas Coevoet <ncoevoet@users.noreply.github.com>
Date: Tue, 5 Jan 2016 12:33:19 +0100
Subject: [PATCH] Update README.md

---
 README.md | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 56a61c7..7028fa4 100644
--- a/README.md
+++ b/README.md
@@ -105,13 +105,13 @@ The command used by the bot to op itself is editable here:
 
 Where $channel and $nick will be replaced by targeted channel and bot's nick at runtime, so you could replace it with :
 
-        !config supybot.plugins.ChanTracker.opCommand "PRIVMSG ChanServ :OP $channel $nick"
+    !config supybot.plugins.ChanTracker.opCommand "PRIVMSG ChanServ :OP $channel $nick"
 
 You can also tell the bot to use ChanServ for quiet and unquiet, if it has +r flag, on freenode:
 
     !config supybot.plugins.ChanTracker.useChanServForQuiets True
     !config supybot.plugins.ChanTracker.quietCommand "PRIVMSG ChanServ :QUIET $channel $hostmask"
-    !config supybot.plugins.ChanTracker.quietCommand "PRIVMSG ChanServ :UNQUIET $channel $hostmask"
+    !config supybot.plugins.ChanTracker.unquietCommand "PRIVMSG ChanServ :UNQUIET $channel $hostmask"
 
 For more readable date information in output, you should change this:
 
@@ -161,9 +161,12 @@ By default, if the bot is asked to set a ban (+b), it will also kick affected us
 
     !config supybot.plugins.ChanTracker.kickMode
     !config supybot.plugins.ChanTracker.kickMessage
-
+    !config help supybot.plugins.ChanTracker.kickOnMode
+    
 The bot will remove exception modes (that is exempt e, or invite exempt I) for people banned if 'doActionAgainstAffected' for given channel is True.
 
+ChanTracker is trying to resolve ip behind host, but that can affect performance or freeze the bot due to socket's calls, if you use supybot.plugins.ChanTracker.resolveIp to True, you should set supybot.debug.threadAllCommands to True to avoid that.
+
 ## Channel Protection ##
 
 The plugin has a lot of built-in channel protection features that can be enabled either individually and per channel, or globally:
@@ -179,6 +182,7 @@ The plugin has a lot of built-in channel protection features that can be enabled
 - nick: nick change spam
 - cycle: join/part flood
 - massJoin
+- clones detection
 
 You should tweak settings to fits your needs, do not use default values. It really depends channel's population and usage ...