From Hive Mind LOIC
This document refers to the control language used in the upcoming release. It is not yet implemented. For the current hive control language, google around for NewEraCrackers documentation.
The structure of a command
- This is the beginning delimiter of the command string, which must be supplied with EVERY command, and must have a valid number. This is also the group identifier. Since this protocol has been developed to manage many targets through 1 interface, and we can't be certain whether commands are serialized, it was necessary to enable it to recognize one set of commands from another. As such, each set of commands has its own group identifier. The preference is given to higher group identifier. As such commands with group number 1 (G=1), are ignored/cleared in favour of commands with group number 2 (G=2), which are ignored/cleared in favour of commands with group number 3 (G=3), and so on. Each node will maintain which group number it currently has loaded, and if it reads a command from a higher group number, it will clear all its targets and methods, then set its current group number to the new group, and not process any lower numbered commands. This provides a way to ensure that all clients are using the same commands, regardless of conflicts with previous commands, or whether (due to connection trouble) they missed a set, or what order the commands come in. As such, to change/delete a target/method, a new control group must be created.
- This is the address of the target to be attacked. It also works as a unique identifier for each target. This must be used when sending target specific commands. It can be an IP, an IP:PORT, or a URL. From the this parameter, the desired IP, Port, Host, and Subsite, will be extracted.
... Other commands will go here! ...
- This is the ending delimiter, which tells the message processor that it has reached the end of the message. This can be omitted, and if it is, the end of the string will be considered the ending delimiter.
... to be continued!