MapBase/source-sdk-2013-mapbase
1
0
Fork 0
mirror of https://github.com/mapbase-source/source-sdk-2013.git synced 2024-12-26 14:55:30 +03:00
Code Issues Packages Projects Releases Wiki Activity

Filled in some I/O/KV

Blixibon 2019-05-05 11:50:08 -05:00
parent 804a48006b
commit 6cff206a52
2 changed files with 25 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
Articles/Base Entity.md

@ -1 +0,0 @@
Mapbase makes several changes to the base entity class that every single entity in the Source engine derives from. This means every entity in the FGD possesses these changes.

25
Base-Entity.md Normal file

@ -0,0 +1,25 @@
Mapbase makes several changes to the base entity class that every single entity in the Source engine derives from. This means every entity in the FGD possesses these changes.
### Inputs
---
New User I/O that could pass parameters:
* **PassUser1** `<any>` - Fires OutUser1 with the any parameter.
* **PassUser2** `<any>` - Fires OutUser2 with the any parameter.
* **PassUser3** `<any>` - Fires OutUser3 with the any parameter.
* **PassUser4** `<any>` - Fires OutUser4 with the any parameter.
* **FireRandomUser** `<void>` - Fires OnUser1, OnUser2, OnUser3, or OnUser4 with a 25% chance of each.
* **PassRandomUser** `<any>` - Fires OutUser1, OutUser2, OutUser3, or OutUser4 with a 25% chance of each, passing any parameter.
### Outputs
---
* **OutUser1** `<any>` - Fires in response to the PassUser1 input, outputting any parameter.
* **OutUser2** `<any>` - Fires in response to the PassUser2 input, outputting any parameter.
* **OutUser3** `<any>` - Fires in response to the PassUser3 input, outputting any parameter.
* **OutUser4** `<any>` - Fires in response to the PassUser4 input, outputting any parameter.
---
* **OnKilled** `<void>` - Fires when this entity is removed with the 'Kill' or 'KillHierarchy' input.
### KeyValues
---
No keyvalues have actually been added, although the owner entity can now be accessed with the **OwnerEntity** keyvalue and m_fFlags can now be accessed with the aptly named **m_fFlags** keyvalue, but neither are actually used in any base FGD classes to avoid clutter.