# $EPIC: dcc.txt,v 1.4 2007/02/02 23:28:03 jnelson Exp $
dcc [<command> [<arguments>]]
DCC stands for Direct Client-to-Client connection. The DCC command manages all off these connections. There are two primary uses for DCC; chatting with other users without having to use the irc network; and file transfers. These are examples; they are not the limit of DCC's capabilities.
DCC connections are offered with CTCP DCC requests. This means that you need to have a way to send a message to the person you want to offer the DCC to, typically you have to be on the same network.
DCC offers that others make to you are considered CTCP messages as far as IGNORE and flood control and the like go.
DCC requires that the initiator be able to accept inbound connections to their host. Firewalls (such as NAT routers used by broadband customers) often preclude this possibility and so if you are behind a firewall you will not be able to offer DCC connections, but you will be able to accept requests by others.
If both you and the person you want to talk to are behind a firewall which disallows inbound connections then you will not be able to use DCC at all. This is not a restriction in EPIC or in the DCC specification; it is simply how the internet works.
Using DCC with no arguments is the same as [DCC LIST]].