I started my bot and invited bot to chan (keyed chan) and did /msg mybot hello, but did not get the msg back to complete necessary steps to work with my bot. I ftp'd up to my bot and checked my bots dir and noticed no userfile is created. Also, the only way i can successfully start my bot via telnet is by ./eggdrop -m mybot.conf, it will not start if i use ./eggdrop mybot.conf. Any ideas what i am doing wrong? I am using a linux shell.
I tried to telnet (puddy) up to the bot, using the port specified in the "listen" as apposed to 22, and the console would come up for a moment, then just disapear. I do not get my "nick" prompt to enter NEW.
The only way i can telnet is by using port 22 (that i know of, because i tried the latter with no sucess)
Any Ideas that may help again would be greatly appreciated.
port 22 is reserved for the SSH daemon; your linux shell is most likely firewalled and doesn't allow outside connections except on port 22
I presume you meant "putty", not "puddy"
using putty, login to your shell via ssh, not telnet
once inside, type "telnet localhost <botport>" and you'll get to the "nickname" prompt; if this doesn't work, try to substitute localhost with your vhost's IP (if you have a vhost)
also make sure to add "bind msg - hello *msg:hello" at the end of mybot.conf - this should enable bot's default response (i.e. adding you as an owner and allowing you to /dcc chat yourbot) to your /msg yourbot hello
unbind msg - hello *msg:hello do you mean for me to set it to
bind msg - hello *msg:hello?
Also, yes lol i meant putty, not puddy <<<< bad gurl lol
One more thing, i was just informed that my having an undernet host, may be causing me problems, but a few friends are on undernet hosts and are not experiencing problems, so
I will try what u suggested ***fingers crossed*** im getting closer:)
unbind msg - hello *msg:hello do you mean for me to set it to
bind msg - hello *msg:hello?
That's your problem right there. There should not be a question mark (?) at the end of that line. You can do 1 of 2 things: 1) remove the question mark from the end of that bind, or 2) delete that line entirely, and then comment out the unbind, like this:
the question mark was at the end because i was asking the question lol
its not on the config file that way, on the config its:
unbind msg - hello *msg:hello
but it is not commented out.
should i set this to:
bind msg - hello *msg:hello as u stated earlier, or should i comment this out alltogether?
Any ideas on this?
Also, thank you so much for your time:) I printed out this section "Setting Up Your Eggdrop - Configuration" and read it completely, i may have missed sompthing so i will of course read it again:)
i went ahead and changed unbind to bind msg - hello *msg:hello
I reread and saw that here (thank you for telling me to reread it lol)
I found in this section of "setting up eggdrop"
"unbind msg - ident *msg:ident and unbind msg - addhost *msg:addhost: these lines unbind the ident and addhost commands. You will almost certainly want to rebind the ident command, either by commenting out the unbind line (this will enable the default 'ident' msg command) or by binding it to a new command. It's a good idea to change the command for extra security. To bind it to another command, let's say 'horse', you would add the line bind msg - horse *msg:ident.
"
that did it also i went in unmasked so now i will mask again and add my mask to the user file
again thank you so much, this is a great and helpful forum!
i always always bind 'hello' to something different, just cos there are too many lames out there who would just pee themselves to access an eggdrop, even if just for a few moments.
im in such the early stages of learning. Thank you for the tips.
I already msg'd my bot and she recognized me as own, is it too late to change my bind to something other than hello, w/o having to start from scratch (cause she added to other bots now)?
in your config file, there is no need to change the "hello" trigger, it will be functional only the first time someone says it to the bot (i.e. the owner) and the bot is in userfile creation mode