You create a text file called trivia.txt either with questions downloaded or ones you have self-researched. You save / keep the file in the same place that you would store this snippet (even if you have loaded it straight to your remotes, you will find it in the files where yours or your bots files are kept- e.g. C:/Program Files/BotName/mIRC ). Then the snippet will read the file from within the same location...
They will be the same commands as yours if you include the commands snippet as part of larger commands. At the moment this snippet has nothing to offer, however, if you include your acupuncture snippet, and along with your stick snippet, and with the other snippets, you would have commands to place in there. The commands won\'t be different since they are already incorporate into the other snippets. It doesn\'t need to be made editable...
@sadistic_sin With all the action command snippets, they could be drawn together into one package, something similar to:
on *:TEXT:*:#: {
if (!cake isin $1) && ($2 isin $chan) { describe $chan puts cake in $2 \'s mouth }
elseif ($2 !isin $chan) || ($2 == $me) { describe $chan throws cake at $nick instead } {
if (!acupuncture isin $1) && ($2 isin $chan) { describe $chan $2 gets needled }
elseif ($2 !isin $chan) || ($2 == $me} { describe $chan $nick gets stabbed instead }
}
else { return }
}
Something like that for example anyway .... hard to think about it while I\'m at work ;)
Unfortunately, this one would not count as a snippet. To develop this, you could have included a list of actionable commands, for example, put together your acupuncture and stick script then had the commands to refelct the commands in process... for example, after placin in your actionable snippets, then place in:
on *:Text:!commands:#: {
msg $nick The commands are: !stick <nickname> to poke a stick; !acupuncture <nick> for needles
Rather than single line snippets, you could try incorporating a few of your ideas into one larger \"package\". You could add to this, as it stands, for example:
on *:TEXT:!stick*:#: {
if ($2 == $null) { msg $chan There\'s no way thats happening pal }
elseif ($2 == $me) { msg $chan no $nick, you do it yourself }
else { describe $chan gently pokes both of $2\'s eyes out with a stick }
}
If you can\'t get back to the channel on part, I\'m not sure anybody will know when to invite you back. If you only want it to work in the active channel ($2), then rather than enter the channel name: eg. !gtfo #channelname, it would be simpler to have something like:
on *:text:!gtfo:#: {
part $active ...
since the snippet already only identifies the entry of text and the parting of the specified channel ($2). However, if you\'re bot is in 20 channels and you only want it to part a specified channel, the channel entry remains, but rather than having to go to that channel and type !gtfo <#chan>, you could msg the bot with the command:
on 500:text:!gtfo*:*: {
part $2...
This allows both a channel command and a private msg command to the bot. I have included for example, user level access 500, because if there are no access levels, as this currently stands, anybody could tell your bot to !gtfo...
The active channel will the one where the bot/snippet is located and the game is requested. I was suggesting take out the invitations to join particular channels on the snippet, so it will be played either in chans where bot is active, and instead have a separate request bot snippet.... just an idea to avoid the complicatios of query msgs to commence games where the bot/snippet is not available in the chan requested.
Having %kill2 with two different random responses could be a difficulty, although I can see that one is successful and the other unsuccessful...
A good interactive game idea (a little brutal for me though ;P). You might consider a random reading of active nicks on the nicklist and the game once started, takes active nicks at random and has its own murder game running? Just an idea....
Linesftw, there is no kick in the snippet, so you don\'t have to worry about that...
SpotRedDog, you enter the nick manually from those already in the channel, as in !kill SpotRedDog :D ... no need for the menu option to play the game.
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.
alexxx, read the authors note and the installation.txt