Dcc Options » History » Version 17
Per Amundsen, 07/29/2019 09:38 PM
| 1 | 1 | Per Amundsen | {{>toc}} |
|---|---|---|---|
| 2 | |||
| 3 | h1. Dcc Options |
||
| 4 | |||
| 5 | 3 | Per Amundsen | "Direct Client to Client":https://en.wikipedia.org/wiki/Direct_Client-to-Client options. |
| 6 | |||
| 7 | 11 | Per Amundsen | _See also [[/dcc]]._ |
| 8 | |||
| 9 | 12 | Per Amundsen | h1. Dcc Get |
| 10 | |||
| 11 | 1 | Per Amundsen | h2. Default download dir |
| 12 | |||
| 13 | The default download folder to use when receiving a file. |
||
| 14 | |||
| 15 | 7 | Per Amundsen | h2. Use fast get |
| 16 | |||
| 17 | if enabled, retrieves data as fast as possible without sending acknowledge packets, otherwise sends acknowledge packets after each read. (Slower but better compatibility with some clients/bots) |
||
| 18 | |||
| 19 | 6 | Mr. BS | h2. Show progress in taskbar |
| 20 | |||
| 21 | 14 | Per Amundsen | If enabled, AdiIRC will display progress bar in app icon in Taskbar for dcc file transfers. |
| 22 | |||
| 23 | h2. Buffer |
||
| 24 | |||
| 25 | The number of bytes to buffer when reading from the socket. (4096 is most compatible) |
||
| 26 | 1 | Per Amundsen | |
| 27 | 12 | Per Amundsen | h1. Dcc Send |
| 28 | 8 | Per Amundsen | |
| 29 | 7 | Per Amundsen | h2. Use fast send |
| 30 | |||
| 31 | if enabled, sends data as fast as possible without waiting for acknowledge packets, otherwise waits for acknowledge packets after each send. (Slower but better compatibility with some clients/bots) |
||
| 32 | 1 | Per Amundsen | |
| 33 | h2. Portrange start |
||
| 34 | |||
| 35 | Start of the portrange to use for *sending* dcc files, this is not used for receiving files. |
||
| 36 | |||
| 37 | h2. Portrange end |
||
| 38 | |||
| 39 | End of the portrange to use for *sending* dcc files, this is not used for receiving files. |
||
| 40 | |||
| 41 | h2. Bind to adapter or IP address |
||
| 42 | |||
| 43 | If enabled, AdiIRC will try to bind to the chosen network adapter or IP address when *sending* dcc files, otherwise it will use ip address retrieved from the server. |
||
| 44 | |||
| 45 | h2. Prioritize IPv6 |
||
| 46 | |||
| 47 | If "Bind to adapter or IP address" is enabled, AdiIRC will use the IPv6 address if found. |
||
| 48 | |||
| 49 | 12 | Per Amundsen | h1. Dcc Get Folders |
| 50 | 1 | Per Amundsen | |
| 51 | List of folders to save dcc file transfers matched by file type/extensions. |
||
| 52 | |||
| 53 | [[Dcc_Get_Folders_Dialog|Dcc Get Folders Dialog]] |
||
| 54 | |||
| 55 | h2. Dcc Ignore Method |
||
| 56 | |||
| 57 | If set to *Disabled*, all incoming transfers are allowed. |
||
| 58 | |||
| 59 | If set to *Accept only*, only incoming transfers with file types matching the list will be allowed. |
||
| 60 | |||
| 61 | If set to *Ignore only*, only incoming transfers with file types *not* matching the list will be allowed. |
||
| 62 | 12 | Per Amundsen | |
| 63 | 17 | Per Amundsen | h1. Ignore all |
| 64 | |||
| 65 | If enabled all SEND/SSEND requests will be ignored. |
||
| 66 | |||
| 67 | 12 | Per Amundsen | h1. Auto accept |
| 68 | |||
| 69 | h2. Auto accept transfers |
||
| 70 | |||
| 71 | If enabled, AdiIRC will automatically accept dcc file transfers from any users. (Not recommended) |
||
| 72 | |||
| 73 | h2. Auto accept transfers only from host |
||
| 74 | |||
| 75 | If enabled, AdiIRC will automatically accept dcc file transfers from any users matching a host in the list. (Not recommended) |
||
| 76 | |||
| 77 | 16 | Per Amundsen | _Syntax for matching a host name is nick!ident@host, [[Scripting_Wildcards|wildcards]] can be used._ |
| 78 | 15 | Per Amundsen | |
| 79 | _The host name can be prefixed with *network:* to only match on a specific network, network name can be retrieved from [[$network]]._ |
||
| 80 | |||
| 81 | 12 | Per Amundsen | h2. If file exists |
| 82 | |||
| 83 | Action to take when receiving a dcc transfer file transfer and *Auto accept transfers* is enabled and the file already exists. |
||
| 84 | |||
| 85 | 13 | Per Amundsen | When set to *Ask*, you will be prompted what to do. |
| 86 | When set to *Resume*, it will automatically resume the transfer. |
||
| 87 | When set to *Overwrite*, the old file will be deleted and then start the transfer. |
||
| 88 | When set to *Cancel*, the transfer will be canceled/ignored. |