Sven Co-op - User contributions [en]

Worldspawn

2023-11-12T16:43:46Z

Tunac: No link to sky list exists. Hiding text that claims so.

{{Entity_Infobox
| title=
}}

Worldspawn is non-interactive entity, everything that builds a map except placed or spawned entities- brushes, sky, tool textures e.t.c. Map itself is an unique entity, which options you can access by going into 'Map'-->'Map properties'. Environmental death are caused
by World e.g. when player dies because of fall damage, the entity which killed player is "worldspawn". Whenever mapper is placing new brush into the map, it's becomes the part of the "worldspawn". You can change important settings of your map like sky texture to use, render distance, replacement files and even player models restrictions.

== Keyvalues ==

{{Entity_keyvalue|Map Description / Title|message|Title of the map. The usage is unknown- it won't show any kind of text.}}
{{Entity_keyvalue|Environment Map|skyname|Name of sky to use, e.g. 'cliff'. You can check all skies names by going into 'gfx'-->'env' folder. Note that every sky is split into 6 different files, two last characters represent the direction. Remember to NOT include those characters (as well as '_' symbol in some of skies), if you do, the default sky will be used ('desert'). To determine where the sky will be seen, use 'sky' texture on surfaces where you want your sky.}}
{{Entity_keyvalue|CD Track to play|sounds|Doesn't work- it's an old method to play music from CD.}}
{{Entity_keyvalue|Default light level|light|Seems to not working.}}
{{Entity_keyvalue|Default Wave Height|WaveHeight|Wave height of func_water entities. It is not overriding func_water "Wave Height" setting.}}
{{Entity_keyvalue|Max viewable Distance|MaxRange|Render distance, higher values for farther distance but slower render. Decrease this value greatly improves performance but causes player to see end of the render plane what looks terrible.}}
{{Entity_keyvalue|Chapter Title Message|chaptertitle|Simple method to show a text message on screen- it's a chapter-type string that appears on map start.}}
{{Entity_keyvalue|Level Fade In|startdark|If set to 'Yes', the fade in effect (from completely dark to fully tranparent) will be applied as soon as map starts.}}
{{Entity_keyvalue|Display game title|gametitle|If set to 'Yes', the Half Life logo title (as seen in the beginning of Half-Life campaign) will be displayed.}}
{{Entity_keyvalue|New Level Unit|newunit|Removes data and global triggers from previous levels. Not applicable for Sven Co-op.}}
{{Entity_keyvalue|Map Team List|mapteams|Not supported- Sven Co-op does not spit players between teams.}}
{{Entity_keyvalue|Default Team|defaultteam|Same as above.}}
{{Entity_keyvalue|Roaming Monsters (node graph)|freeroam|If set to 'Yes', monsters will use nodes (info_node entities) to roam (walk from one point to another freely) at map start.

Note that each monster can override this behaviour by "Monster Roaming (nodes)" keyvalue.}}
{{Entity_keyvalue|Map Team List|mapteams|Not supported- Sven Co-op does not spit players between teams.}}
{{Entity_keyvalue|Default Team|defaultteam|Same as above}}
{{Entity_keyvalue|Custom Sentences File|sentence_file|You can specify your own "senteces.txt" file in a replacement of default sentences.}}
{{Entity_keyvalue|Custom Materials File|materials_file|You can specify your own "materials.txt" file in a replacement of default material sounds.

Example path string: "sound/mapname/filename.txt".}}
{{Entity_keyvalue|Global Sound Replacement File|globalsoundlist|Path to a sound replacement file to use.}}
{{Entity_keyvalue|Global Model Replacement File|globalmodellist|Path to a model replacement file to use.}}
{{Entity_keyvalue|Force Player Models|forcepmodels|List of models that can be used for this map, separated by comma "," symbol. Model names are the same as subfolders

in "models/player" folder. Note that models not listed here cannot be used in this map.}}
{{Entity_keyvalue|Minimum Game Version|scversion2|Game version required for this map to run. Leave that as it is.}}

== Changes ==

5.0 Steam Release: Added 'Custom Materials File' keyvalue, updated 'Minimum Game Version' keyvalue with new entries.

{{entity_title}}

[[Category:Entities]]
[[Category:Point entities]]

Trigger teleport

2023-09-08T08:33:23Z

Tunac: Improved description for Flag 64

{{Entity_Infobox
| title=
| type=b
}}

A brush entity which teleports a player to a destination of your choice as he enters the trigger.

== Keyvalues ==

{{Entity_keyvalue|Target|target|Name of the entity which the player is teleported to. Ideally an [[info_teleport_destination]] entity, but other entities can be used.}}
{{Entity_keyvalue|Delay before trigger|delay|Delay before the trigger_teleport triggers its target after being activated by an entering player or monster. This is usable if there is other entity we want to trigger that has same name as info_teleport_destination. }}
{{Entity_keyvalue|Target Path|netname|This is not a trigger destination as FGD says. This value is obsolete, use "Target" instead.}}
{{Entity_keyvalue|Allow Tiny Monsters|tiny_monsters|If set to 'Yes', monsters like cockroaches can trigger this entity as well as other monsters.}}
{{Entity_keyvalue|Teleport Cooldown Delay|teleport_cooldown|Time, in seconds, the trigger_teleport can be used (can teleport another entity/player) again.}}
{{Entity_keyvalue|Ignore Delays|teleport_ignore_delay|If set to 'Yes', "Teleport Cooldown Delay" will be ignored.}}
{{Entity_keyvalue|Start Inactive|teleport_start_inactive|If set to 'Yes', this Trigger starts disabled, which means it need to be triggered in order to work.}}
{{Entity_keyvalue|Teleport If Blocked|teleport_if_blocked|If set to 'Yes' (as it is by default), players will be teleported to target even if this target is blocked.
<br>
=== Inventory Rules, InventoryRules @BaseClass: ===
List of inventory-related keyvalues used with item_inventory entity. Whenever player is attempting to use an entity, the inventory test runs. If test result is negative, the entity won't work. In other case, entity can be used as normal, but only by player who passed the test with required inventory conditions:"Inventory: Need item(s)", item_name_required : Item(s) (names separated by spaces) required to use this entity.
Refers to "Item name" value of item_inventory.}}
{{Entity_keyvalue|Inventory: Need item(s) from group(s)|item_group_required|Groups (separated by spaces), in which carried items belong to, required to use this entity. Refers to "Item group name" value of item_inventory.}}
{{Entity_keyvalue|Inventory: Item count in group need have|item_group_required_num|Minimal number of items, that belong
to specified group, required to use this entity. Use with "Inventory: Need item(s) from group(s)" keyvalue. Value of '0' means that all items from current group are required.}}
{{Entity_keyvalue|Inventory: CAN'T have item|item_name_canthave|Items in player inventory that will fail the test, and disallow usage
of this entity. Refers to "Item name" value of item_inventory.}}
{{Entity_keyvalue|Inventory: CAN'T have item from group|item_group_canthave|Items in player inventory, which belong to specified group, that will fail the test, and disallow usage of this entity. Refers to "Item group name" value of item_inventory.}}
{{Entity_keyvalue|Inventory: Item count in group CAN'T have|item_group_canthave_num|Minimal number of items in player inventory, which belong to specified group, that will fail the test, and disallow usage of this entity. Refers to "Item group name"
value of item_inventory. Value of '0' means no single item from current group should be equipped to pass the test.}}
{{Entity_keyvalue|On pass: Ignore item's on use triggers?|pass_ignore_use_triggers|If set to 'Yes' item's trigger targets from 'Target: On use (by trigger)' will not be fired when item is used by this entity.}}
{{Entity_keyvalue|On pass: Drop item(s)|pass_drop_item_name|Items to force-drop when the test result is positive, and entity is used successfully. Refers to "Item name" value of item_inventory. Multiple item names are separated by spaces.}}
{{Entity_keyvalue|On pass: Drop item(s) from group(s)|pass_drop_item_group|Items to force-drop, that belong to specified group, when the test result is positive, and entity is used successfully. All items from this group will be dropped.
Refers to "Item group name" value of item_inventory. Multiple item names are separated by spaces.}}
{{Entity_keyvalue|On pass: Ignore item's on drop triggers?|pass_ignore_drop_triggers|If set to 'Yes' item's trigger targets from 'Target: On drop' will not be fired when item is dropped by this entity with 'Drop items(s)' events above.}}
{{Entity_keyvalue|On pass: Return item(s)|pass_return_item_name|Items to return to their starting positions when test result is positive. Refers to "Item name" value of item_inventory. Multiple item names are separated by spaces.}}
{{Entity_keyvalue|On pass: Return item(s) from group(s)|pass_return_item_group|Items, that belong to specified group, to return to their starting positions when test result is positive. All items from this group will be returned. Refers to "Item group name" value of item_inventory. Multiple group names are separated by spaces.}}
{{Entity_keyvalue|On pass: Ignore item's on return triggers?|pass_ignore_return_triggers|If set to 'Yes' item's trigger targets from 'Target: On return' will not be fired when item is returned by this entity with 'Return items(s)' events above.}}
{{Entity_keyvalue|On pass: Destroy item(s)|pass_destroy_item_name|Items to remove when test result is positive. Refers to "Item name" value of item_inventory. Multiple item names are separated by spaces.}}
{{Entity_keyvalue|On pass: Destroy item(s) from group(s)|pass_destroy_item_group|Items, that belong to specified group, to remove when test result is positive. All items from this group will be removed. Refers to "Item group name" value
of item_inventory. Multiple group names are separated by spaces.}}
{{Entity_keyvalue|On pass: Ignore item's on destroy triggers?|pass_ignore_destroy_triggers|If set to 'Yes' item's trigger targets from 'Target: On Destroy' will not be fired when item is destroyed by this entity with 'Destroy items(s)' events above.}}
{{Entity_keyvalue|Target: Inventory rules failed|target_on_fail|Entity to trigger whenever test result is negative.}}

== Flags ==

{{Entity_flag|1|Monsters|If set, monsters can trigger this.}}
{{Entity_flag|2|No Clients|If set, players won't be able to trigger this.}}
{{Entity_flag|4|Pushables|If set, func_pushable entities can trigger this.}}
{{Entity_flag|8|Everything else|If set, everything other than monsters, clients and pushables can trigger this. Does not exclude the above.}}
{{Entity_flag|16|Fire on Enter|Not applicable on trigger_teleport- it's already fires on enter!}}
{{Entity_flag|32|Fire on Exit|If set, trigger_once will fire as soon as something that entered it left it, instead of the instant something enters it.}}
{{Entity_flag|64|Random Destination|If multiple targets have the same <code>targetname</code>, one will be chosen as the destination randomly for every player as he enters the trigger.}}
{{Entity_flag|128|Relative Teleport|The player's destination will be the location of the destination plus his offset from the trigger_teleport's origin in the moment of the player entering the trigger. If you decide to use this, you will probably want to add an origin brush to your trigger_teleport.}}
{{Entity_flag|256|Keep Angles|Instead of copying the destination entity's angles onto the player as part of the teleportation, let the player keep his angles as they are.}}
{{Entity_flag|512|Keep velocity|Do not set the players velocity to 0 as he enters the trigger_teleport and keep his current velocity instead.}}
{{Entity_flag|1024|Rotate (Dest Angles)|Add the angles of the trigger_teleport's destination onto the player's angles.}}

== Notes ==

"Kill Target" and "Delay Before Trigger" keyvalues does not work on this entity. Also "Target" keyvalue can be used only to specify teleportation destination. That means this trigger can't act like touch detectors (to fire it's target when touched).

== Changes ==

5.0 Steam Release: Transposed 'Ignore Delays' and 'Start Inactive' flags into keyvalues. Added 'Teleport if Blocked' keyvalue.5.06: Now uses 'InventoryRules' base class.

{{entity_title}}

[[Category:Entities]]
[[Category:Brush entities]]

Player weaponstrip

2023-01-07T12:50:50Z

Tunac: Spawnflag for removing HEV is 1

{{Entity_Infobox
| title=
}}

Removes all weapons and ammo from player. It's possible to also remove HEV suit.Keyvalues

{{Entity_keyvalue|Players to strip|m_iAffected|Allows to change which players will be affected by player_weaponstrip.}}

== Flags ==

{{Entity_flag|1|Strip suit, too|(Also) remove HEV suit.}}

{{entity_title}}

[[Category:Entities]]
[[Category:Point entities]]

Info node air

2023-01-07T12:22:11Z

Tunac: Info about swimming NPCs added, linked to nodes tutorial

{{Entity_Infobox
| title=
}}

Equivalent to [[info_node]] for flying & swimming monsters, like monster_alien_controller, monster_stukabat, and monster_ichthyosaur.

An in-depth tutorial on [[Mapping/All_about_info_nodes|how to use nodes]] is available in the [[Mapping]] section of the wiki.

== Keyvalues ==

{{Entity_keyvalue|Activity|hinttype|Currently non-functional.}}
{{Entity_keyvalue|Hint type|activity|Currently non-functional.}}

== Changes ==

5.0 Steam Release: Added 'Activity' and 'Hint Type' keyvalues.

{{entity_title}}

[[Category:Entities]]
[[Category:Point entities]]

Info node

2023-01-07T12:14:00Z

Tunac: Added link to nodes tutorial and paragraphed the wall of text

{{Entity_Infobox
| title=
}}

Nodes are required in order for monsters to navigate around the map properly.

It is advised to have nodes' origins hover slightly over the ground by 1 to 4 units, in order to prevent nodes from being ignored in nodegraph calculation due to them falsely being identified as being stuck in the floor. The nodegraph is created about 3 seconds after a map has loaded, if the current nodegraph appears to be outdated (Map's 'Create date' later than nodegraph's) or does not exist. The nodegraph-file is located in 'maps/graphs/mapname.nod'. The *.nrp-file which is also produced is a log file containing rather difficult-to-use information. There is no distance limitation for two nodes to connect. Try to place them in as little quantity as possible and as great quantity as required.

Nodes are also used when a monster is ordered to move somewhere by a scripted_sequence, unless the monster is set to not use them. Without nodes, monsters can only walk to their target if it is in direct line of sight with no obstacles blocking the path.

The nodegraph will never change in the middle of play. If a path between two nodes is being blocked sometime after nodegraph-generation, monsters will understand this. However, if a path is blocked while the nodegraph is being calculated, and opened afterwards, monsters won't grasp this. This can happen when you have a door that starts closed. To fix this, you will have to make the door start open and close it about 5 seconds after the map has loaded, when the nodegraph is generated, using a [[trigger_auto]].

An in-depth tutorial on [[Mapping/All_about_info_nodes|how to use nodes]] is available in the [[Mapping]] section of the wiki.

== Keyvalues ==

{{Entity_keyvalue|Activity|hinttype|Currently non-functional.}}
{{Entity_keyvalue|Hint type|activity|Currently non-functional.}}

== Changes ==

5.0 Steam Release: Added 'Activity' and 'Hint Type' keyvalues.

{{entity_title}}

[[Category:Entities]]
[[Category:Point entities]]

Game text

2023-01-07T11:46:54Z

Tunac: Put resolution and position in a table for increased readability

{{Entity_Infobox
| title=
}}

An entity to display HUD messages to the player who activated it, or all players.

== Keyvalues ==

{{Entity_keyvalue|Message text|message|The message to send. Can have a maximum of 490 chars. However, Valve Hammer Editor will truncate the string to 128 if longer than that and crash if the keyvalue is displayed while having more than 127 chars. If you need a message that long, it is adviced to manually assemble it once using a few trigger_changevalue entities. Using '\n', you can get into the next line.}}
{{Entity_keyvalue|X|x|Horizontal positioning. 0.0 to 1.0. 0.0 means left. 1.0 means right. More accurately, this defines the horizontal offset of where every line of the message starts. A value of 1.0 would literally shove the message off of the right side of the screen. '-1' centers every line depending on its length.}}
{{Entity_keyvalue|Y|y|Vertical positioning. 0.0 to 1.0. 0.0 means top. 1.0 means bottom. '-1' centers the whole message as one, if it has multiple lines. It is adviced to not center this, as it obscures the players view too much and looks shabby when drawn over the crosshair. Try values like 0.4 or 0.6 instead. Note that depending on the resolution, too high/low values may end up out of screen. Try to stay between 0.2 and 0.8. In case you ever wondered how big of an y-value equals exactly one line break, here is a list showing that in dependence on the player's resolution:}}

{| class="wikitable sortable"
|-
! Resolution !! Position
|-
|1600 x 1200||0.016666
|-
|1280 x 960||0.020800
|-
|1280 x 1024||0.019550
|-
|1152 x 864||0.023150
|-
|1024 x 768||0.026000
|-
|800 x 600||0.033333
|-
|720 x 576||0.034700
|-
|640 x 480||0.041600
|-
|960 x 600||0.033333
|-
|1088 x 612||0.032700
|-
|1280 x 720||0.027800
|-
|1280 x 800||0.025000
|-
|1600 x 900||0.022222
|}

{{Entity_keyvalue|Text effect|effect|Specify a text effect. 'Fade in/out' has a time-value to fade in, to stay on screen and to fade out. 'Credits' is the same as 'Fade in/out', except that it causes the message to flicker. 'Scan out' has a time-value for per-char color transition and fade-in time per char.}}
{{Entity_keyvalue|Color 1 (Add 4th number >0 for opaque)|color|Color with which the text is rendered. Note that HUD messages are rendered additive. If you want your text to appear darker, make the color darker. You can add optional 4th parameter for opaque.}}
{{Entity_keyvalue|Color 2 (Add 4th number >0 for opaque)|color2|Another color with which the text is rendered. It comes to use with 'Credits'- and 'Scan out'-effect only. Note that HUD messages are rendered additive. If you want your text to appear darker, make the color darker. You can add optional

4th parameter for opaque.}}
{{Entity_keyvalue|Fade in time (or character scan time)|fadein|If the effect is 'Fade in/out' or 'Credits', this specifies the fade-in time. If the effect is set to 'Scan out', this sets the time that is taken for every single char to change its color from 'Color 2' to 'Color 1'. Fade-in time should be short.}}
{{Entity_keyvalue|Fade out time|fadeout|If the effect is 'Fade in/out' or 'Credits', this specifies the fade-out time. If the effect is set to 'Scan out', this has no effect. Fade-out time should be longer than fade-in time, so the player notices that the message is going to disappear and can react by trying to read faster.}}
{{Entity_keyvalue|Hold time|holdtime|Time the message stays on screen after fading in, before it will being to fade out. For effect 'Scan out', this delay will start after all chars have faded in.}}
{{Entity_keyvalue|Scan time|fxtime|For effect 'Scan out', this defines the time required for a character to fade in to 'Color 2'. The next char will only start fading in as the previous one finishes. Small values like 0.01 to 0.1 seconds make sense here.}}
{{Entity_keyvalue|Text channel|channel|Select one of four channels to use. If a message already exists in one channel, it will be replaced.}}

== Flags ==

{{Entity_flag|1|All players|If set, the game_text's message will be displayed to all players instead of just the activator.}}
{{Entity_flag|2|No console echo|If set, players will not receive a duplicate of the message in their console. Set this for messages that can be reread or are sent often to prevent console-spam and reduce network-bandwidth-usage.}}

== Notes ==

The game_text's target will be fired when the game_text entity is triggered. This is very useful when you want to use a single notification sound consistently on all your game_text entities.
Sven Co-op features a HUD monster-/player-info, which uses HUD message channel 3. Avoid using that channel for important messages. Even if you disable monster-info by setting the CVar 'mp_allowmonsterinfo' to '0', player-info will still display on that channel.

== Issues ==

If a text message is replaced by another one because it is set to use the same channel, the time-values won't be updated, causing the new message to expire earlier than desired. Furthermore, only one text message can exist at a specific screen coordinate at a time, even if two different channels are provided.
If one line of the message is too long to fit on a player's screen, it will crash the game.

== Changes ==

5.0 Steam Release: Colour can now have opacity parameter specified.

{{entity_title}}

[[Category:Entities]]
[[Category:Point entities]]

Custom precache

2023-01-07T10:56:34Z

Tunac: Added info about sky map precaching

{{Entity_Infobox
| title=
}}

Allows you to set 9 custom models, 9 custom sounds, and 9 custom skyboxes to be precached. Note that model and sound replacements done through model and/or sound replacement file are already precached automatically. In case 9 of either sort do not suffice for your case, create another custom_precache entity. Model path starts in Sven Co-op's directory.

* You should put your models into the 'models'-folder.
* Sound path starts in the 'sound'-folder.
* Skyboxes are placed in the 'gfx/env/' directory.
Creating subfolders by your map's name for models & sound is advised.

{{entity_title}}

[[Category:Entities]]
[[Category:Point entities]]

Ambient music

2023-01-06T22:51:44Z

Tunac: Created page with "{{Entity_Infobox | title= }} This entity is used to play music within a level. The difference from Ambient Generic is the volume being controlled via the..."

{{Entity_Infobox
| title=
}}

This entity is used to play music within a level. The difference from [[ambient_generic|Ambient Generic]] is the volume being controlled via the CVar 'mp3volume' instead of 'volume'.

== Keyvalues ==

{{Entity_keyvalue|Sound File|message|Name of the sound file to play. File Path starts in the 'sound'-folder, example: 'mymap/musicfile.ogg'.}}
{{Entity_keyvalue|Volume|volume|Set how loud the sound shall be in a range from 0 (not audible) to 10 (normal), but ultimately controlled by the player from the options menu.}}

== Flags ==

{{Entity_flag|1|Start Silent|Music starts once the entity is triggered.}}
{{Entity_flag|2|Loop|Replays the music until toggled off.}}
{{Entity_flag|4|Activator Only}}

{{entity_title}}

[[Category:Entities]]
[[Category:Point entities]]

Svencraft

2023-01-06T18:33:41Z

Tunac: Fix broken link

Svencraft is the Map Editor for Sven Co-op. It closely resembles Valve Hammer Editor in design and use but comes with additional features.

If you want to use Svencraft, please refer to the guide on [[Mapping/Setting up the SDK|Setting up the SDK]].

[[Category:Game]]

Mapping/All about info nodes

2023-01-06T18:10:35Z

Tunac: Tiny edit to force-reload the new images

This guide teaches you all about the usage of info_nodes. There is actually a bit more to it than just tossing a few of them into your map, so here we go:

==What is a node?==
A node is a nagivation point used by the AI to help them move around in your map. You might have seen the message "''Rebuilding Node Graph''" when loading up a new map. At this stage the engine is creating a network of lines between all nodes, so monsters and NPCs know where valid paths are from one node to another.

==Nodes and AI==
Even without the nodes, the AI in the Goldsrc engine knows how to walk through 3D space and navigate around small objects. The AI has been improved in Sven Co-op over the years and is even better at navigating on its own. However, it still relies on nodes to find its way through more complicated scenarios and execute its AI behaviour.

This first example scenario puts the Zombie behind the counter. It will want to walk towards the player but it will fail since it can't determine a clear path. The AI might be smart enough to navigate past smaller objects but this large counter is too much for it to handle.

[[File:NmcnQdj.png|400px]]

Let's add some info_nodes (yellow squares). These points will generate a network of paths for the Zombie to take. As soon as it spots the player and it can't directly engage him, it will look to the node network for guidance and determine the fastest path from its current node to the node the player is currently closest to (indicated by the red line).

[[File:Tc1vzny.png|400px]]

Another example of the usage of nodes is to help the AI execute its special behaviour. The AI code of this Grunt for instance, tells it to find cover when it is taking damage. It will look to the node network to find this spot, so I've placed a strategic node behind the sandbag.

[[File:Zyqp87F.png|400px]]

==Node Networks==
As we've established, nodes are important for the AI to function properly. But how is the network built? The engine will determine if there is a straight visual line between two nodes and if there is, a link is made. I've placed four nodes in this room, and the links will look like this:

[[File:VV1RNjq.png|400px]]

You can actualy see these links in game. Walk to a spot where you know a node is at and type '''impulse 199''' into the console. This will show you all links for this node for a limited amount of time. Mind that it will only show this information for nodes you are close enough to, it will not show you the network for the entire map.

[[File:NSCSirg.jpg|400px]]

A single node can hold very many link to the rest of the network. As long as there is a possible line of sight, there shall be another link.

[[File:Wu17QvH.png|400px]]

The visibility between the nodes can be blocked by solid world geometry and also by func_walls, '''as long as the wall is higher than 32 units.'''

[[File:KhV5Z2u.png|400px]]

The point where the node will be created will always float at 32 units above ground level, so if a wall is 32 units or lower there will be a link. The engine will also create links through non-solid brushes no matter how high they are.

[[File:KsdYcxT.png|400px]]

==Four different types==
Now we know how the network is built, we can expand on this knowledge by introducing the different types of monsters. There are four types:
*Small sized (Headcrab, Chumtoad, etc)
*Normal sized (Zombie, Grunt, etc)
*Large sized (Gargantua, Bullsquid, etc)
*Flying (Alien Controller, Stukabat, etc)

When the node network is built, it will also determine if a certain monster type can actually use the paths. A passage might be too small for a Large sized creature, so it will not establish a usable link between the nodes. You can highlight the different types by use of the other impulse commands. Small creatures will use the default path visible with ''impulse 199'', ''impulse 197'' will show you the paths for Normal sized creatures, ''impulse 196'' for Large sized Creatures and ''impulse 195'' for all airborne creatures (more on them later!).

In the following example you can see how the node network for Normal sized creatures (highlighted as a pink beam) doesn't extend under the low beam, because the brush blocks the way. Small sized creatures would however be able to crawl under it and use the default node link to find their way.

[[File:4eJNF4S.jpg|400px]]

==How to properly place info_nodes==
Now that we know how the node network works, we can move on to placing our nodes. What are good practises to get the most out of our nodes?

When the map starts, all info_node entities will fall to ground level, so it does not matter how high above the ground you place them. Node points will always be created 32 units above the ground where you place your info_node entity. Just make sure that the origin on the info_node is not inside the floor because this might cause the engine to overlook them.

[[File:CQZrkhs.png|400px]]

So where to place your nodes? We've seen that AI can get into trouble whenever there is an obstacle or no clear line between it and the player. So it's good to add a few nodes to help them navigate around (green). You can see those nodes at the door and around the counter. Next to that it's good to place a few 'anchor points' (blue) in the room. This will give the AI a starting point to navigate from and it can serve as a spot for special AI behaviour (such as the Grunt running for cover earlier).

[[File:WlKqghy.png|400px]]

Some guides might tell you to place an info_node every X units. This is not strictly necessary. The engine also doesn't require it. You can place two nodes at a distance of 9000 units from eachother and they will still create a link, as long as they have a line of sight to eachother. You just have to place enough nodes for the AI to have enough anchor points. If you do not have enough, you might encounter undesirable AI behaviour. For instance, if the node a Grunt is falling back to is too far away, it will not resume its normal behavior for a long time. If the node is closer, it will then decide on a new course of action once it has reached the node.

As mentioned before, nodes will only create a link where there is a visual line of sight between two nodes. Luckily, it ignores movable brush entities, such as func_doors, so you can place this door in between the nodes and there still will be a link.

[[File:GKabYUx.png|400px]]

The nodes will link through most brush entities that are movable, such as func_train, func_rotating, func_button, but also func_breakables. Next to that it will go through all non-solid entities such as func_illusionary and everything that uses zhlt_noclip 1.

==info_node_air==
Airborne monsters use a special type of node called the info_node_air. Just as regular info_nodes, these are used for navigation and AI behaviour. However, you might find that airborne monsters are not as good as finding their way to the player as land creatures, since they also have to navigate in upward and downward directions. Info_node_air will not drop down to ground level and info_node_air and info_node will not create links to eachother.

Especially the Alien Controller will hardly move on its own without the help of air nodes. To make sure it will float down or up to engage players on their level, you'll need enough air nodes on that same level. Without these, the Alien Controller will just hover there, not knowing how to get to the player under the ledge. So when you use these monsters, it's good to place extra nodes.

[[File:BoVrm08.png|400px]]

Other flying creatures that use the air nodes are the Stukabat and the Flyer Flock but also swimming creatures make use of them, such as the Leech and the Ichthyosaur. So make sure you place enough info_node_air entities in the waters that house them.

[[File:AHxgxAw.png|400px]]

The Apache and the Osprey technically also use the air nodes network for navigation, however, the Osprey will only function with path_corners to guide it (the game crashes without). The Apache will use air nodes to find its way to the player but isn't very good at it and will just wierdly wobble after the player. Setting up a network of path_corners for the Apache will make it behave far more realisticly and it will then require no air nodes for its navigation.

==Less is more==
As we've established, you just need enough nodes for the monsters to find their way around. But often maps are littered with nodes that serve hardly any function at all. The example below shows you the route (red line) the Grunt has to take to find its way to the player. It only needs those four nodes to get there, so each node in between is just an extra unnecessary step. So if we remove all of those and leave a few nodes as anchor points for navigation and AI behaviour, we can do with almost a third of the nodes we started with.

[[File:UBuzlT1.png|400px]]

Having less nodes is good in multiple ways. First, it uses up less entity slots (which are limited). Secondly, it makes the node graph calculation faster and finally, it makes the node network far less complex. This can benefit the performance of your map, since each monster has to do route calculations. For only a handfull of monsters this will not be a problem but imagine a large map with many active roaming enemies accessing the node network constantly.

==Misc. info==
In Sven Co-op, the info_node entity also has an Activity and Hint type keyvalue. These currently have no function. Judging from the source code, Valve planned to put extra information into nodes, so the AI could use them for specific purposes. Imagine a node that suggests to a Grunt that this is a place to find cover. These hint nodes actually ended up being used in Half-Life 2. In HL1 the code for hint nodes is only found for the Houndeye, where it can investigate buzzing machinery and blinking lights.

[[Category:Mapping]]
[[Category:Tutorials]]

Func breakable

2023-01-06T15:43:05Z

Tunac: Added info about instant break weapons

{{Entity_Infobox
| title=
| type=b
}}

A brush entity, which receives damage from all normal damage sources, such as weapon fire, and can, eventually, break from it, spilling some debris/gibs in its place.

== Keyvalues ==

{{Entity_keyvalue|Classification|classify|Classification of this entity. If specified, enemies of this class will attack this entity.}}
{{Entity_keyvalue|Strength|health|Set how many hitpoints the func_breakable has.}}
{{Entity_keyvalue|Material type|material|Choose the material which matches what your func_breakable is supposed to be the most. The material type affects the func_breakable's sounds emitted when it takes damage, as well as which gibs are created when it is destroyed. If the material is set to 'Unbreakable glass', the func_breakable is, regardless of how funny that is, in fact, unbreakable.}}
{{Entity_keyvalue|Instant break weapon|weapon|Allows you to specify an instant-break weapon other than the crowbar. Requires "Instant Break" flag to work.

* '''Crowbar''' is the default option and will work with both the crowbar and electric crowbar. Will not work with a thrown crowbar.
* '''Crowbar (Electric Only)''' requires the electric-mode of the crowbar. Will not work with a thrown crowbar.
* '''Pipe Wrench'''}}
{{Entity_keyvalue|Gibs direction and velocity|explosion|Set whether the gibs fly relative to where the attack came from, damage received and material (e.g. concrete gibs fly with less velocity) or randomly. This has no effect on func_breakables destroyed via a trigger. Note: Blowing up stuff is much more fun when shit goes flying instead of just falling to the ground as if nothing happened.}}
{{Entity_keyvalue|Delay before fire|delay|Delay between the func_breakable breaking and it actually firing its target. If the 'Touch'-flag is set, the func_breakable will break in the same moment in which it fires its target.}}
{{Entity_keyvalue|Gib model|gibmodel|Custom model of broken entity parts. Models with multiple 'Submodels' uses all of sub-models for gibs.}}
{{Entity_keyvalue|Spawn on break|spawnobject|If the func_breakable is broken, the specified item will drop. It does not respawn after collected.}}
{{Entity_keyvalue|Explode magnitude <nowiki>(0=none)</nowiki>|explodemagnitude|If greater than zero, the func_breakable will cause an explosion at its position when it breaks. The greater the magnitude, the more damage the explosion will cause. Note that explosion damage values above 200 are know to cause explosion damage to even go through walls.}}
{{Entity_keyvalue|Sound replacement file|soundlist|Allows you to setup a sound replacement file for the func_breakables sounds. The path begins in 'svencoop/sound/mapname', whereas 'mapname' would be your map's name. You can go to the parent directory using '../'. A valid sound replacement file contains one or more lines with two sound-paths, which are separated by a space and wrapped into quotes. The first sound is the sound to be replaced. The second sound is the new sound. Sound-paths start in the sound directory. You cannot go to the parent directory using '../' in that case. These sounds do not need to be precached using a custom_precache point entity.}}
{{Entity_keyvalue|Show HUD info|showhudinfo|If set to 'Yes', the HUD information (name, health etc.) are shown.}}

== Flags ==

{{Entity_flag|1|Only trigger|If set, this func_breakable will only break when triggered, even if its health value is set to '1'.}}
{{Entity_flag|2|Touch|If set, this func_breakable will break as soon as a player touches it. If a delay before fire is set, the func_breakable will wait for that to run out before breaking after a touch.}}
{{Entity_flag|4|Pressure|If set, the func_breakable can be destroyed from pressure, as is e.g. inflicted by a func_train, regardless of the train's damage.}}
{{Entity_flag|8|Repairable|If set, this func_breakable can be repaired, as in, have its health restored, by a player 'attacking' it with weapon_pipewrenches' primary attack, for the amount of that weapon's primary damage value.}}
{{Entity_flag|32|Show HUD info|If set, the func_breakable will show HUD info for players looking at it. This is not affected by CVar 'mp_allowmonsterinfo'.}}
{{Entity_flag|64|Immune to Client|If set, the func_breakable will be immune to player attacks.}}
{{Entity_flag|256|Instant Break|If set, this func_breakable will break instantly if hit with a crowbar.}}
{{Entity_flag|512|Explosives only|If set, this func_breakable can be damaged by explosives only.}}

== Changes ==

* 5.0 Steam Release: Renamed 'Target on Break' keyvalue to 'Target' (removed from this subpage, it's not unique anymore).

{{entity_title}}

[[Category:Entities]]
[[Category:Brush entities]]

Func pushable

2023-01-06T15:37:52Z

Tunac: Added info about instant break weapons

{{Entity_Infobox
| title=
| type=b
}}

Similar to [[func_breakable]], but this entity can also be pushed and carried by players.

== Keyvalues ==

{{Entity_keyvalue|Classification|classify|Classification of this entity. If specified, enemies of this class will attack this entity.}}
{{Entity_keyvalue|Target on break|target|The func_breakable triggers its target when it breaks.}}
{{Entity_keyvalue|Strength|health|Set how many hitpoints the func_breakable has.}}
{{Entity_keyvalue|Material type|material|Choose the material which matches what your func_breakable is supposed to be the most. The material type affects the func_breakable's sounds emitted when it takes damage, as well as which gibs are created when it is destroyed. If the material is set to 'Unbreakable glass', the func_breakable is, regardless of how funny that is, in fact, unbreakable.}}
{{Entity_keyvalue|Instant break weapon|weapon|Allows you to specify an instant-break weapon other than the crowbar. Requires the "1-Hit Break" flag to work.

* '''Crowbar''' is the default option and will work with both the crowbar and electric crowbar. Will not work with a thrown crowbar.
* '''Crowbar (Electric Only)''' requires the electric-mode of the crowbar. Will not work with a thrown crowbar.
* '''Pipe Wrench'''}}
{{Entity_keyvalue|Gibs direction and velocity|explosion|Set whether the gibs fly relative to where the attack came from, damage received and material (e.g. concrete gibs fly with less velocity) or randomly. This has no effect on func_breakables destroyed via a trigger. Note: Blowing up stuff is much more fun when shit goes flying instead of just falling to the ground as if nothing happened.}}
{{Entity_keyvalue|Delay before fire|delay|Delay between the func_breakable breaking and it actually firing its target. If the 'Touch'-flag is set, the func_breakable will break in the same moment in which it fires its target.}}
{{Entity_keyvalue|Gib model|gibmodel|Custom model of broken entity parts. Models with multiple 'Submodels' uses all of sub-models for gibs.}}
{{Entity_keyvalue|Spawn on break|spawnobject|If the func_breakable is broken, the specified item will drop. It does not respawn after collected.}}
{{Entity_keyvalue|Explode magnitude <nowiki>(0=none)</nowiki>|explodemagnitude|If greater than zero, the func_breakable will cause an explosion at its position when it breaks. The greater the magnitude, the more damage the explosion will cause. Note that explosion damage values above 200 are know to cause explosion damage to even go through walls.}}
{{Entity_keyvalue|Sound replacement file|soundlist|Allows you to setup a sound replacement file for the func_breakables sounds. The path begins in 'svencoop/sound/mapname', whereas 'mapname' would be your map's name. You can go to the parent directory using '../'. A valid sound replacement file contains one or more lines with two sound-paths, which are separated by a space and wrapped into quotes. The first sound is the sound to be replaced. The second sound is the new sound. Sound-paths start in the sound directory. You cannot go to the parent directory using '../' in that case. These sounds do not need to be precached using a custom_precache point entity.}}
{{Entity_keyvalue|Friction (0-400)|friction|Friction of func_pushable, higher values makes it harder to move. Set it to 400 or values near to 400 to make it unmovable by pushing it (still func_pushable can be easily moved by using it and pressing left/right).}}
{{Entity_keyvalue|Buoyancy|buoyancy|How well this entity will float in liquid.}}
{{Entity_keyvalue|Max Hull size|maxhullsize|Obsolete.}}
{{Entity_keyvalue|Min Hull size|minhullsize|Obsolete.}}
{{Entity_keyvalue|HUD Info name|displayname|Name you will see on the in-game HUD when looking at this entity. Requires "Show HUD Info" flag.}}

== Flags ==

{{Entity_flag|8|Repairable|Players can repair this entity with the wrench.}}
{{Entity_flag|16|Monsters Ignore?|Monsters will ignore this entity.}}
{{Entity_flag|32|Show HUD Info|Whether or not to show the name and health of this entity when looking at it in-game.}}
{{Entity_flag|128|Breakable|Can be broken.}}
{{Entity_flag|256|1-Hit Break|Can be broken in one hit by the weapon set in "Instant Break Weapon".}}
{{Entity_flag|512|Explosives Only|Can only be broken with explosives.}}
{{Entity_flag|1024|Liftable|Players can lift this entity off of the ground. It's recommended to not using this feature, it's heavily bugged.}}

== Issues ==

* Liftable pushables shake when being held (and fly away when let go of).
* Stacking liftable pushables on each other breaks them, making them fly infinitely up when attempting to be lifted again.
* Pushables tend to get stuck in or go through complex geometry. Try to keep the area around this entity as square as possible.
* Hull Size key is obsolete.

{{entity_title}}

[[Category:Entities]]
[[Category:Brush entities]]

Func platrot

2023-01-06T14:38:34Z

Tunac: Language tweaks

{{Entity_Infobox
| title=
| type=b
}}

Same as [[func_plat]], but it also rotates with customizable rotation speed. Vertically moving elevator that moves up automatically when a player steps on it. It's also automatically called when player wait for it at the top of the whole travel altitude. This entity requires an origin brush tied to it.

== Keyvalues ==

{{Entity_keyvalue|Move Sound|movesnd|Sound that is played while the platform is moving.}}
{{Entity_keyvalue|Move Sound Loops?|movesnd_loop|Sets if Move Sound should be looped during brush movement until it stops.}}
{{Entity_keyvalue|Stop Sound|stopsnd|Sound which is played once as the train stops moving.}}
{{Entity_keyvalue|Sound Volume|volume|Self-explanatory.}}
{{Entity_keyvalue|Sound Replacement File|soundlist|Allows you to setup a sound replacement file for the func_plat sounds. The path begins in 'svencoop/sound/mapname', whereas 'mapname' would be your map's name. You can go to the parent directory using '../'. A valid sound replacement file contains one or more lines with two sound-paths, which are separated by a space and wrapped into quotes. The first sound is the sound to be replaced. The second sound is the new sound. Sound-paths start in the sound directory. You cannot go to the parent directory using '../' in that case. These sounds do not need to be precached using a custom_precache point entity.}}
{{Entity_keyvalue|Fire On Open Start|fireonopening|Entity to trigger when platform starts opening.}}
{{Entity_keyvalue|Fire On Open Start Trigger State|fireonopening_triggerstate|Set the use-type with which the entity specified above will be fired.}}
{{Entity_keyvalue|Fire On Close Start|fireonclosing|Entity to trigger when platform starts closing.}}
{{Entity_keyvalue|Fire On Close Start Trigger State|fireonclosing_triggerstate|Set the use-type with which the entity specified above will be fired.}}
{{Entity_keyvalue|Fire On Open End|fireonopened|Entity to trigger when platform ends opening.}}
{{Entity_keyvalue|Fire On Open End Trigger State|fireonopened_triggerstate|Set the use-type with which the entity specified above will be fired.}}
{{Entity_keyvalue|Fire On Close End|fireonclosed|Entity to trigger when platform end closing.}}
{{Entity_keyvalue|Fire On Close End Trigger State|fireoncloed_triggerstate|Set the use-type with which the entity specified above will be fired.}}
{{Entity_keyvalue|Damage inflicted when blocked|dmg|Damage to deal when entity is blocked.}}
{{Entity_keyvalue|Speed of rotation|speed|Movement-speed in units per second.}}
{{Entity_keyvalue|Travel altitude|height|How many units func_plat travels up to the top. It CAN'T be negative, the FGD lies!}}
{{Entity_keyvalue|Spin amount|rotation|Total amount of degrees this entity spins from it's starting to ending position.}}
{{Entity_keyvalue|Move Sound Override|noise|Custom sound file that is playing when entity is moving. Overrides default "Move Sound" sound.}}
{{Entity_keyvalue|Stop Sound Override|noise1|Custom sound file to play when the entity ends movement. Overrides default "Stop Sound" sound.}}

== Flags ==

{{Entity_flag|1|Toggle|If selected, the lift is no more automatically called from top and activated by stepping on it. It required trigger to do so.}}
{{Entity_flag|64|X Axis|Enable this to make platform rotate around x axis instead of z axis.}}
{{Entity_flag|128|Y Axis|Enable this to make platform rotate around y axis instead of z axis.}}

== Changes ==

* 5.0 Steam Release: Added 'Damage inflicted when blocked', 'Move Sound Override' and 'Stop Sound Override' keyvalues.

{{entity_title}}

[[Category:Entities]]
[[Category:Brush entities]]

Func plat

2023-01-06T14:34:58Z

Tunac: Language tweaks

{{Entity_Infobox
| title=
| type=b
}}

Vertically moving elevator that moves up automatically when a player steps on it. It's also automatically called when player waits for it at the top of the whole travel altitude.

== Keyvalues ==

{{Entity_keyvalue|Move Sound|movesnd|Sound that is played while platform is moving.}}
{{Entity_keyvalue|Move Sound Loops?|movesnd_loop|Sets if Move Sound should be looped during brush movement until it stops.}}
{{Entity_keyvalue|Stop Sound|stopsnd|Sound which is played once as the train stops moving.}}
{{Entity_keyvalue|Sound Volume|volume|Self-explanatory.}}
{{Entity_keyvalue|Sound Replacement File|soundlist|Allows you to setup a sound replacement file for the func_plat sounds. The path begins in 'svencoop/sound/mapname', whereas 'mapname' would be your map's name. You can go to the parent directory using '../'. A valid sound replacement file contains one or more lines with two sound-paths, which are separated by a space and wrapped into quotes. The first sound is the sound to be replaced. The second sound is the new sound. Sound-paths start in the sound directory. You cannot go to the parent directory using '../' in that case. These sounds do not need to be precached using a custom_precache point entity.}}
{{Entity_keyvalue|Fire On Open Start|fireonopening|Entity to trigger when platform starts opening.}}
{{Entity_keyvalue|Fire On Open Start Trigger State|fireonopening_triggerstate|Set the use-type with which the entity specified above will be fired.}}
{{Entity_keyvalue|Fire On Close Start|fireonclosing|Entity to trigger when platform starts closing.}}
{{Entity_keyvalue|Fire On Close Start Trigger State|fireonclosing_triggerstate|Set the use-type with which the entity specified above will be fired.}}
{{Entity_keyvalue|Fire On Open End|fireonopened|Entity to trigger when platform ends opening.}}
{{Entity_keyvalue|Fire On Open End Trigger State|fireonopened_triggerstate|Set the use-type with which the entity specified above will be fired.}}
{{Entity_keyvalue|Fire On Close End|fireonclosed|Entity to trigger when platform end closing.}}
{{Entity_keyvalue|Fire On Close End Trigger State|fireoncloed_triggerstate|Set the use-type with which the entity specified above will be fired.}}
{{Entity_keyvalue|Damage inflicted when blocked|dmg|Damage to deal when entity is blocked.}}
{{Entity_keyvalue|Travel altitude|height|How many units func_plat travels up to the top. It can be set to negative only if "toggle" flag is selected.}}
{{Entity_keyvalue|Speed|speed|Movement-speed in units per second.}}
{{Entity_keyvalue|Move Sound Override|noise|Custom sound file that is playing when entity is moving. Overrides default "Move Sound" sound.}}
{{Entity_keyvalue|Stop Sound Override|noise1|Custom sound file to play when the entity ends movement. Overrides default "Stop Sound" sound.}}

== Flags ==

{{Entity_flag|1|Toggle|If selected, the lift is not automatically called from top and activated by stepping on it. It requires a trigger to do so.}}

== Changes ==

* 5.0 Steam Release: Added 'Inventory Rules', 'Damage inflicted when blocked', 'Move Sound Override' and 'Stop Sound Override' keyvalues.

{{entity_title}}

[[Category:Entities]]
[[Category:Brush entities]]

Func mortar field

2023-01-06T14:24:10Z

Tunac: Spelling & language fixes

{{Entity_Infobox
| title=
| type=b
}}

This entity serves as a spawnzone for mortars, which cause a sound effect, shortly followed by an explosion on the ground straight below where they were spawned. This entity can be hooked up to [[momentary_rot_button|momentary_rot_buttons]] or [[func_rot_button|func_rot_buttons]] to do aimed mortar strikes.

== Keyvalues ==

{{Entity_keyvalue|Spread Radius|m_flSpread|Mortars spreading radius, bombs will spawn randomly within specified radius.}}
{{Entity_keyvalue|Repeat Count|m_iCount|Amount of mortars to spawn each airstrike call.}}
{{Entity_keyvalue|Targeting|m_fControl|Controls area of airstrike with the following options.

* '''Random''' makes mortars spawn randomly within the volume of func_mortar_field.

* '''Activator''' option simply force mortars to strike at '!activator' (activator of the script) e.g. when player pushed a button which fires func_mortar_field, and the 'Activator' option is selected, the mortars spawns above the player. Note that bombs will be called at '!activator' location during the moment of firing func_mortar_field, which means the '!activator' has time to escape from within the airstrike area. Another thing about 'Activator' option is that '!activator' location is not important- the bombs will strike '!activator' even if it's outside the volume of the func_mortar_field- the location, placement and size of this entity does not matter.

* '''Table''' variant can be seen in Half Life single player campaign- Gordon controls the airstrike area by two momentary button, first button controls X position of mortarts, and the second button controls its Y position. This option enables "X Controller" and "Y Controller" keyvalues. When func_mortar_field is triggered, the entity picks percentage of X and Y position (from left/top to right/bottom) of func_rot_buttons hooked to it, and converts those to X and Y sizes of this entity volume, e.g. when the left/right momentary button (X Controller) is in the far left side, and the top/bottom momentary button (Y Controlled) is in the center of the whole movement distance, the airstrike will be called at 0% X and 50% Y position of func_mortar_field.}}
{{Entity_keyvalue|X Controller|m_iszXController|The name of momentary_rot_button or func_rot_button to control X coordinates of mortar spawnpoint. Requires 'Table' value in "Targeting" key (see above).}}
{{Entity_keyvalue|Y Controller|m_iszYController|The name of momentary_rot_button or func_rot_button to control Y coordinates of mortar spawnpoint. Requires 'Table' value in "Targeting" key (see above).}}

{{entity_title}}

[[Category:Entities]]
[[Category:Brush entities]]

Func mortar field

2023-01-06T14:16:43Z

Tunac: Changed keyvalues to be clearer

{{Entity_Infobox
| title=
| type=b
}}

This entity serves as a spawnzone for mortars, which cause a sound effect, shortly followed by an explosion on the ground straight below where they were spawned. This entity can be hooked up to [[momentary_rot_button|momentary_rot_buttons]] or [[func_rot_button|func_rot_buttons]] to do aimed mortar strikes.

== Keyvalues ==

{{Entity_keyvalue|Spread Radius|m_flSpread|Mortars spreading radius, bombs will spawn randomly within specified radius.}}
{{Entity_keyvalue|Repeat Count|m_iCount|Amount of mortars to spawn each airstrike call.}}
{{Entity_keyvalue|Targeting|m_fControl|Controls area of airstrike.

* '''Random''' makes mortars spawn randomly within volume of func_mortar_field.

* '''Activator''' option simply force mortars to strike at '!activator' (activator of the script) e.g. when player pushed a button which fires func_mortar_field, and the 'Activator' option is selected, the mortars spawns above the player. Note that bombs will be called at '!activator' location in a moment of firing func_mortar_field, what means the '!activator' have a time to escape from within airstrike area. Another think about 'Activator' option is that '!activator' location is not important- the bombs will strike '!activator' even if it's out of volume of the func_mortar_field- the location, placement and size of this entity does not matter.

* '''Table''' variant can be seen in Half Life single player campaign- Gordon controls the airstrike area by two momentary button, first button controls X position of mortarts, and the second button controls it's Y position. This option enables "X Controller" and "Y Controller" keyvalues. When func_mortar_field is triggered, the entity picks percentage of X and Y position (from left/top to right/bottom) of func_rot_buttons hooked to it, and converts those to X and Y sizes of this entity volume, e.g. when the left/right momentary button (X Controller) is in the far left side, and the top/bottom momentary button (Y Controlled) is in the center of the whole movement distance, the airstrike will be called at 0% X and 50% Y position of func_mortar_field.}}
{{Entity_keyvalue|X Controller|m_iszXController|The name of momentary_rot_button or func_rot_button to control X coordinates of mortar spawnpoint. Requires 'Table' value
in "Targetting" key (see above).}}
{{Entity_keyvalue|Y Controller|m_iszYController|The name of momentary_rot_button or func_rot_button to control Y coordinates of mortar spawnpoint. Requires 'Table' value
in "Targetting" key (see above).}}

{{entity_title}}

[[Category:Entities]]
[[Category:Brush entities]]

Func ladder

2023-01-06T14:01:47Z

Tunac: Added entry for its spawnflag

{{Entity_Infobox
| title=
| type=b
}}

Invisible brush-entity which allows players to climb on its surface on touch. Player won't stop using the ladder unless jumping off or moving away from the ladder's surface sideways. Ladders on ceilings works as well. Sloped ladders produce dissatisfactory results and should not be used. Touching a ladder while falling will nullify the player's velocity and safe him from falling damage. Usually used in combination with a [[func_illusionary]] with ladder-textures for the visual counterpart.

== Flags ==

{{Entity_flag|1|Start Off|If selected, the func_ladder is disabled at map start, which means it needs to be triggered in order to be enabled.}}

{{entity_title}}

[[Category:Entities]]
[[Category:Brush entities]]

Func trackchange

2023-01-06T13:30:30Z

Tunac: Fix broken markup in flags

{{Entity_Infobox
| title=
| type=b
}}

Brush entity that works as a rotating ascending/descending elevator for func_tracktrain.
It connects two path_tracks- elevator takes the train from last path_track of the top path, rotating and descending, and then, after finishing, the train is assigned to path_track of the bottom path.
This can be reverted for ascending platform. The func_trackchange platform need origin brush (preferably located at the center of entity), and the top and the bottom path_corners should be centered to this entity
for best results.

See the picture on the left- the platform with origin brush tied to it (func_trackchange), and orange cubes
that represents the top and the bottom path_track.

Similar variant to this entity is func_trackautochange, however you can't trigger func_trackautochange
in other way than by path_track's "Fire on dead end" value, you would trigger connected train instead.

== Keyvalues ==

{{Entity_keyvalue|Move sound|movesnd|Sound playing when func_trackchange is moving:}}
{{Entity_keyvalue|Move Sound Loops?|movesnd_loop|Sets if Move Sound should be looped during brush movement until it stops.}}
{{Entity_keyvalue|Stop sound|stopsnd|Sound to play when the func_trackchange stop moving.}}
{{Entity_keyvalue|Sound volume|volume|Volume of move and stop sounds.}}
{{Entity_keyvalue|Sound Replacement File|soundlist|Set the path to a sound replacement file for this entity. The path begins in 'svencoop/sound/mapname', whereas 'mapname' would be your map's name. You can go to the parent directory using '../'. A valid sound replacement file contains one or more lines with two sound-paths, which are separated by a space and wrapped into quotes. The first sound is the sound to be replaced. The second sound is the new sound. Sound-paths start in the sound directory. You cannot go to the parent directory using '../' in that case. These sounds do not need to be precached using a custom_precache point entity.}}
{{Entity_keyvalue|Fire On Open Start|fireonopening|Entity to trigger when platform starts opening.}}
{{Entity_keyvalue|Fire On Open Start Trigger State|fireonopening_triggerstate|Set the use-type with which the entity specified above will be fired.}}
{{Entity_keyvalue|Fire On Close Start|fireonclosing|Entity to trigger when platform starts closing.}}
{{Entity_keyvalue|Fire On Close Start Trigger State|fireonclosing_triggerstate|Set the use-type with which the entity specified above will be fired.}}
{{Entity_keyvalue|Fire On Open End|fireonopened|Entity to trigger when platform ends opening.}}
{{Entity_keyvalue|Fire On Open End Trigger State|fireonopened_triggerstate|Set the use-type with which the entity specified above will be fired.}}
{{Entity_keyvalue|Fire On Close End|fireonclosed|Entity to trigger when platform end closing.}}
{{Entity_keyvalue|Fire On Close End Trigger State|fireoncloed_triggerstate|Set the use-type with which the entity specified above will be fired.}}
{{Entity_keyvalue|Damage inflicted when blocked|dmg|Damage to deal when entity is blocked.}}
{{Entity_keyvalue|Travel Altitude|height|Travel distance, from top to bottom. If "Start at Bottom flag is selected, the travel distance won't change from bottom to top,

it only makes platform start at bottom and awaits for func_tracktracin to arrive.}}
{{Entity_keyvalue|Spin amount|rotation|The spin done by this platform on entire way up/down.}}
{{Entity_keyvalue|Train to Switch|train|Name of func_tracktrain this platform will transport to top/bottom track.}}
{{Entity_keyvalue|Top track|toptrack|Name of last path_track of the top path (if "Start at Bottom" is selected this is the name of the first path_track at the top path).}}
{{Entity_keyvalue|Bottom track|bottomtrack|Name of first path_track of the bottom track. (if "Start at Bottom" is selected this is the name of the last path_track

at the bottom path).}}
{{Entity_keyvalue|Move/Rotate Speed|speed|Speed in which func_trackchange travel the whole way up/down (units per seconds).}}
{{Entity_keyvalue|Move Sound Override|noise|Custom sound file that is playing when entity is moving. Overrides default "Move Sound" sound.}}
{{Entity_keyvalue|Stop Sound Override|noise1|Custom sound file to play when the entity ends movement. Overrides default "Stop Sound" sound.}}
{{Entity_keyvalue|Blocked Sound|noise2|Custom sound file to play when train is blocked.}}

== Flags ==

{{Entity_flag|1|Auto Activate train|If selected, train isn't paused at the top/bottom of the path after func_trackchange finish it's movement. Instead, it's continue moving forward.}}
{{Entity_flag|2|Relink track|The functionality of this flag is unknown. However, this entity seems to work fine whenever this flag is selected or not.}}

{{Entity_flag|8|Start at Bottom|Platform starts at the bottom instead at the top path_track if this flag is ticked.}}
{{Entity_flag|16|Rotate Only|If selected, the platform only rotates in place of it's origin without travelling specified altitude.

The top and the bottom path_tracks should have their origin positioned in the same coordinates.}}

{{Entity_flag|64|X Axis|Train rotates around X axis instead of Z axis. Can be combined with "Y Axis".}}
{{Entity_flag|128|Y Axis|Train rotates around Y axis instead of Z axis. Can be combined with "X Axis".}}

== Notes ==

Remember to create origin brush for this entity around which func_trackchange rotates.It is said that func_trackchange works better with controllable func_tracktrain, however it seems to both controllable
and non-controllable func_tracktrains supports both func_trackchange and func_trackautochange.

== Changes ==

5.0 Steam Release: Added 'Damage inflicted when blocked', 'Move Sound Override', 'Stop Sound Override' and 'Blocked Sound' keyvalues.

{{entity_title}}

[[Category:Entities]]
[[Category:Brush entities]]