Developer: Difference between revisions
Jump to navigation
Jump to search
EloreLtroc (talk | contribs) No edit summary |
mNo edit summary |
||
| (38 intermediate revisions by 22 users not shown) | |||
| Line 1: | Line 1: | ||
{{stub}} | {{stub}} | ||
{{for|information about being a developer for Valve games|[[Steam 3rd Party Mod Support]]}} | |||
{{this is a|console variable|name=developer}} 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 (amount of lines shown adjustable by {{cmd|contimes}} cvar) | |||
::* execution of [[:Category:Developer mode commands|certain commands]] like {{command|ent_text}} and {{command|npc_kill}} is allowed | |||
::* [[VPhysics]] penetration errors are displayed in the [[Map_(level_design)|map]] | |||
::* console logs {{command|exec}}-ed scripts | |||
::* etc. | |||
*2: More debugging information; console displays: | |||
::* [[Inputs_and_Outputs|input/output]] events | |||
::* errors and events in [[scripted_sequence|scripted sequences]] | |||
::* loaded [[model|models]] during map load | |||
::* entities transferred to next map when changing level | |||
::* [[NPC|NPCs]] that aren't in [[squads]] | |||
::* notification when orphaned [[Entity_Hierarchy_(parenting)|child entities]] are removed when parent entity no longer exist | |||
::* 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. | |||
<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. | |||
{{todo|Better details here!}} | |||
Developer mode can also be enabled via the '''-dev''' or '''-developer''' [[Command Line Options|command line switches]]. | Developer mode can also be enabled via the '''-dev''' or '''-developer''' [[Command Line Options|command line switches]], either as a shortcut or Steam command line. The {{l4ds|4.1}} relies on this switch in order to load into developer mode. | ||
== See also == | == See also == | ||
Other console commands and variables that a developer may find useful include: | Other console commands and variables that a developer may find useful include: | ||
*[[sv_cheats]] | * [[sv_cheats]] | ||
*[[impulse]] | * [[impulse]] | ||
If you are looking for information about being a developer for Valve games, you may instead find these pages useful: | If you are looking for information about being a developer for Valve games, you may instead find these pages useful: | ||
* [[Steam 3rd Party Mod Support]] | * [[Steam 3rd Party Mod Support]] | ||
Latest revision as of 09:56, 27 September 2024
For information about being a developer for Valve games, see Steam 3rd Party Mod Support.
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:
- 2: More debugging information; console displays:
- input/output events
- errors and events in scripted sequences
- loaded models during map load
- entities transferred to next map when changing level
- NPCs that aren't in squads
- notification when orphaned child entities are removed when parent entity no longer exist
- 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.
Todo: Better details here!
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: