execFSM: Difference between revisions
Jump to navigation
Jump to search
PhilippRauch (talk | contribs) mNo edit summary |
Lou Montana (talk | contribs) m (Text replacement - "\| *((\[\[[a-zA-Z0-9_ |()]+\]\],? ?)+) * \}\}" to "|seealso= $1 }}") |
||
(44 intermediate revisions by 11 users not shown) | |||
Line 1: | Line 1: | ||
{{ | {{RV|type=command | ||
| arma2 | | arma2 | ||
|1.00 | |1.00 | ||
| | |gr1= Program Flow | ||
| ''' | | Execute scripted [[FSM]] and return the FSM handle or 0 when failed. The FSM file is first searched in the mission folder, then in the campaign scripts folder and finally in the global scripts folder. Argument (if any) are available in <tt>_this</tt> variable inside FSM. Variables set inside FSMs can be read/modified externally, using [[setFSMVariable]] and [[getFSMVariable]] commands.<br> | ||
<br> | |||
The return value is the FSM handle; it can be used to determine (via [[completedFSM]]) when the FSM has finished. | |||
{{Feature|arma3|In Arma 3, the FSM handle is also available within the FSM through the <tt>_thisFSM</tt> variable.}} | |||
<br> | |||
Scripted FSMs are added into the scheduler just like [[exec]] scripts, [[execVM]] scripts and [[spawn]] scripts.<br> | |||
To see what FSMs are currently in the scheduler, use [[diag_activeMissionFSMs]] command. | |||
{{Feature|important|While the code placed into any of the sections of FSM cannot be suspended ([[canSuspend]] is false), the FSM itself is suspended every simulation between the state's <tt>init</tt> and <tt>precondition</tt> (exception is the '''init state'''). This is the only place where scripted FSM is suspended/resumed. | |||
The usual difference between the state's <tt>init</tt> and <tt>precondition</tt> is 1 frame but if the scheduler is busy it can take longer. See [[FSM]] for more information about FSM's structure.}} | |||
| | | arguments [[execFSM]] fsmFilePath | ||
| | |p1= arguments: [[Anything]] - Arguments accessible as <tt>_this</tt> in the FSM | ||
| | |p2= fsmFilePath: [[String]] - file with FSM code | ||
| [[Number]] | | [[Number]] - FSM handle | ||
|s2= [[execFSM]] fsmFilePath | |||
| | |p21= fsmFilePath: [[String]] - file with FSM code | ||
| r2= [[Number]] - FSM handle | |||
| [[ | |x1= <code>_id = [[player]] [[execFSM]] "test.fsm";</code> | ||
| | |x2= <code>_handle = [_a, _b, _c] [[execFSM]] "test.fsm";</code> | ||
|x3= <code>_handle = [[execFSM]] "test.fsm";</code> | |||
|seealso= [[FSM]], [[FSM Editor Manual]], [[execVM]], [[call]], [[spawn]], [[exec]], [[commandFSM]], [[completedFSM]], [[doFSM]], [[getFSMVariable]], [[setFSMVariable]] | |||
}} | }} | ||
{{GameCategory|arma2|Scripting Commands}} | |||
{{GameCategory|tkoh|Scripting Commands}} | |||
[[Category:Scripting Commands | {{GameCategory|arma3|Scripting Commands}} | ||
[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]] |
Revision as of 00:42, 17 February 2021
Description
- Description:
- Description needed
- Groups:
- Program Flow
Syntax
- Syntax:
- Syntax needed
- Parameters:
- arguments: Anything - Arguments accessible as _this in the FSM
- fsmFilePath: String - file with FSM code
- Return Value:
- Return value needed
Alternative Syntax
- Syntax:
- execFSM fsmFilePath
- Parameters:
- fsmFilePath: String - file with FSM code
- Return Value:
- Number - FSM handle
Examples
- Example 1:
_id = player execFSM "test.fsm";
- Example 2:
_handle = [_a, _b, _c] execFSM "test.fsm";
- Example 3:
_handle = execFSM "test.fsm";
Additional Information
- See also:
- FSMFSM Editor ManualexecVMcallspawnexeccommandFSMcompletedFSMdoFSMgetFSMVariablesetFSMVariable
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note