Developer: Difference between revisions
m (Changed parameters of {{this is a}} to comply with the updated version. This action was performed by a bot.) |
Gameplayer (talk | contribs) No edit summary |
||
| Line 6: | Line 6: | ||
Valid values are: | Valid values are: | ||
*0: No debugging information (standard behavior) | *0: No debugging information (standard behavior) | ||
*1: Standard debugging information | *1: Standard debugging information; console messages appear in the top-left of the player's HUD, execution of certain commands like [[ent_text]] and [[npc_kill]] is allowed | ||
*2: More debugging information; console displays input/output events, errors and events in scripted sequences, etc. | |||
*3: Same as 2, but with more console messages {{todo|Does this introduce any of the debugging stuff otherwise associated with 4?}} | *3: Same as 2, but with more console messages {{todo|Does this introduce any of the debugging stuff otherwise associated with 4?}} | ||
*4: Highest(?) level of debugging information; | *4: Highest(?) level of debugging information; bounding boxes can show up on objects with VPhysics errors, etc. | ||
<code>developer 4</code> adds additional on-screen info like where the clients crosshair is pointing (not in HL2/Source 2013, shows the crosshair of all the players in multiplayer) and shows hitboxes and boundboxes when collision anomalies or errors occur. | <code>developer 4</code> adds additional on-screen info like where the clients crosshair is pointing (not in HL2/Source 2013, shows the crosshair of all the players in multiplayer) and shows hitboxes and boundboxes when collision anomalies or errors occur. | ||
Revision as of 09:09, 25 August 2024
developer is a console variable available in all 
Source games. It enables various levels of developer debugging options. This includes entity diagnostic information which will be printed to the console and also at the top of the screen.
Syntax: developer <value>
Valid values are:
- 0: No debugging information (standard behavior)
- 1: Standard debugging information; console messages appear in the top-left of the player's HUD, execution of certain commands like ent_text and npc_kill is allowed
- 2: More debugging information; console displays input/output events, errors and events in scripted sequences, etc.
- 3: Same as 2, but with more console messages Todo: Does this introduce any of the debugging stuff otherwise associated with 4?
- 4: Highest(?) level of debugging information; bounding boxes can show up on objects with VPhysics errors, etc.
developer 4 adds additional on-screen info like where the clients crosshair is pointing (not in HL2/Source 2013, shows the crosshair of all the players in multiplayer) and shows hitboxes and boundboxes when collision anomalies or errors occur.
Developer mode can also be enabled via the -dev or -developer command line switches, either as a shortcut or Steam command line. The 
Left 4 Dead series relies on this switch in order to load into developer mode.
See also
Other console commands and variables that a developer may find useful include:
If you are looking for information about being a developer for Valve games, you may instead find these pages useful: