Difference between revisions of "Message queue"
(Added history, tuning, and scripting) |
m (1 revision imported) |
(No difference)
|
Latest revision as of 08:20, 1 December 2017
The message queue is a system through which all messages sent to the Battle.net server must pass through. When a message is sent (using the AddQ function), it is added to the queue. The queue then holds the message until it has been determined that it's safe to send. This is done using a credit system, in which the bot is "charged" credits for each packet sent, and passively earns credits over time.
History
StealthBot's queue system is based off of the one used by JavaOp, by iago[x86]. It was originally written in 2004, and then ported to StealthBot in 2009.
Tuning
There are several config overrides that allow for fine tuning of the message queue. You should not touch these unless you know what you are doing, as it may result in your being banned from Battle.net.
Section | Key | Description | Default |
---|---|---|---|
Override | QueueMaxCredits | The maximum number of credits that the bot can have. | 600 |
Override | QueueCostPerPacket | The amount of credits paid for each sent packet. | 200 |
Override | QueueCostPerByte | The amount of credits paid for each byte sent. | 7 |
Override | QueueCostPerByteOverThreshhold | The amount of credits paid for each byte after the threshold is reached. | 8 |
Override | QueueStartingCredits | The number of credits the bot starts with. | 200 |
Override | QueueThreshholdBytes | The length of a message before triggering the threshold. | 200 |
Override | QueueCreditRate | The amount of time (in milliseconds) to earn one credit. | 7 |
Scripting
The scripting system is given access to the Queue through the Queue object.