Crossfire Protocol Reference
Clone this wiki locally
- Migrating from Crossfire 0.3a8 to 0.3a11
- Migrating from Crossfire 0.3a7 to 0.3a8
- Migrating from Crossfire 0.3a6 to 0.3.7
- Migrating from Crossfire 0.3a5 to 0.3a6
- Migrating from Crossfire 0.3a4 to 0.3a5
Once a connection has been established with a remote host, Crossfire
will wait until it receives a UTF-8 string which matches
If Crossfire was started as a server it will reply with an
acknowledgement that matches
The handshake can also be modified to include the names of tools that should be enabled when the server starts. More information about tool support and how to enabled / disable them can be found on the Tools API page.
The complete list of commands that Crossfire supports can be found on the Commands page. All of the command definitions describe the packet form(s), the request arguments, the response values and examples.
Crossfire provides a mechanism where the functionality of the protocol can be extended by clients through the use of
tools. Tools can be contributed as described in the Tools API.
Crossfire, by default, provides some of its core functionality through the use of tools. The default set of tools built into Crossfire includes: