Template:I BaseEntity (Source 2): Difference between revisions
Jump to navigation
Jump to search
Gameplayer (talk | contribs) m (Moved template to category Input templates) |
m (→top: Substituted IO templates) |
||
Line 8: | Line 8: | ||
</noinclude><!-- | </noinclude><!-- | ||
-->{{minititle|Base}} | -->{{minititle|Base}} | ||
{{ | {{I|RunScriptFile|Load and execute a script file.}} | ||
{{ | {{I|RunScriptCode|Execute a fragment of script code.}} | ||
{{ | {{I|CallScriptFunction|Call a script function.}} | ||
{{ | {{I|CallPrivateScriptFunction|Calls a script function from this entity's private script scope.}} | ||
{{ | {{I|CallGlobalScriptFunction|Calls a script function in the global script scope.}} | ||
{{ | {{I|Kill|Removes this entity from the world.}} | ||
{{ | {{I|KillHierarchy|Removes this entity and all its children from the world.}} | ||
{{ | {{I|AddOutput|Adds an entity I/O connection to this entity. Parameter format: OutputName→TargetName→InputName→Parameter→Delay→MaxRefires}} | ||
{{ | {{I|FireUser1|to=FireUser4|Fires the respective<code>OnUser</code>outputs; see [[User Inputs and Outputs]].}} |
Latest revision as of 12:52, 21 April 2025
This template is a holder for inputs that are assigned to all entities in Source 2 games.
Currently script functions are still present in Counter-Strike 2 and the respective .fgd files, despite the majority of the VScript system being disabled in the game.
Base:
- RunScriptFile
- Load and execute a script file.
- RunScriptCode
- Execute a fragment of script code.
- CallScriptFunction
- Call a script function.
- CallPrivateScriptFunction
- Calls a script function from this entity's private script scope.
- CallGlobalScriptFunction
- Calls a script function in the global script scope.
- Kill
- Removes this entity from the world.
- KillHierarchy
- Removes this entity and all its children from the world.
- AddOutput
- Adds an entity I/O connection to this entity. Parameter format: OutputName→TargetName→InputName→Parameter→Delay→MaxRefires
- FireUser1 to FireUser4
- Fires the respective
OnUser
outputs; see User Inputs and Outputs.