Func portal bumper

Not using a portal bumper

How to place the bumper in Hammer

The result - a portal will be bumped to fit on the concrete

Entity description

It tells Portal to 'bump' portals that cannot open inside it away. Use it when a portal-proof surface runs directly on to a portal-friendly one.

You don't need to use one if there is an angle in the surface (e.g. the corners of a room).

Note:Each func_portal_bumper must stick at least two units out from the surface.

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 bumping functionality

Activate

Turn on bumping functionality

Toggle

Toggle bumping 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.