Func noportal volume

Entity description

It defines a region in which no portal can be placed.

When placed in contact with or intersecting a portalable surface, a func_noportal_volume entity prevents the placement of portals on that surface that overlap its area. If the portal is "fired" inside its area, the portal gun sound is a kind of "squelch" and no portal appears. If the portal is "fired" outside but close to the edge of the func_noportal_volume, then the portal will, if possible, appear but will be moved away from the entity so that no part of the portal overlaps it. A func_noportal_volume that is not in contact with a portalable surface has no effect. It should protrude at least two units from the surface. The recommended texture for the brush is tools/toolsinvisible.

A func_portal_bumper entity is frequently found paired with a func_noportal_volume. It is not clear what functionality this adds.

Warning:The blocking behaviour is checked based on the bounding box, so convex volumes should be multiple entities.

Keyvalues

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

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.

Flags

• 1 : Start inactive

Inputs

Deactivate

Turn off blocking functionality

Activate

Turn on blocking functionality

Toggle

Toggle blocking functionality

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.