Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. UrlTitle tcl

    Someone seems to continue this on githuib: https://github.com/teeli/urltitle
  3. UrlTitle tcl

    Lo probare y vere mi experiencia.
  4. Last week
  5. Covid19.tcl

    i am conducting a survey: how would you rate the corona psyop - on a scale of one to ten ? Works nice in every way - using 1.3.4
  6. Earlier
  7. LiveTennis.tcl

    Version 1.0.0

    1 download

    DESCRIPTION: Gives real-time tennis game results via scorespro.com. ++ http package is REQUIRED for this script to work. ++ tls package is REQUIRED for this script to work. (1.7.18-2 or later) COMMANDS: !tennis - shows default option matches !tennis live - shows live matches !tennis sch - shows scheduled matches !tennis fin - shows finished matches !tennis all - shows all matches !tennis save <id> - save match in LIVE list (get ID from list) !tennis list - shows the LIVE list. !tennis del <id> - remove the saved match from LIVE list !tennis help - get more help ;p Output Example: -= Live Tennis =- Junaid R. (AUS) - Luca Gelhardt (GER) ; Score: 0:1 ; Match Status: Set 2 ; Set Results: 1:6 0:0 ; Total games: 7 ; Comment: N/A -- Men Exhibition: Tennis Point Series Germany ; ID: m5299527-1

    30.00 EUR

  8. Timer.tcl

    Version 1.0.0


    DESCRIPTION: Allows you to start/stop processes timers or see the list of active ones.


  9. BlackRSS.tcl

    Version 1.0.0


    DESCRIPTION: Gets news from RSS sites added via IRC. Now featuring a preferential setting that let's the user define his keywords to get only the news that contains them. Every chan can have its own list of RSS feeds to check. packages required : tdom, http, tls Commands : !rss - shows the ID's and the commands for the RSS added !rss add <rss cmd> <link> <name> [num=X time=X enc=X word=X,Y,Z] Options (if not specified the standard values are set bellow): num=X -> define the number of new rss news to get ; ex: num=5 time=X -> define the time in minutes for the bot to check for new news ; ex: time=3 enc=X -> define the 'encoding' if the news aren't looking so great (like utf-8) word=X,Y,Z -> define keywords for the rss news (only the news that contain one of the words specified in the title or desc will be shown) ex: word=coronavirus,pandemic,covid --- You can specify one, all or none of the options shown !rss list -> lists each RSS news added with their details (id,cmd,link, etc.) !rss del <id> (removes an added RSS, the ID can be taken from !rss list or !rss) !rss check <link> (checks a RSS link) !rss help - shows the help

    5.00 EUR

  10. Solved scrabble.tcl

    put the file that scrabble.data not in scripts but in eggdrop (near eggdrop config)
  11. Solved scrabble.tcl

    [21:29:16] Tcl error [start:scrabble]: random limit must be greater than zero unknown namespace in import pattern "::tk::msgcat::*" while executing "namespace import -force ::tk::msgcat::*" (in namespace eval "::tk::dialog::error" script line 2) invoked from within helpme please
  12. Opening a telnet session directly to your bot is similar to opening a DCC chat session - you will be placed in the command console and can control your bot with DCC commands. The difference is that telnet is not dependant on IRC, so you don't need to be on IRC to telnet to the bot. To telnet to your bot, you must specify its hostname and port in your telnet client. The hostname is the same as your bot's vhost - e.g. if your bot's host on IRC is froo@cool.tclhelp.team, you would telnet to cool.tclhelp.team. The port you need to specify depends on the listen port you have set in the bot's config file, e.g. if you have listen 4941 all, you need to telnet to port 4941. If you have enabled protect-telnet in the bot's config file and are having trouble opening a telnet session with your bot, you'll need to check that you've created a telnet mask for yourself. A telnet mask looks like -telnet!*@host.goes.here. If you want to telnet from *.yourisp.net for example, you'll need to add that as a telnet host by typing .+host YourNick -telnet!*@*.yourisp.net.
  13. Your bot recognises you by the hostname you have on IRC (e.g. zeke@tclhelp.team). It compares this hostname with the hostmasks contained within your user record (e.g. *!zeke@*.tclhelp.team) and will recognise you if they match. If you change your ident or get a new ISP, your bot will not recognise you and will not respond to your DCC chat requests. Eggdrop has a built in msg command called ident that is used to make the bot recognise you after your hostname has changed. The syntax is /msg <botnick> ident <password> [nickname]. The nickname portion is only required if you're using a different nick from the one your bot knows you by (e.g. if your user record on the bot is 'froo' but you're using 'froo2' on IRC, you'll need to specify 'froo' as the nickname). Note that if you used the advanced or complete example config file that's included with Eggdrop to create your config file, your bot may have disabled the ident command, or you may have changed it to something different. Look for the following section in your bot's config file: # Many takeover attempts occur due to lame users blindly /msg ident'ing to the bot and attempting to guess passwords. We now unbind this command by default to discourage them. You can enable these commands by commenting the following two lines. unbind msg - ident *msg:ident unbind msg - addhost *msg:addhost To reactivate the ident command, add the following line just below the above lines: bind msg - ident *msg:ident If you'd like to set your ident command to something different, you can replace ident with another word (note that you don't change the *msg:ident bit - that stays the same). The ident function isn't the only way to add new hostmasks. You can add, remove and modify your hosts using the .+host and .-host DCC commands. Type .help +host and .help -host for more info on using these commands. Of course, to use these DCC commands, you must already be logged into the bot, so you'd have to add any new hostmasks before your ident and/or host changes.
  14. 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.
  15. BlackWeather.tcl

    I appreciate the scripts running well done
  16. Jokes.tcl [EN version ONLY]

    Version 1.0.0


    DESCRIPTION: Shows jokes from laughfactory.com by specifing category or by search. COMMANDS: !joke (shows a random joke from a random category) !joke categ (list categories for jokes) !joke <cat. nr> (shows a random joke from a specified category) !joke <string> (shows a random joke based on a specified string) !joke help (shows the help) To enable autoshow : .chanset +autojokes | from BlackTools: .set #channel +autojokes (on timer) ### # Jokes categories: ## # 1 - LATEST # 2 - ANIMAL # 3 - BLONDE # 4 - BOYCOTT THESE # 5 - CLEAN # 6 - FAMILY # 7 - FOOD # 8 - HOLIDAY # 9 - HOW TO BE INSULTING #10 - INSULT #11 - MISCELLANEOUS #12 - NATIONAL #13 - OFFICE #14 - POLITICAL #15 - POP CULTURE #16 - RELATIONSHIP #17 - RELIGIOUS #18 - SCHOOL #19 - SCIENCE #20 - SEX #21 - SEXIST #22 - SPORTS #23 - TECHNOLOGY #24 - WORD PLAY #25 - YO MOMMA ##


  17. UrlTitle tcl

    Hello I'm interested to test this but found thiserror [14:29:49] Connection to https://youtu.be/aKpEz72ob1s failed [14:29:49] Error: invalid command name "::http::meta"
  18. UrlTitle tcl

    Hello I'm interested to test this
  19. Banc.tcl [RO version ONLY]

    Version 2.0


    DESCRIPTION: Cele mai noi si mai tari bancuri de pe mioritice.com - sursa zilnica de bancuri de calitate de la oameni amuzanti. COMENZI: !banc (preluare banc aleatoriu din catergoria default setata) !banc categ (listare categorii bancuri) !banc <nr. categ> (preluare banc aleatoriu din categoria dorita) !banc set <nr.categ> (setare categorie implicita pentru canal.) ### # Categorii bancuri: ## # 1 - Cele mai noi # 2 - Populare # 3 - Top Bancuri # 4 - Animale # 5 - Bula si altii # 6 - Categorii sociale # 7 - Despre sex si sexe # 8 - Discutii de tot felul # 9 - Diverse #10 - Etnii natiuni si rase #11 - Personalitati #12 - Politice #13 - Regiuni #14 - Religie #15 - Sadice si scarboase #16 - Seci #17 - Sportivi si despre sport ##


  20. Covid19.tcl

    It's a good script. And thank you very much for help and patience that it works for me now.
  21. CountryInfo.tcl

    Version 1.0


    DESCRIPTION: Shows some info of the world countries (capital, currencies, population, etc). Also records countries from users joining your channel and makes a top list. INSTALLATION: ++ http package is REQUIRED for this script to work. ++ tls package is REQUIRED for this script to work. (1.7.18-2 or later) -------------------------------------------------------------------------- * How to install tls: wget https://core.tcl-lang.org/tcltls/uv/tcltls-1.7.20.tar.gz tar -xzf tcltls-1.7.20.tar.gz cd tcltls-1.7.20 ./configure make (as superuser - root) make install


  22. Covid19.tcl

    FIXED works great thanks
  23. 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
  24. install-bt.sh

    Version 1.0.0


    A small linux script that allows you to install in your eggdrop the latest BlackTools 2.5.3 script. COMMAND: bash install-bt.sh <eggdrop directory>


  25. UrlTitle tcl

    Seems a good script
  26. iceRadio.tcl

    Finally a complete TCL for IceCast radios! Multiple mounts, that no TCL had it until now, and besides of this TCL is very easy to customise for your personal needs!
  27. currency.tcl

    Version 1.0.0


    DESCRIPTION: An utility to convert currencies. A list of currencies is available in tcl. ++ http package is REQUIRED for this script to work. ++ json package is REQUIRED for this script to work. Commmands: !conv <currency> ; it will convert the <currency> in the default currency set !conv <currency> [value] ; it will convert the value specified of <currency> to the default !conv <from_currency> <to_currency> ; it will convert <from_currency> to to_currency !conv <from_currency> <to_currency> [value] ;it will convert <from_currency> to <to_currency>


  28. 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.


  1. Load more activity