Info particle system

Template:Base point It dispatches and offers some control over a specified particle system.

Keyvalues

Particle System Name ([todo internal name (i)]) <string>: The name of the particle system to spawn. NOT the name of a PCF file!

Start Active? ([todo internal name (i)]) <boolean>: Whether the particle system should begin as soon as the entity spawns.

Control Point 1 ([todo internal name (i)]) to Control Point 63 <targetname>: Parents a control point to the given entity's origin. If any value is left blank all those following it will be ignored.
Tip:Control point 0 is the origin of the info_particle_system itself.

Note:Because the control point is configured on the client, the entity you specify must exist there. This means that most invisible entities (info_target in particular) will not work. Your best bet is another info_particle_system with a blank system name.

Control Point 1's Parent ([todo internal name (i)]) to Control Point 7's Parent <integer>: The control point to act as a parent to this one.

Parentname:

Parent (parentname) <targetname>: Specifies a movement parent. An entity will maintain its initial offset from its parent. An attachment point can be added to the end of the name, separated by a comma.

Pitch Yaw Roll (Y Z X) (angles) <QAngle>: This entity's orientation in the world. Pitch is rotation around the Y axis, yaw is the rotation around the Z axis, roll is the rotation around the X axis.

Name (targetname) <string>[ Edit ]: The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g. parentname or target).
Also displayed in Hammer's 2D views and Entity Report. See also: Generic Keyvalues, Inputs and Outputs available to all entities

Start,Stop: Tell the particle system to start/stop emitting.
Note:To forcibly restart an effect, you must fire Stop first. Start has no effect if the server thinks the system is already running.

DestroyImmediately (in all games since ): Particle System disappears immediatly instead of fading out

Parentname:

SetParent <stringRedirectInput/string>: Move with this entity. See Entity Hierarchy (parenting).

SetParentAttachment <stringRedirectInput/string>: Change this entity to attach to a specific attachment point on its parent. The entity will teleport so that the position of its root bone matches that of the attachment. Entities must be parented before being sent this input.

SetParentAttachmentMaintainOffset <stringRedirectInput/string>: As above, but without teleporting. The entity retains its position relative to the attachment at the time of the input being received.

ClearParent: Removes this entity from the the movement hierarchy, leaving it free to move independently.