$contents: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 3: Line 3:


== Syntax==
== Syntax==
  $contents "<bone_name>" "<content_type_1>" "<content_type_2>" "<content_type_3>"
  $contents "<content_type_1>" "<content_type_2>" "<content_type_3>"


* The current contents types you can use are:
* The current content_types you can use are:
; <code>grate</code>: Makes it be a grate (not solid to bullets, solid to everything else)
; <code>grate</code>: Makes it be a grate (not solid to bullets, solid to everything else)
; <code>monster</code>: Makes it be marked as an NPC
; <code>monster</code>: Makes it be marked as an NPC

Revision as of 20:40, 30 March 2008

The QC command $contents specifies the contents to use for contents-mask tests during non-hitbox traces.

  • This feature was specifically added to allow us to make things like fences out of props instead of brush models.

Syntax

$contents "<content_type_1>" "<content_type_2>" "<content_type_3>"
  • The current content_types you can use are:
grate
Makes it be a grate (not solid to bullets, solid to everything else)
monster
Makes it be marked as an NPC
notsolid
Makes it be not solid to anything
solid
Makes it be solid (usually useful only for the $jointcontents command to make a solid child of a non-solid parent)
ladder
Make it be a ladder

Example

$contents "monster" "grate"