View source for Env mortar controller

[[File:env_mortar_controller_image.png|350px|right]]
{{CD|???|base=??? CBaseAnimating}}
{{This is a|point entity|name=env_mortar_controller|game=Black Mesa}} This is an airstrike map that allows you to mark and launch bombs at a specified point. For full functionality, this entity must be used in combination with {{ent|env_mortar_launcher}}, {{ent|point_camera}} and {{ent|info_camera_link}}. In the original game it was used once in bm_c2a5i.
{{bug*|In current versions of the game, this entity have no fire delay (the fire button lock doesn't happen). If player will spam the button - this will create a lot of bombs which will cause huge fps drop (due to explosions) and then may cause the game to crash. Not in {{bms12|4}} (the mod version) and early versions of the game.
{{workaround|See workaround below.
}}
}}
{{bug*|This entity doesn't work properly in multiplayer, only 1 player will be able to shoot, the crosshair will not work for others.}}
{{bug*|Never solid.}}

==Keyvalues==
{{KV Targetname}}
{{KV|Mortar Launcher|intn=mortarlauncher|target_destination|{{code|env_mortar_launcher}} to use.}}

== Inputs ==
{{I|attachscreen|param=void|Fires on entity spawn to attach screen.|nofgd=1}}

==Attaching screen==
First, place {{ent|point_camera}} at required position, set orientation and give a name. This entity will display area in airstrike map. You also need to change value for {{code|Render Target}}, set <code>_rt_Satellite</code> value.

<gallery mode=nolines heights=820px widths=820px>
File:attachcam_pic1.jpg|Example.
</gallery>

Now we need {{ent|info_camera_link}}. In {{code|Entity Whose Material Uses _rt_camera}} you need to add name of {{ent|env_mortar_controller}}, in {{code|Camera Name}} add name of {{ent|point_camera}} you placed earlier.

<gallery mode=nolines heights=820px widths=820px>
File:attachcam_pic2.jpg|Example.
</gallery>

Now compile your map and check the result. You now have functional screen. Don't forget to specify {{ent|env_mortar_launcher}} name in {{code|Mortar Launcher}} property.

==Fixing mortar spam==
{{ent|env_mortar_launcher}} can dynamically change values in properties with [[AddOutput]], we'll use this feature to fire 0 shells when fired once. Unfortunately, {{ent|env_mortar_launcher}} and {{ent|env_mortar_controller}} don't have any outputs that fires when shell is launched, we need to use triggers instead.

Create a {{ent|trigger_weaponfire}} in the form of an empty box inside. There should be a free space of 30 [[hammer units]] inside (<code>x, y, z</code>), {{ent|env_mortar_launcher}} should be placed in the center.

<gallery mode=nolines heights=820px widths=820px>
File:fixmortspam_pic1.jpg|Example.
</gallery>

Now create another {{ent|trigger_weaponfire}} that is 12 hammer units in size on all axes. This trigger should be in {{ent|env_mortar_launcher}} center. Give a name for this trigger ({{code|shellkiller}} for example) and for {{code|Start Disabled?}} property set value <code>Yes</code>.

<gallery mode=nolines heights=820px widths=820px>
File:fixmortspam_pic2.jpg|Example.
</gallery>

We need to add outputs now, for the second trigger ({{code|shellkiller}}) make the following output:
{{entity-output-start}}
{{entity-output||OnStartTouch|!activator|Kill||0.00|No|}}
{{entity-output-end}}

For the first trigger, make the following outputs: 
{{entity-output-start}}
{{entity-output||OnStartTouch|shellkiller|Enable||0.00|No|}}
{{entity-output||OnStartTouch|mortar_launcher|AddOutput|fireshellscount 0|0.00|No|{{code|mortar_launcher}} is the name of {{ent|env_mortar_launcher}}.}}
{{entity-output||OnStartTouch|shellkiller|Disable||2.00|No|}}
{{entity-output||OnStartTouch|mortar_launcher|AddOutput|fireshellscount 1|2.00|No|}}
{{entity-output-end}}


Now spam is prevented. The only issue is mortar launch sounds, you can fix this by replacing the sound with a blank sound and playing the original sound via outputs.