Eggdrop Wiki talk:Todo

From Eggdrop Wiki

(Difference between revisions)
Jump to: navigation, search
(I will add this after my account has been fully activated...)
(partyline)
Line 15: Line 15:
There are different methods to get on the partyline.
There are different methods to get on the partyline.
-
/dcc chat <botnick>
+
* /dcc chat <botnick>
-
/ctcp chat <botnick>
+
* /ctcp chat <botnick>
-
telnet <ipadress> <listen-port>
+
* telnet <ipadress> <listen-port>
== dcc chat ==
== dcc chat ==

Revision as of 17:26, 24 November 2011

Perhaps move this to Eggdrop_Wiki:Community_portal instead (and link that in the navbox)? --Pixelz 18:20, 27 May 2009 (UTC)

Contents

Plans to make the wiki not suck

I think we need to come to a consensus on what a good general layout/direction of the wiki is. I was thinking the front page could have "sections" for sorts, each "section" having information relevant to different levels of eggdrop users. People new to eggdrop could have one section or main article or whatever that describes in general what eggdrop is, linking to more in-depth articles such as how to compile eggdrop, the "console system" explained, difference between static & dynamic channels, <insert more random stuff here>. I was also thinking about some good way to handle console commands. The best idea I've come up with so far is to have a different template for each command, so that there's only one place to change information about it. The problem with this idea is that I don't see a good way to handle really long descriptions. In any case, a system that is easily maintained needs to be thought out. --Pixelz 19:58, 28 May 2009 (UTC)

I will add this after my account has been fully activated...

sudo apt-get install libssl-dev ...--SKy 16:55, 24 November 2011 (UTC)

partyline

The partyline is very useful to find out why you bot won't come to irc or to see if scripts are working properly and so on. There are a lot common problems in order to join the partyline.

There are different methods to get on the partyline.

  • /dcc chat <botnick>
  • /ctcp chat <botnick>
  • telnet <ipadress> <listen-port>

dcc chat

  • dcc chat will only work if the bot is already on IRC
  • needs server port on your local computer
  • The local computer from where you want to establish a dcc connection needs to be able to open a server port. This means it needs to be reachable from outside. This is a major problem these days as most routers have NAT enabled by default. If you want to learn that, it's not really eggdrop related. Consult your routers manual for port forwarding or search the web.
  • in this case it does not matter if the bot is running firewalled shell
  • for many clients (mIRC, xchat, ...) type: '/dcc chat <botnick>'

ctcp chat

  • ctcp chat will only work if the bot is already on IRC
  • in this case it does not matter if your local computer is firewalled
  • the shell where the eggdrop may not run a firewall or must forward the listen port
  • you need to set 'listen <listen-port> all' in your eggdrop configuration file, consult eggdrop example configuration file for details
  • for many clients (mIRC, xchat, ...) type: '/ctcp chat <botnick>'

telnet

  • most operating systems have a telnet client preinstalled (Windows 7 has not, google 'Windows 7 telnet client' how to install it)
  • when you eggdrop is running on a shell you can login into your shell and type 'telnet 127.0.0.1 <listen-port>' for example 'telnet 127.0.0.1 55555' - the advantage of this method is that no firewall can be in the way
  • After you made sure that this is working you do not need to login into your shell. You can telnet from your local computer. 'telnet <shell-ip> <listen-port>'
  • You may be interested in a better telnet client. Note that those are not supported by the official eggdrop developers.
  • eggdrop telnet client http://forum.egghelp.org/viewtopic.php?t=18625
  • or xchat telnet.tcl http://forum.egghelp.org/viewtopic.php?t=18701
  • Or if you are using sBNC 1.3. you can add 'source "scripts/telnetclient.tcl"' to sbnc.tcl. After being on your sBNC type '/sbnc addtelnet <shell-ip> <listen-port>'. If sBNC installed on the same shell you can also use 127.0.0.l as IP-adress and of course there will be also no firewall problems.
Personal tools