Func portal bumper: Difference between revisions
Jump to navigation
Jump to search
Note:Each func_portal_bumper must stick at least two units out from the surface.
(Cleanup) |
(Rewrite Template:Lang to Template:LanguageBar. This action was performed by a bot.) |
||
| (11 intermediate revisions by 9 users not shown) | |||
| Line 1: | Line 1: | ||
{{LanguageBar|title=func_portal_bumper}} | |||
{{this is a|brush entity|name=func_portal_bumper|series=Portal}} | |||
{{CD|CFuncPortalBumper|base=CBaseEntity}} | |||
__TOC__ | |||
You don't need to use one if there is an angle in the surface (e.g. the corners of a room). | ==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. | |||
While having this is not ''absolutely'' necessary, it does make your puzzles much more user friendly. 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.}} | |||
== Usage == | |||
<gallery mode="packed" heights="256px"> | |||
File:testbumper0000.jpg|Not using a portal bumper | |||
File:Portalbumperplacement.JPG|How to place the bumper in Hammer | |||
File:testbumper0001.jpg|The result - a portal will be bumped to fit on the concrete | |||
</gallery> | |||
== Keyvalues == | == Keyvalues == | ||
{{KV Targetname}} | {{KV Targetname}} | ||
| Line 13: | Line 23: | ||
== Flags == | == Flags == | ||
{{Fl|1|Start inactive}} | |||
== Inputs == | == Inputs == | ||
{{ | {{I|Deactivate|Turn off bumping functionality}} | ||
{{ | {{I|Activate|Turn on bumping functionality}} | ||
{{ | {{I|Toggle|Toggle bumping functionality}} | ||
{{I Targetname}} | {{I Targetname}} | ||
{{I Parentname}} | {{I Parentname}} | ||
Latest revision as of 17:55, 18 July 2025
func_portal_bumper is a brush entity available in 
Portal series.
 Class hierarchy
|
|---|
| CFuncPortalBumper |
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.
While having this is not absolutely necessary, it does make your puzzles much more user friendly. 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.Usage
Not using a portal bumper
How to place the bumper in Hammer
The result - a portal will be bumped to fit on the concrete
Keyvalues
- Name (targetname) <string>[ Edit ]
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentnameortarget).
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
- Start inactive : [1]
Inputs
- Deactivate
- Turn off bumping functionality
- Activate
- Turn on bumping functionality
- Toggle
- Toggle bumping functionality
Parentname:
- SetParent <string>
- Move with this entity. See Entity Hierarchy (parenting).
- SetParentAttachment <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 <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.