Player weaponstrip: Difference between revisions
Jump to navigation
Jump to search
Bug:In 
and 
, the player's weapon will lower and become non-functional, but will not actually disappear.:
Workaround:Fire a DisableDraw input to the [todo tested in ?]
Bug:If player changes the map after their weapons are stripped, the 
). (tested in: 
)
Note:In multiplayer, only the
(its position in the world irrelevant so it's logical entity) |
MyGamepedia (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
{{bug|In {{portal}} and {{portal2}}, the player's weapon will lower and become non-functional, but will not actually disappear.:{{workaround|Fire a DisableDraw input to the <code>viewmodel</code> entity with a slight delay after triggering the weaponstrip. (This does ''not'' prevent later picked up weapons from appearing.)}}}} | {{bug|In {{portal}} and {{portal2}}, the player's weapon will lower and become non-functional, but will not actually disappear.:{{workaround|Fire a DisableDraw input to the <code>viewmodel</code> entity with a slight delay after triggering the weaponstrip. (This does ''not'' prevent later picked up weapons from appearing.)}}}} | ||
{{bug|If player changes the map after their weapons are stripped, the <code>viewmodel</code> of the last held weapon will appear but will be non-functional. This is fixed by picking up a new weapon.}} | {{bug|tested={{hls}}|If player changes the map after their weapons are stripped, the <code>viewmodel</code> of the last held weapon will appear but will be non-functional. This is fixed by picking up a new weapon {{not|{{bms}}}}.}} | ||
{{note|In multiplayer, only the <code>!activator</code> is targeted. This means the input needs to be fired as a result of a player interaction, such as touching a trigger or pressing a button. In games with [[VScript]], <code>EntFireByHandle()</code> can instead be used to fire the input with a specific player as the activator.}} | {{note|In multiplayer, only the <code>!activator</code> is targeted. This means the input needs to be fired as a result of a player interaction, such as touching a trigger or pressing a button. In games with [[VScript]], <code>EntFireByHandle()</code> can instead be used to fire the input with a specific player as the activator.}} | ||
Revision as of 11:24, 17 May 2025
 Class hierarchy
|
|---|
| CStripWeapons |
| player.cpp
|
player_weaponstrip is a logical entity available in all 
Source games.
This entity strips the player of their weapons and/or suit.
Bug:In and , the player's weapon will lower and become non-functional, but will not actually disappear.:Workaround:Fire a DisableDraw input to the viewmodel entity with a slight delay after triggering the weaponstrip. (This does not prevent later picked up weapons from appearing.)Bug:If player changes the map after their weapons are stripped, the viewmodel of the last held weapon will appear but will be non-functional. This is fixed by picking up a new weapon (not in ). (tested in: )Note:In multiplayer, only the !activator is targeted. This means the input needs to be fired as a result of a player interaction, such as touching a trigger or pressing a button. In games with VScript, EntFireByHandle() can instead be used to fire the input with a specific player as the activator.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
Inputs
- Strip
- Strip player's weapons
- StripWeaponsAndSuit
- Strip player's weapons and suit
- StripActiveWeapon (only in
) - Removes the active weapon.
- StripWeaponByClassname (only in )
- Removes a weapon by classname, eg 'weapon_gascan'
See also
- trigger_weapon_strip - Similiar brush entity.