Frictional Game Wiki

<h1>Areas</h1> <div class="level1"> <p> Areas are oblong-shaped collision zones which can trigger callbacks when the player or other objects enter them; they are also often used as position markers for things spawned in code such as sounds or particle effects. </p> <p> HPL3 ships with several different area types - here's a quick summary of them and of some of their properties. </p> </div> <h2>Trigger</h2> <div class="level2"> <p> The most commonly used type of area, used for all sorts of purposes. </p> </div> <h3>Important Properties</h3> <div class="level3"> </div> <h4>BlocksLineOfSight</h4> <div class="level4"> <p> If true, this area acts as a blocker for AI seeing the player. </p> </div> <h4>CC_Entities, CC_Funcs</h4> <div class="level4"> <p> Collision callbacks - for example, if you set CC_Entities to <code>player</code> and CC_Funcs to <code>TriggerHitArea</code> then TriggerHitArea will be called in your map script whenever the player enters or leaves the area. </p> </div> <h4>PlayerLookAtCallback</h4> <div class="level4"> <p> Called when the player has the area on-screen. Various other properties in the same section modify exactly when that happens. </p> </div> <h4>PlayerInteractCallback</h4> <div class="level4"> <p> Makes the area interactable, and triggers this callback when the player interacts with it. You can also set <code>CustomInteractIcon</code> etc. </p> </div> <h2>AmbientLight</h2> <div class="level2"> <p> The player, by default, casts a small point light around him so that you can see things even when the room is very dark. This area type changes that ambient light to fit the current area. </p> </div> <h3>Important Properties</h3> <div class="level3"> </div> <h4>Type</h4> <div class="level4"> <p> Indoors / Outdoors / None </p> </div> <h2>CameraAnimation</h2> <div class="level2"> <p> Used as a camera viewpoint in a camera animation. See <a href="/doku.php?id=hpl3:game:scripting:user_modules:camera_animation" class="wikilink1" title="hpl3:game:scripting:user_modules:camera_animation">Camera Animation</a>. </p> </div> <h2>Climb</h2> <div class="level2"> <p> This area becomes interactable; when you interact, you will climb up to a specified foot position. It's used for things like climbing into vent shafts or climbing up on to a nearby table or something; for higher climbs, you probably want a camera animation or a ladder instead. </p> </div> <h3>Important Properties</h3> <div class="level3"> </div> <h4>FeetPosition</h4> <div class="level4"> <p> Name of an entity (usually a trigger area) specifying where the feet should land after the climb. </p> </div> <h4>Crouch</h4> <div class="level4"> <p> Specify if the player should be automatically crouched after the climb (useful for vent shafts). </p> </div> <h2>Crawl</h2> <div class="level2"> <p> The player will be crawling on their belly while in this area, and can't run or stand up. Useful for vent shafts. </p> </div> <h2>Datamine</h2> <div class="level2"> <p> The player can interact with this area as if it were a datamine prop - see <a href="/doku.php?id=hpl3:game:scripting:user_modules:datamine" class="wikilink1" title="hpl3:game:scripting:user_modules:datamine">Datamine</a> </p> </div> <h2>DatamineAudioSource, DatamineAnimNode</h2> <div class="level2"> <p> Currently unused. </p> </div> <h2>Description</h2> <div class="level2"> <p> Used with the <a href="/doku.php?id=hpl3:game:scripting:user_modules:description" class="wikilink1" title="hpl3:game:scripting:user_modules:description">Description</a> module. Not used in SOMA. </p> </div> <h2>Distortion</h2> <div class="level2"> <p> This area will apply a <a href="/doku.php?id=hpl3:game:scripting:user_modules:distortion_effects" class="wikilink1" title="hpl3:game:scripting:user_modules:distortion_effects">Distortion Effect</a> to the player while they are in it. </p> </div> <h2>DoorwayTrigger</h2> <div class="level2"> <p> This area is really useful for telling you when the player has walked into a particular part of the map. You set up a doorway with the Z-axis pointing in to the 'inside' and away from the 'outside'. Now when the player walks in through the door, the DoorwayCallback is called with an <code>alState</code> parameter of 1. When the player walks out through the door, the callback is called with an <code>alState</code> of -1. </p> <p> You can also link sets of doorways, which is a great way to figure out if the player is inside an irregular space. If you specify the <code>DoorwayGroup</code> property, then you can use the function <code>Doorway_PlayerIsInGroup</code> to check if the player has crossed into the space delimited by these doorways. (Essentially, if you cross any of the doorways going 'inwards' so <code>alState</code>==1, then you are in the group; crossing any going 'outwards' so <code>alState</code>==-1 means you are outside the group). </p> </div> <h3>Important Properties</h3> <div class="level3"> </div> <h4>DoorwayEntity</h4> <div class="level4"> <p> This acts just like CC_Entities on an area - it just specifies which entity to check for collisions with. This is usually <code>player</code>. </p> </div> <h4>DoorwayCallback</h4> <div class="level4"> <p> Called when the <code>DoorwayEntity</code> goes in or out of the doorway. </p> </div> <h2>Hide</h2> <div class="level2"> <p> This marks of a specific area as somewhere that the player can hide i.e. they will no longer be visible to AI. This is not used in SOMA. </p> </div> <h2>InteractAux</h2> <div class="level2"> <p> This is used to expand the interaction area of another entity such as a prop; so that you can, for example, give a small button a bigger interact area. For all purposes, interacting with the area is treated as if you're interacting with the prop itself. If you set interaction disabled on the prop, the area will deactivate too. </p> </div> <h3>Important Properties</h3> <div class="level3"> </div> <h4>InteractParent</h4> <div class="level4"> <p> The entity to interact with. </p> </div> <h2>Ladder</h2> <div class="level2"> <p> This is used to allow the player to climb ladders. Position the ladder area up the ladder prop. Note that in SOMA rungs have to be 0.5 units apart, and the ladder area itself has to be a multiple of 0.5 units tall and aligned to the rungs for the animation to work properly. </p> </div> <h3>Important Properties</h3> <div class="level3"> </div> <h4>Exit_Top, Exit_Top_Crouching</h4> <div class="level4"> <p> Use these to specify an area to move to when you step off the top of the ladder (usually a Trigger area). </p> </div> <h4>Exit_Bottom, Exit_Bottom_Crouching</h4> <div class="level4"> <p> Use these to specify an area to move to when you step off the bottom of the ladder (usually a Trigger area). </p> </div> <h2>Liquid</h2> <div class="level2"> <p> Creates an area of liquid - useful for pools of water or for use in SOMA's airlocks. You can control waves, surface colors, fog under water etc. - properties should be reasonably self-explanatory. </p> </div> <h2>MapTransfer</h2> <div class="level2"> <p> Map Transfer areas are used in map transitions; anything within a Map Transfer area is preserved as the next map is loaded. </p> </div> <h2>PathNode</h2> <div class="level2"> <p> Pathnodes are points rather than areas; they are used in AI for the pathfinding system. </p> </div> <h2>PlayerStart</h2> <div class="level2"> <p> Player Start areas are where the player will appear as the result of a map load (by default, the player appears at <code>PlayerStartArea_1</code>, although that can be changed) or as the result of a <code>Player_Teleport()</code> call. </p> </div> <h3>Important Properties</h3> <div class="level3"> </div> <h4>Crouching</h4> <div class="level4"> <p> Specifies whether the player should be crouching when they appear at that spot. </p> </div> <h2>PosNode</h2> <div class="level2"> <p> Not used in SOMA. </p> </div> <h2>Rope</h2> <div class="level2"> <p> Not used in SOMA. </p> </div> <h2>Sit</h2> <div class="level2"> <p> Sit areas specify an area that the player can interact with to sit down. </p> </div> <h2>Soundscape</h2> <div class="level2"> <p> Soundscape areas are used to set up the ambient sound for particular areas. You'd generally have one soundscape area for every room. </p> </div> <h2>Sticky</h2> <div class="level2"> <p> Sticky areas are used to attach other entities to (normally <code>Prop_Grab</code>) - when the entities are pulled away, there'll be resistance, and if you don't pull hard enough they'll snap back. This is used to implement things like pulling power cables from sockets or attaching cables to sockets. </p> </div> <h3>Important Properties</h3> <div class="level3"> </div> <h4>AttachableBodyName</h4> <div class="level4"> <p> Name or names of bodies that can be attached to this area. Accepts wildcards. </p> </div> <h4>CanDetach</h4> <div class="level4"> <p> If true then the connected body can be detached. </p> </div> <h4>RequiresInteraction</h4> <div class="level4"> <p> If true then bodies will only detach or attach if the player is actually interacting with them (as opposed to e.g. walking into an object to knock it free). </p> </div> <h4>MoveBody, RotateBody</h4> <div class="level4"> <p> Whether to orient the body to the attach position. </p> </div> <h4>AttachFunction</h4> <div class="level4"> <p> Called when an entity is attached to this area. </p> </div> <h4>DetachFunction</h4> <div class="level4"> <p> Called when an entity is detached from this area. </p> </div> <h4>SpringyActive, SpringyForceMul, SpringyDetachTime</h4> <div class="level4"> <p> Use these to give some resistance to the detachment or attachment - so that the attach area 'sucks in' the body. </p> </div> <h2>Tool</h2> <div class="level2"> <p> If the player walks into a tool area and has the specified tool in their inventory, then it will automatically be equipped (i.e. brought out and shown on screen in their hands). This is what is used for showing the Omnitool next to an airlock control panel. </p> </div> <h3>Important Properties</h3> <div class="level3"> </div> <h4>ToolsToEquip</h4> <div class="level4"> <p> A list of tools to bring out when in this area. </p> </div> <h4>ConnectedToolAreas</h4> <div class="level4"> <p> Other tool areas that are part of the same group; this is to make it easy to set up irregularly shaped tool areas by combining multiple rectangular areas. </p> </div> <h4>LookEntities</h4> <div class="level4"> <p> Specify a look entity, and the tool will only be brought out if the player is facing that entity. In most cases, it would be the object that they can interact with e.g. the airlock panel. This is used so that the tool isn't brought out if the player backs in to a tool area. </p> </div> <h2>AgentRepel</h2> <div class="level2"> <p> This area type repels AI creatures who enter it. </p> </div> <h3>Important Properties</h3> <div class="level3"> </div> <h4>ExitArea</h4> <div class="level4"> <p> Specifies a particular point (usually a TriggerArea) to head towards if the agent enters this area. </p> </div> <h2>VisibilityArea, VisibilityPortal</h2> <div class="level2"> <p> These two area types are used to toggle the visibility of large amounts of geometry, which is useful in optimising maps. See <a href="/doku.php?id=hpl3:game:visibility_area" class="wikilink2" title="hpl3:game:visibility_area" rel="nofollow">Visibility Areas</a> </p> </div> <h2>Zoom</h2> <div class="level2"> <p> See also <a href="/doku.php?id=hpl3:game:readables" class="wikilink1" title="hpl3:game:readables">Readables</a>. </p> <p> A zoom area shows a magnifying glass icon when the player interacts with it; when they interact, the player's viewpoint is moved in towards the area, so that they're focused on the contents. You can also add optional text or GUI to pop up over the area. </p> <p> This is used in SOMA for things like whiteboards, maps and pictures on the wall. </p> </div> <h3>Important Properties</h3> <div class="level3"> </div> <h4>TextCategory, TextEntry</h4> <div class="level4"> <p> Specify the text to appear when you click interact for a second time. This is used for simple descriptive text. </p> </div> <h4>OnGuiFunction</h4> <div class="level4"> <p> Instead of text appearing, if you specify an OnGuiFunction that will be called instead. This is useful for drawing more complex text layouts such as the key locations on a map. </p> </div>