You could replace "#ChanName" yourself with $Chan, otherwise every time you wanted to run it in any channel you would have to keep going back through the code and making chan name changes...
It has similar schemes to those in some older bot scripts, like the Ultimate Project ones. The names on the colour schemes are also of the same variety...
Nice try at a variation. The original 8ball is not set on text triggers other than the command 8ball so the responses come out at random. You\'ve added some specific triggers- nice try
Notices are good because they avoid clogging the channel each time a person joins- You could develop this code by creating a channel entry list which would avoid writing new lines for each entry and part
shilex, load the script into your bot. Unfortunately to add and remove users this script does not allow you to do that remotely, so you have to go into the bot and right click on nicks in the nicklist in a channel to grant them access or remove it, or otherwise type it in yourself. The other commands are all remotes... you can access these under your own nick and typing the commands to the bot. For example, in the channel, you would type !op Friend, and your bot would give ops to the nick Friend.
Your snippet is prettier than your pic ... heehee.... You could tidy up a little (for example remove the unnecessary /\'s before each \"write\") Otherwise pretty ok stuff
Your snippet is prettier than your picture heehee... You could clean up the snippet a little (for example take out unnecessary / \'s before each write). Otherwise... pretty ok stuff
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...
Although you have already correctly introduced the idea that you must type !Marry <nick> <reason>, it seems kinda strange to be asked by the snippet for the reason after already having given it. You could set the nick who did the command !Marry <nick> to then be Nick 1, and then when the snippet asks \"why be married\", allow only Nick 1 to respond ... perhaps through a hash table recording responding nicks (?). Then nick 1\'s response will be given in the following responses you have designed.... makes the snippet even for interactive.
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...
You realise that even though you have changed the command line to be !8skull that this is essentially a copied snippet, complete with spelling mistakes that from the original ... eg \"Definantly\" should be \"Definitely\"....
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:
@sadistic_sin One of the difficulties with your current coding is that it is very basic, and I appreciate the fact that you are learning, however, posting a lot of one to two line simple scripts on this site is not likely to help you develop your scripting since they are all \"at the same level\". Take some time to consider how to develop the ideas you have into something more composite.
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:
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:
Code
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:
Code
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.
Another way around it is to take out the channel options so instead of requesting it in a channel where the game is not available, its played in the active chan instead. :)
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.
