Steam Community :: Guide :: Comprehensive guide to convar "nb

Store Page

Team Fortress 2

All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Team Fortress 2 > Guides > sigsegv's Guides

27 ratings

Comprehensive guide to convar "nb_command"

By sigsegv

A detailed list of command strings accepted by the nb_command convar, which can be used to make Team Fortress bots (especially MvM robots) do various things, primarly for testing purposes. These commands are undocumented; I figured out what they were by reverse-engineering the game code.

Award

Created by

sigsegv
Offline

Category: Modding or Configuration

Languages: English

Posted

16 Sep, 2015 @ 11:49pm

668	Unique Visitors
17	Current Favorites

Guide Index

Overview

Summary

Command: "taunt"

Command: "despawn"

Command: "disguise"

Command: "cloak"

Command: "uncloak"

Command: "build sentry at nearest sentry hint"

Command: "goto action point"

Command: "attack sentry at next action point"

Comments

Summary

The nb_command console variable sends a command string to all NextBots in the game. It requires sv_cheats 1, so it's something that you'll only be able to do on a local server for the most part.

Command: "taunt"

Forces all bots to switch to behavior CTFBotTaunt, which effectively functions the same as if the bot had used the old behavior of the "g" key (the "taunt" console command, not "+taunt").

Command: "despawn"

Forces all bots to switch to behavior CTFDespawn, which causes each one to be kicked from the server in exactly the same manner as if you used the console command "kickid" on them.

Command: "disguise"

For all NextBots: if the bot is a spy and is allowed to disguise, then it generates a random number between 1 and 9 and disguises as that class number of the other team.

Command: "cloak"

For all NextBots: if the bot is a spy and is not currently cloaked, it is forced to press its alt-fire button.

This command wasn't designed with the Dead Ringer in mind. Because the spy doesn't become cloaked when priming the DR, this command will toggle whether the DR is primed. If his DR has been triggered and he is cloaked, it will do nothing.

Command: "uncloak"

For all NextBots: if the bot is a spy and is currently cloaked, it is forced to press its alt-fire button.

This command wasn't designed with the Dead Ringer in mind. Because the spy doesn't become cloaked when priming the DR, this command won't do anything unless the DR has been triggered. If the DR cloak has been triggered, then this command will make the spy uncloak.

Command: "build sentry at nearest sentry hint"

For all NextBots: if the bot is an engineer, it will search for the nearest "bot_hint_sentrygun" entity that isn't already in use by another engineer.

If it is able to find one, then its behavior is forced to switch to CTFBotEngineerBuilding, which is the main non-MvM engiebot AI behavior.

Command: "goto action point"

Forces all bots to switch to behavior CTFGoToActionPoint.

This seems to be intended for training mode and doesn't do anything particularly useful.

Command: "attack sentry at next action point"

Forces all bots to switch to behavior CTFTrainingAttackSentryActionPoint. Basically, they'll path toward a sentry, and once they arrive, they will stare at it and press their fire key.

This seems to be intended for training mode and doesn't do anything particularly useful.

4 Comments

< >

compromised 7 Jan, 2017 @ 8:04am

is this related to the sv_allow_point_servercommand
cause there is a training map that I want to use but doesnt spawn enough bots
was wondering if I could keep the maps functionality (the bots follow a certain route) but still make it spawn more bots

Speedo 22 Sep, 2015 @ 12:11pm

Thanks

𝗦𝗢𝗡𝗜𝗖. 22 Sep, 2015 @ 11:55am

helpful/comblicated

pepy 22 Sep, 2015 @ 10:56am

Do moar plesh
:3

< >