Usage Guide

This guide will give you an overview on how to work with the new Bot manager command line system to interact with and administer the running bots.

Bot Manager Commands

The Bot Manager allows a user to command the bots, whether in separate processes or in separate threads. It allows the user/administrator to interact with the bots via the console window using text commands.

• start <bot>: Start the bot that is at the index specified in settings.json.
• stop <bot>: Stop the bot that is at the index specified in settings.json.
• show bots: Dump the bot configuration to the console
• help: Shows available commands
• auth <bot>=<code> : Use to enter in a Steam Guard authentication string.
• exec <bot> <command> : Use to send command to the bot. It can be command from system commands listed below or your custom command implemented in UserHandler. If command is not on the list it will be routed to your UserHandler.
  • linkauth : Start interactive procedure for linking mobile authenticator to the bot account.
  • getauth : Generate current authenticator code (only works with connected authenticator).
  • unlinkauth : Remove mobile authenticator from bot steam account.
• input <bot> <input> : Use to send additional data to the bot. It can be required with some of systems commands or by your custom command. You can wait for this input in your UserHandler with Bot.WaitForInput()

---

• <bot> -> is a zero based index value or bot username.
• <code> -> is a steamguard code.
• <command> -> is a command which will be sent to the bot.
• <input> -> custom data depends on current operation

---

The UseSeparateProcesses option from settings.json controls whether the bots will will remain part of the same process but use separate threads or have separate processes per bot. The bot manager commands will work either way.