Very, very simple snippet
All it is is you can make a list of admins or mods for your bot and when they type
!botoff
It'll turn your bot off
Of course there is no
!boton
feature because when you type !botoff it disables all of your scripts ;p
Also by getting rid of
if ($nick == NICK) || ($nick == NICK1) || ($nick == NICK2) {
Then anyone can type !botoff
Which is not advised
Also to turn your bot back on just type
/remote on
And also remember to change NICK, NICK1, NICK2, NICK3!
And to add more people to the list of peple allowed that command add
if ( $nick == NICK ) {
Right before the line
remote off
And to get rid of one or more just get rid of an
if ( $nick == NICK ) {
line
on *:text:!botoff*:#: {
if ($nick == NICK) || ($nick == NICK1) || ($nick == NICK2) {
remote off
}
Hmm that could be handy.. but once remotes are off the person cant turn them back on lol.. I suggest using a var on every script you have such as;
on :text:!bot off:#:{
if ($nick == NICK) || ($nick == NICK1) || ($nick == NICK2) {
set %off enabled
}
}
on :text:!bot on:#:{
if ($nick == NICK) || ($nick == NICK1) || ($nick == NICK2) {
unset %off
}
}
And place this in all scripts;
if (%off == enabled) { halt }
elseif { your script here
}
Just a thought this requires more work tho :)
I\'m wondering why you would want to turn all your bot scripts off and still have it on line when you could not turn it on again... its probably better to just make your bot quit the server. As dmdlflore suggests, grouping scripts is good because then you can turn off collected features, for example, turn off all the reactive and speech modes when they get annoying and leave protections on. Also, have access levels to the bot is important, as also suggested. I cannot see any practical application for this snippet.