Developer console: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
No edit summary
No edit summary
Line 75: Line 75:
:Difficulty ("skill")
:Difficulty ("skill")
-->
-->
== Setting cvars with C++ ==
Simply:
[the_cvar]->SetValue( [value] );
If you do not have access to a cvar, do this first:
ConVar *[the_cvar] = cvar->FindVar( "[the_cvar]" );
{{tip|This code works even for closed-source cvars.}}
{{todo|How to directly execute concommands?}}


== See also ==
== See also ==


* [[Developer Console Control]] - for programmers
* [[Console Command List]] - partial list of console commands and variables
* [[Console Command List]] - partial list of console commands and variables
* [[:Category:Console Commands]] - list of written articles for console commands
* [[:Category:Console Commands]] - list of written articles for console commands
Line 103: Line 91:


[[Category:Modding]]
[[Category:Modding]]
[[Category:Programming]]

Revision as of 13:43, 15 January 2009

Console output for Episode Two

The console provides a command-line interface for the advanced configuration of Source games. Just about any configuration task can be completed from the console, and indeed they often have to be.

Enabling the console

The console starts disabled. To enable it, load the game and visit Options > Keyboard > Advanced. Once enabled, it can be opened and closed by pressing the button above Tab .

(This should work regardless of your keyboard layout. If it doesn't, add -console to the game's launch options and type bind your_key toggleconsole.)

Submitting

The grey box across the bottom of the console window is where commands are entered. They come in two forms: commands and variables. Commands are simply keywords, but variables ("cvars") require a value of some sort before they are accepted. When setting a cvar you might type something like this :

find_ent point_viewcontrol

When you've finished typing, hit Return or Enter to submit. You'll see everything you type 'echoed' to the console with a preceding ].

A few notes:

  • Multiple values are separated with spaces. If a value contains a space, surround it with quote marks. (e.g. say "Hello everyone on the server".)
  • The console will suggest commands and sometimes values in a pop-out box beneath the input field. Press / to navigate the list and Tab to accept the highlighted suggestion.
  • Only "archived" cvars are stored after the game closes. Use autoexec if you want to set any others when a game loads.
  • Some commands are serverside, others clientside. In multiplayer you can only set clientside ones.
  • There are many command prefixes. The most common are cl ("clientside") and sv ("serverside").

Useful commands

find <term>
The ever-useful find command searches console command names and descriptions for the term your provide.
help <command name>
Displays any help text for a command, without affecting its value.
sv_cheats <bool>
Most cvars that affect gameplay, especially in multiplayer games, are flagged as "cheats". Submit sv_cheats 1 to unlock them.
Note.pngNote:You will never be VAC banned for using built-in cheat commands.
developer <0-2>
Developer mode enables more verbose console output, enables cheats and the console automatically, and makes various other useful changes. If set to 2, the last few lines of console output will be printed at the top of the screen as well.
con_log <file>
condump
Use one of these commands if you want to record what goes on in the console for later use. con_log writes output constantly, while condump records only when invoked.
Tip.pngTip:The console only displays 241 lines at a time. Use con_log if you run up against this.


See also

Template:Otherlang:en Template:Otherlang:en:es, Template:Otherlang:en:jp, Template:Otherlang:en:pl, Template:Otherlang:en:ru, Template:Otherlang:en:zh-tw