Jump to content

Search the Community

Showing results for tags 'Eggdrop'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • TclScripts.Net
    • Announcements & Other Stuff
    • Forum Bugs, Forum Suggestions
  • Eggdrop & TCL
    • Eggdrop Help
    • Tcl Scripts
    • BlackToolS Script
  • Off topic
    • How to..
    • General discussions
    • Interesting Websites
  • Graveyard
    • Archives


  • BLaCkShaDoW ProductionS ®
  • Other
  • Games
  • Statistics
  • Security
  • Eggdrop
  • Modules


  • Community Calendar


  • Articles


  • BlackToolS History Notes


There are no results to display.

Found 14 results

  1. DCC CHAT AND PARTY LINE The great majority of Eggdrop's functions are controlled in a DCC chat session with the bot. DCC chat with the bot has two purposes - to use as a console for entering Eggdrop commands, and to use as a chat area. Simply DCC chat to the bot just like you would a normal user. You can also make the bot initiate the DCC session by typing /ctcp <botnick> CHAT, where <botnick> is the nick of your bot. This method is particularly useful if you're behind a firewall which prevents you from initiating the DCC session. When you've established a connection to the bot, you will be prompted for your password, and then automatically placed on the party line (the main chat area). You type in Eggdrop commands by preceding them with a period (e.g. .help, .bots, .whom, .+chan, etc.). Anything not preceded with a period is sent out to other users on the party line, just like a message sent to an IRC channel. There are also other 'channels' on the bot (other than the party line) which you and others can switch to and in this way the bot can act a bit like an IRC server. TELNET You can also access the command console and party line via a telnet session to the bot. To telnet to the bot, you simply enter its hostname and port (as specified by the 'listen' command in the config file) in your telnet client. You will be asked for your nickname and password on connecting. Once connected, you'll be at the console and on the party line just as you would if you'd opened a DCC session. Telnet is particularly useful if you need to connect to the bot but aren't able to DCC to it (e.g. when the bot isn't on IRC). If the text output appears incorrectly during the telnet session (e.g. each new line is indented by the length of the previous line), you may need to enable some type of "new line mode" in your telnet client's options. In PuTTY, for example, you would enable Implicit CR in every LF under Terminal. USING THE CONSOLE Eggdrop has a comprehensive internal help system. The first thing you should do when you've opened a DCC chat session with the bot is type .help. This will display most of the commands you can use. For more info about a particular command, you type .help <command>. The DCC chat session not only allows you to speak to users on the party line (and other internal 'channels') and use Eggdrop commands, but also lets you monitor your bot. Using the .console command, you can change the types of information displayed to you, e.g. you can choose to view commands used by others, view msgs and notices sent to the bot, view public messages to a channel, and so on. Your console settings also determine what IRC channel you're working with. For example, if your bot is on #monkey and #dolphins, you can set your console to either one of those channels. Many of Eggdrop's commands will apply to your current console channel, e.g. if your console is set to #monkeys and you use the command .op zeke, the bot will op 'zeke' on #monkeys. You can change your current console channel using .console <#channel>. You may save your current console settings using .save. MSG COMMANDS Eggdrop has a limited number of commands performed via msg, but a few of them are quite important, such as the op command and ident command. For a list of msg commands, type /msg <botnick> help. Additional msg commands may be added by certain Tcl scripts. Be very careful when using msg commands that include your password - if you usually type /msg <command> <password> in a channel window in your IRC client, you will eventually end up accidentally msging your password to the channel for everyone to see. PUBLIC COMMANDS Eggdrop has no built-in public commands (i.e. commands you type in the channel) except for 'seen'. If you have the seen module loaded (i.e. loadmodule seen in the config file) and the channel is set to +seen, then the bot will respond to the seen <nick> command in the channel. There are several Tcl scripts out there that add public commands to Eggdrop. For certain functions, such as info commands and games, this is fine. But using public commands for functions such as giving ops, adding users, jumping the bot to a new server, and so on can be insecure. Such scripts could allow malicious users to take control of your channel or Eggdrop, so a good public commands script for these types of functions must have a good authorisation system built-in, and preferably only make the commands available to users who are opped on the channel. Although some people think it looks cool to be able to use public commands without being opped, it is less secure. THE USERFILE Your Eggdrop's userfile controls which users can access the bot, and the level of access each of these users has. The userfile also contains the ban lists and ignore lists. Userfile management is one of the fundamental things you need to learn in order to use your Eggdrop effectively. When you first start your Eggdrop and introduce yourself using the hello command or equivalent, you will be added as the first user and be given all owner privileges (if you have learn-users switched off, the hello command will be deactivated once you've introduced yourself as owner). To display your userfile entry, type .whois <yournick> in the console. You will see a display similar to the following: HANDLE PASS NOTES FLAGS LAST YourNick yes 0 fjmnoptx 19:57 (partyline ) #monkeys fmno 18:44 #dolphins fmno 14 Apr HOSTS: *!mynick@*.myhost.net, *!mynick@123.456.789.* The information above displays the user's handle (the handle is simply the user's nickname on the bot), whether or not they have a password set, how many notes they have, their global and channel flags, where and when they were last seen by the bot, and their hostmasks. Below you'll learn how to manipulate the userfile. DISPLAYING ALL USERS To display all the users in your bot's userfile, type .match * 999. This will display a record similar to the one shown above for each user. ADD/REMOVE USERS There are three ways a user can be added to the bot. If you have learn-users enabled in the config file, anyone can msg the hello command to the bot and the bot will add them with the default flags (as set in the config file's default-flags setting). Otherwise, you may add a user using either the .adduser or .+user command in the console. If the user you want to add is in one of the bot's channels, then .adduser is the most convenient command. Make sure the channel the user is in is your current console channel (read Using the Console again if you're not sure about this), then type .adduser <nick>, where <nick> is the nickname of the user you want to add. The user will be added to the bot's userfile with the default flags, and their hostmask will automatically be added. The .+user command should be used when the person you want to add is not on IRC. Type .+user <nick> <hostmask> to add the user with the specified nickname and hostmask. Once a user has been added, they will need to set a password using the pass command. Tell the user to type /msg <botnick> pass <password> to set their password. You may instead wish to set a password for them using the .chpass command (explained below). To remove a user from the bot, simply type .-user <handle>. CHANGING A USER PASSWORD To set a password for a user or change their password, type .chpass <handle> <password>. You can unset the password by doing .chpass <handle> without specifying a password. USER FLAGS User flags determine what privileges a user has, e.g. whether or not they can get ops on a channel, which bot commands they can use, etc. All built-in flags are lower case alphabet letters. You can list all the flags by typing .help whois, but for now you only need to know the most important flags: v - voice o - op m - master n - owner f - friend p - partyline access Many of the user flags are separated into two categories - global and channel - while some flags are global only. The v, o, m, n, and f flags are examples of flags that may be global or channel-specific, while the p flag is global-only. Channel flags only apply to a specific channel, e.g. if you give someone the o flag on #monkeys, the user will only be able to get ops on #monkeys, but if you give the user a global o flag, they will be able to get ops on all channels the bot is on. Global flags are also more powerful in nature, in that they give the user access to more powerful bot commands than the equivalent channel flags. Flags are added to or removed from a user using the .chattr command. To add a global o flag, for example, you would type .chattr <handle> +o. To add a channel specific o flag, you would do .chattr <handle> +o <#channel>. Removing flags is much the same - to remove a global o it's .chattr <handle> -o, and to remove a channel o it's .chattr <handle> -o <#channel>. You can also add/remove multiple flags in one command, e.g. .chattr <handle> +fo will give the user the f and o flags. Be very careful when giving out a global n (owner) flag. This will give the user access to virtually all the commands on your bot, and depending on how you have the bot configured it may also give the user access to your shell account via the .tcl command. ADD/REMOVE HOSTMASKS The .+host <handle> <hostmask> command allows you to add hostmasks to a user, e.g. .+host hyena *!hyena@*.africa.net. To remove a hostmask from a user, use .-host <handle> <hostmask>. THE BAN LIST The ban list is a part of the Eggdrop's userfile specifically for storing bans. Bans are added to the bot's internal ban list (also called the enforced or permanent ban list) using the .+ban command. They may also be added automatically by the bot (e.g. in response to a flood) or by a Tcl script. Internal bans can either be global (they apply to all channels the bot is on) or channel-specific. A ban may be permanent or expire automatically after a set amount of time, and it may optionally be 'sticky' (the bot makes sure the ban is always active on the channel). Note that if you're using +dynamicbans in a channel's settings, a ban set in the bots internal ban list will be removed from the channel after ban-time minutes (as set in the config file), but it will remain in the internal ban list and will be reactivated whenever someone matching the ban joins the channel. If you're using +dynamicbans but want a ban to be active on the channel around the clock, you should make the ban sticky. DISPLAYING THE BAN LIST Type .bans to display all currently active global bans and channel bans (for the current console channel). To display both active and inactive bans, type .bans all. These lists will also display bans that are active on the channel but not in the bot's internal ban list (such bans will be preceded by an asterisk). ADD/REMOVE BANS Global bans are added using the command .+ban <banmask> (e.g. .+ban *!*lamer@*.isp.net). You can add a channel ban using .+ban <banmask> <#channel>. Bans added using these commands will be permanent (i.e. they will remain in the bot's internal ban list until someone manually removes the ban). You can remove a ban in one of two ways - using the banmask or reference number. The output of .bans all will display a reference number before each ban. If you want to remove ban number 4, for example, you would type .-ban 4. Keep in mind that a ban's reference number can change depending on the console channel you're using (e.g. if you type .console #dolphins, then .bans all, then .console #monkeys, then .bans all, the reference numbers for bans may be different in the two lists you displayed). To remove a ban by its banmask, simply use .-ban <banmask>. STICKY BANS You can make a ban sticky by using the .stick command with either the reference number or banmask, i.e. .stick <number> or .stick <banmask>. A sticky ban will be reactivated by the bot if anyone removes it from the channel. CHANNEL SETTINGS The way your Eggdrop acts and responds to events in your channel is largely affected by channel settings. Eggdrop has many built-in channel settings, and you can set different settings for each channel, allowing for extreme flexibility. When you first created your Eggdrop's config file and added entries for each channel the bot was to reside on, you would have encountered channel settings for the first time. In the setup guide, you may remember having seen the following: channel add #dolphins { options } channel set #dolphins+option -option You will notice that there are two types of channel settings. The first type are ones you set between the curly braces, such as idle-kick and flood protection settings (e.g. flood-join, etc.). The second type are on/off switches you set as part of a channel set command. These switches include options such as autoop, dynamicbans, revenge, etc. These settings are preceded by a + or - sign to specify whether or not you want the option to be active or inactive respectively. For more information about each channel setting and its function, refer to the example config file(s) included with the bot. Dynamic channel settings If you want to add a channel to your bot or change a channel's settings, you don't actually need to edit the config file. Eggdrop has built-in DCC commands that allow you to add/remove channels and change channel settings via the console. To add a channel, simply type .+chan #channel. Removing a channel is as simple as .-chan #channel. Channel settings are modified using the .chanset command. This works in different ways depending on whether you're changing a on/off switches such as autoop, dynamicbans, etc., or changing a channel option such as idle-kick. Below are some examples of how the .chanset command is used: .chanset #channel +enforcebans will enable the enforcebans option. .chanset #channel -dynamicbans +autoop will disable dynamicbans, and enable autoop. .chanset #channel chanmode +sntk green will change the channel's chanmode setting to "+sntk green". .chanset #channel idle-kick 60 will set the channel's idle-kick setting to 60. To view all current channel settings for a channel, type .chaninfo #channel. THE CHANFILE Because the bot cannot modify its own config file, channels added with the .+chan command and channel settings modified with the .chanset command need to be stored in a special file called the chanfile. You may remember specifying the chanfile in your bot's config file (e.g. set chanfile "mybot.chan"). The chanfile ensures any changes you make using the DCC commands will be remembered even if the bot is shut down and restarted. There is a downside to having a channel file. Whenever the bot starts, it will first read from its config file, followed by the chanfile. Any channel settings you've specified in the config file will be overwritten by those in the chanfile - if you make changes to a channel's settings in the config file, they will not take effect. In order to change a channel's settings, you have to use the DCC commands. This can often result in a channel's actual settings being out of sync with those specified in the config file. As a result, some people chose not to add channels in the config file at all, instead using exclusively the DCC commands for adding channels and modifying their settings. You can chose not to have a chanfile by setting it to "" in the bot's config file (e.g. set chanfile ""). This will allow you to make all changes to channel settings in the config file, but any changes you make using the DCC commands will not be remembered permanently by the bot. Remember to utilise Eggdrop's internal .help feature to learn more about all the different commands. Once you're familiar with all the basic Eggdrop functions and commands, find out how to enhance your Eggdrop.
  2. Actualizare lista cu companii de SHELL/iRCD/eggDROP / Update the list of companies SHELL/iRCD/eggDROP forcesp.net exolia.fr powershells.de eushells.com xzibition.com risingnet.net exodus.ro eushells.ro (verificat, si compatibil cu TCL-urile TCLscripts.net) kire.net jeah.net shell-mx.net lomag.net kewlshells.com Notã: Lista cu companiile de servicii SHELL/iRCD/eggDROP s.a.m.d este colectatã de pe web iar serviciile/tarifele cat si calitatea/stabilitatea serviciilor nu este/nu are nici o legatura cu tclscripts.net. Toate informatiile sunt colectate cu scop informativ Note: The list of SHELL/iRCD/eggDROP s.a.m.d service companies is collected from the web and the services/rates as well as the quality/stability of the services is not related to tclscripts.net. All information is for informational purposes
  3. corona-stats

    Version 1.0.1


    # COVID-19 (corona) statistics script for Eggdrop A script that displays real time statistics about COVID-19 (corona). ## Requirements * Eggdrop >= 1.6.18 * TCL >= 8.6 * tcllib (<https://www.tcl.tk/software/tcllib/>) * tcltls (<https://core.tcl-lang.org/tcltls/index>) ## Commands !corona [country] - Shows total statistics if no argument is given. If a country name is given as argument detailed statistics for that country is displayed. Ex: !corona Sweden !corona-<XX> - Shortcut command to display detailed statistics for a specific country. XX is replaced by a short country name. Ex: !corona-se, !corona-us etc !coronaus-<XX> - Display statistics for a US state. XX is replaced by the short state name. Ex: !coronaus-ny for New York, or !coronaus-al for Alabama. !coronaca-<XX> - Display statistics for a province in Canada. XX is replaced by the short province name. Ex: !coronaca-on for Ontario, or !coronaca-ns for Nova Scotia. !coronatop5 [category] - Display top 5 country statistics. Provide an optional category to override the default (cases). !coronatop5 help - Display valid categories.


  4. Solved TLC scripts not working.

    Hi there, Thanks for the awesome scripts you have there, however I encountered some problems with 2 of the scripts you have here. First one is FAZAN. Not returning any error, eggdrop shows script as loaded but whenever i go into the channel and type !fazan on / !fazan (nothing happens). Second is the black scrabble. This is the error i always get when i type !scrabble on. Until recently all it returned was (scrabble is not on). Unknown channel setting. while executing "channel get $chan Scrabble" (procedure "start:Scrabble" line 38) invoked from within "start:Scrabble $_pub1 $_pub2 $_pub3 $_pub4 $_pub5" Thank you in advance for your help. Using latest version of eggdrop paired with unrealircd
  5. Eggdrop v1.8.4 Stable Release

    Eggdrop v1.8.4 has gone STABLE. Hooray! The major changes are: - lots of work on the compile process for less-commonly seen systems (SunOS, DragonFly, etc), and making eggdrop more compiler-friendly in general - added and enhanced SSL/TLS warnings to make troubleshooting easier - raised the ban expiration limit from 1 year to 5 years, and added a new \%y field to +ban - lots of work on TLS bot links - improved/clarified botnet TLS documentation- go read it! - made TLS fingerprints persistent across a botnet after relinking - sterilized a LOT of small, lingering bugs. You can follow development and report bugs on https://github.com/eggheads/eggdrop Download Eggdrop v1.8.4 here
  6. pisg 0.80-preview2

    Version 0.80


    Pisg - an abbreviation of the Perl the IRC Statistic Generator . The parser, which generates a nice html-stats user activity on a specific channel on IRC. It is used to generate log files.Supported formats: X-Chat, mIRC, mIRC6 , Eggdrops, bxlog for BitchX, irssi, virc98, dancer, Trillian, Grufti, mbot, winbot, zcbot, muh, energymech, ircII, psybnc, ircle, infobot, axur, bobot ++, oer , perlbot, Vision, pircbot, KVIrc , HydraIRC, sirc, moobot, supybot, blootbot, dircproxy. The only requirement thing: the Perl (and of course do the logs). More info: https://pisg.github.io/


  7. BlackHoroscopRO.tcl

    Version 1.4.1


    Ofera previziune detaliate zilnice ale horoscopului pentru fiecare semn zodiacal. UPDATES: complet reconstruit intr-un stil nou si cu o alta sursa web de informatii pentru horoscop. adaugate setari de protectie la flood impotriva celor care abuzeaza de folosirea comenzilor. adăugata setare pentru o zodie prestabilita fiecarui user, diferita pentru fiecare canal. adaugate informatii procentuale despre dragoste, sanatate si succes. adaugate informatii suplimentare despre numerele norocoase. adaugat suport utf-8. Semne zodiacale: Berbec, Taur, Gemeni, Rac, Leu, Fecioara, Balanta, Scorpion, Sagetator, Capricorn, Varsator si Pesti. INSTALARE: pachetele http si json sunt necesare pentru ca acest script sa functioneze. editeaza BlackHoroscop.tcl si pune-l in directorul /scripts al eggdropului tau, adauga linia "source scripts/BlackHoroscop.tcl" in conf-ul eggdropului tau si apoi rehash..


  8. pisg

    Version 0.7.3


    Pisg - an abbreviation of the Perl the IRC Statistic Generator . The parser, which generates a nice html-stats user activity on a specific channel on IRC. It is used to generate log files.Supported formats: X-Chat, mIRC, mIRC6 , Eggdrops, bxlog for BitchX, irssi, virc98, dancer, Trillian, Grufti, mbot, winbot, zcbot, muh, energymech, ircII, psybnc, ircle, infobot, axur, bobot ++, oer , perlbot, Vision, pircbot, KVIrc , HydraIRC, sirc, moobot, supybot, blootbot, dircproxy. The only requirement thing: the Perl (and of course do the logs). More info: http://pisg.sourceforge.net/


  9. Eggdrop v1.8.3 Stable Release

    The final release of Eggdrop version 1.8.2 is here! The major changes are: - bugfixes related to SSL/TLS and botnets in particular - Backwards-compatible syntax change to the addbot command (dcc and Tcl) to restore sanity when dealing with IPv6 addresses. - A new .resetconsole dcc command was added to reset your console flags to the defaults. - Simplified botnet debugging, with the console modes +h/+g showing outgoing and incoming botnet raw traffic respectively. - Significant work on many botnet features and bugs, to include additional granularity in botnet traffic console flags, improved logging, and some issues with SSL handshakes. - Additional error/sanity checks for user inputs with various commands You can follow development and report bugs on https://github.com/eggheads/eggdrop Download Eggdrop v1.8.3 here
  10. BlackToolS 2.5

    Aici găsiţi versiunea 2.5 a scriptului BlackToolS, pe care o puteţi descărca de mai jos. Pentru mai multe info consultati manualul tcl-ului (vedeti comanda .man). We offer a lot of support for BlackTools scripts, however you can also support us: Donations will help me to keep working on this project.
  11. eggdrop 1.8 eggdrop-1.8.1.tar.gz

    Version 1.8.1


    The major changes between 1.8.0 and 1.8.1 are: * Autobotchk: Added functionality improvements, allowing special characters to be used in botnicks (and hence filenames), and made it able to deal with split up configs that source further files. * .who linkedbot output: Truncates long channel listings appropriately. * eggdrop.conf: Update source code to match defaults given in Eggdrop configuration file. * Timer drifts: If your bot really gets frozen longer than 60 minutes, it now shows times longer than 60 minutes. * ./configure: Added an options summary at the end so you see which Tcl version was used, and whether it found IPv6 and SSL files * OpenSSL: A new version of OpenSSL broke our OpenSSL detection (the hexstr2buf function) and we fixed that. * Versioning: Moved previously hard-coded version strings to version.h and update them via misc/setpatch instead of misc/addpatch. This also fixes inconsistencies in setting the internal version integer. * Bugs: A lot were cleaned up! For the full list of changes see doc/Changes1.8. You can follow development and report bugs on https://github.com/eggheads/eggdrop


  12. There's no simple way to recover the original password you set on the bot. You need to edit the bot's userfile directly and reset the password. The userfile is usually in your bot's main directory and has the .user file extension, e.g. NiceBot.user. There are two ways you can do this - either telnet to the shell and edit the userfile in the shell's text editor (e.g. pico), or FTP to the shell, download the userfile, edit it on your system, then upload it to overwrite the existing one. First, kill the bot from the shell (if you don't do this, the bot may overwrite any changes you make to the userfile). Then find your entry in the userfile. The example below shows a user entry for "CoolDude": CoolDude - p ! #pigs 910669920 fo ! #cows 952889739 fo --HOSTS *!cool@*.coolisp.net --PASS +vGjzQ0zcBbK/ Delete the password line, e.g. --PASS +vGjzQ0zcBbK/. This will delete the your password. You can now restart your bot. When your bot appears on IRC, you will need to set your password again using the msg command: /msg botnick pass <password>. The same method is valid if your hostmask has changed, just need to modify the line: --HOSTS *!cool@*.coolisp.net Have fun!
  13. About Eggdrop

    Eggdrop is the world's most popular open source IRC Bot "..designed for flexibility and ease of use" and is freely distributable under the GNU General Public License (GPL). Eggdrop was originally developed by Robey Pointer; however, he no longer works on Eggdrop so please do not contact him for help solving a problem or bug. Some features of Eggdrop ​designed to run on Linux, *BSD, SunOs, Windows, MacOS X, etc. extendable with tcl scripts and/or C modules support for the big five IRC Networks (UnderNet, DALnet, EfNet, IrcNet, and QuakeNet) the ability to form botnets and share partylines and userfiles between bots Some benefits of Eggdrop the oldest IRC bot still in active development (was created in 1993) established IRC help channels and web sites dedicated to Eggdrop thousands of premade tcl scripts and C modules best of all ... It's FREE! How to install an Eggdrop The Short Short & Updated Version ssh to the shell. wget or ftp the source from [[1] [2] ] UnPack it ( tar zxvf eggdrop1.8.0.tar.gz ) Switch to the directory ( cd eggdrop1.8.0 ) Start the config script ( ./configure ) Compile the modules ,either all ( make config ) or select some of them ( make iconfig ). Compile the bot ( make ) Create botdir ( mkdir /home/name/botdir ) Install it to a directory of your choice ( make install DEST=/home/name/botdir or try make eggdrop install DEST=/home/name/botdir ). Switch to the botdir and edit the sample config file eggdrop.conf, then rename it to something appropriate (e.g. botnick.conf). Start the bot up in user-creation mode (only the first time) ( ./eggdrop -m <config file> ). Telnet to the port you chose in the config file and type "NEW" as user. Setup your real user name and password. Now you are owner of the bot , and from now on you start it without the -m option , just (./eggdrop <config file>). If you dont see it appearing on IRC right away, Telnet to the Partyline and try .jump irc.someserver.com You should have setup your channels in the config, but if you activated dynamic channels you can now use .+chan #channel on the partyline to make your bot join additional channels. Now learn the partyline commands to setup users and give them the flags you want. (.+user , .adduser , .chattr) and generally .help . All partyline commands beging with a "." Enjoy. Note: Eggdrop requires tcl to compile. If the server does not have tcl installed, you will need to download and [install] it. Hint: You might want to set your $LD_LIBRARY_PATH enviromental varible. export LD_LIBRARY_PATH; LD_LIBRARY_PATH=/usr/local/lib" or where ever your libary is. If you get a error like this... ./eggdrop: error while loading shared libraries: libtcl8.4.so: cannot open shared object file: No such file or directory Setting Up botchk botchk is a nice little cron script that will start your bot for you if its not running. e.g if the bot die's or the is box restarted. be carefull though, as it will just keep starting up the bot no matter why it dies, make shore you box admin alows the use of botchk. in the eggdrop/scripts dir run this command ./autobotchk <config> -dir /home/botdir -noemail where <config> is the name of your bots config file and /home/botdir is the dir of you bot. Eggdrop logs To not keep logs, in its eggdrop.conf file just comment out (precede the line with #) these two lines: #logfile mco * "logs/eggdrop.log" & #logfile jpk #lamest "logs/lamest.log" Then .rehash your bot and manually delete the log files if any. To know more about logging, just read in the config file itself. If you decide to do logging, keep an eye on them, they can grow massive. Crontab autobotchk - This will re-start your bot if it's not running because server went down, etc. This won't work if there is an error in the bot's conf file of course. Login to your shell (not telnet to bot). Enter this cmd: crontab -l That will tell you if it's already available. If it's not, reply will be something like: crontab: no crontab for (your user name) If it's not enter your bots directory: cd /home/user/yourbotsname and then do: cron-egg yourbotsname.conf crontab -l It should now reply: 0,10,20,30,40,50 * * * * /home............mybot.botchk >/dev/null 2>&1 Which means it will check every 10 mins if bot is running, if not it will start it for you. For example: on a different server that didn't work and I had to do this: cd /home/user/yourbotsname/scripts/ ./autobotchk yourbotsname.conf Then do again to view it listed: crontab -l If you do not want to be e-mailed each time your bot is off line, add the ' >/dev/null 2>&1' part of the code if it isn't there already: crontab -e For example if it has: 0,10,20,30,40,50 * * * * /home/user/MyBot/mybot.botchk Change it to: 0,10,20,30,40,50 * * * * /home/user/MyBot/mybot.botchk >/dev/null 2>&1 Ctrl+x to save changes, then y, hit enter key. Ouput will be: crontab: installing new crontab Extensions / Scripts Eggdrops can be heavily extended using tcl scripts. Misc / News [ 04 Dec 2016 ]: Eggdrop 1.8.0 released [ 04 Oct 2011 ]: Eggdrop 1.6.21 released IRC support To get support via IRC: join #egghelp (eggdrop questions), #TCL-HELP (scripting questions) on Undernet.
  14. BlackToolS 2.4

    Aici găsiţi versiunea 2.4 a scriptului BlackToolS, pe care o puteţi descărca de mai jos. Pentru mai multe info consultaţi manualul tcl-ului (vedeţi comanda .man). We offer a lot of support for BlackTools scripts, however you can also support us: Donations will help me to keep working on this project.