mirror of
https://github.com/ncoevoet/ChanTracker.git
synced 2025-04-26 04:51:07 -05:00
commit
7769471237
12
README.md
12
README.md
@ -65,16 +65,16 @@ You should increase the ping interval because when the bot joins a channel, it r
|
||||
|
||||
!config supybot.protocols.irc.ping.interval 3600
|
||||
|
||||
By default, **bot will not stay opped**, but you can configure that globally or per channel:
|
||||
If you want the bot to manage its own op status, you can change the config value :
|
||||
|
||||
!config supybot.plugins.ChanTracker.doNothingAboutOwnOpStatus False
|
||||
!config channel #myChannel supybot.plugins.ChanTracker.doNothingAboutOwnOpStatus False
|
||||
|
||||
By default, **bot will not stay opped**, if it's configured to manage it's own op status, but you can configure that globally or per channel:
|
||||
|
||||
!config supybot.plugins.ChanTracker.keepOp False
|
||||
!config channel #myChannel supybot.plugins.ChanTracker.keepOp True
|
||||
|
||||
If you don't want the bot to manage its own op status, you can change the config value :
|
||||
|
||||
!config supybot.plugins.ChanTracker.doNothingAboutOwnOpStatus True
|
||||
!config channel #myChannel supybot.plugins.ChanTracker.doNothingAboutOwnOpStatus False
|
||||
|
||||
The channel modes that will be tracked are currently defined here (qb, and eI if opped -- only ops can see the e and I lists for a channel):
|
||||
|
||||
!config supybot.plugins.ChanTracker.modesToAsk
|
||||
|
@ -125,7 +125,7 @@ conf.registerChannelValue(ChanTracker, 'announceCtcp',
|
||||
# others settings
|
||||
|
||||
conf.registerChannelValue(ChanTracker, 'doNothingAboutOwnOpStatus',
|
||||
registry.Boolean(False, """bot will never try to change his own op status"""))
|
||||
registry.Boolean(True, """bot will never try to change his own op status"""))
|
||||
|
||||
conf.registerChannelValue(ChanTracker, 'keepOp',
|
||||
registry.Boolean(False, """bot stays opped"""))
|
||||
|
Loading…
x
Reference in New Issue
Block a user