EPIC Enhanced Programmable IRC-II Client

on dcc_lost (removed)

Former synopsis

/on [<noise>]dcc_lost "<pattern>" { <commands> }

Description

The dcc_lost event formerly reported the end of a DCC Chat or DCC Send connection, including unsuccessful connections. It also reported failure to use an explicitly requested local port, allowing a script to choose another port or abandon the offer. Allowing default handling displayed a message.

EPIC6 has removed the DCC implementation and this named hook. It no longer generates these disconnection or port-conflict events. There is no built-in DCC loss message to customize or suppress.

Former parameters

For ordinary disconnection, $0 held the peer nickname and $1- held a variable disconnection message.

The special port-in-use form used:

Parameter Former meaning
$0 Person receiving the offer.
$1 DCC type, such as send or chat.
$2 URL-encoded filename, if any.
$3 DCC refnum.
$4 Port that was already in use.
$5- Literal text PORT IN USE.

These describe the removed interface, not arguments generated by EPIC6. Changing want_port through the former dccctl function or deferring a new /dcc ... -p ... offer is unavailable because those DCC primitives were removed too.

Compatibility

Attempting to register /on dcc_lost ... is rejected with No such ON function: DCC_LOST. Retained script references, including timeout code that attempts to synthesize the event, do not restore the hook or DCC connections. Scripts implementing their own connections must provide their own close, error, and port-selection handling.

For loss of an IRC server connection, see on disconnect. It concerns a different transport and has different parameters.

Source references