This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| format:esd [2025/04/30 02:38] – [Engine Details] metalcrow | format:esd [2025/05/04 21:58] (current) – [Engine Details] metalcrow | ||
|---|---|---|---|
| Line 51: | Line 51: | ||
| ===== Engine Details ===== | ===== Engine Details ===== | ||
| - | When ezstate wants to perform an animation (action), it calls EzStateActionEvent_Execute_By_CommandId | + | EzState:: |
| - | This is called for each ActionEvent in EzState:: | + | This then calls the following functions to process the sections of the state: parseEzStateConditions, |
| - | That is called from parseEzStateEntryCommands-> | + | These take a state, and run the corresponding sections |
| - | Example: State 0 (the idle state), checks | + | For executing the bytecode for each state, this maps to the executeEzStateBytecode function. The [[https:// |
| + | |||
| + | * For example, when ezstate wants to do something related to the game state, it calls a function using an ID. This maps to EzStateActionEnv_QueryOperation | ||
| + | |||
| + | |||
| + | Example: State 0 (the idle state), checks | ||
| ===== Editors ===== | ===== Editors ===== | ||