This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| format:esd [2025/02/24 23:41] – created admin | format:esd [2025/05/04 21:58] (current) – [Engine Details] metalcrow | ||
|---|---|---|---|
| Line 49: | Line 49: | ||
| The current list of labeled states is in [[esd-state-list|ESD State List]] | The current list of labeled states is in [[esd-state-list|ESD State List]] | ||
| + | ===== Engine Details ===== | ||
| + | |||
| + | EzState:: | ||
| + | |||
| + | This then calls the following functions to process the sections of the state: parseEzStateConditions, | ||
| + | |||
| + | These take a state, and run the corresponding sections for this state. For each command in the section, it calls parseEzStateCommandCall | ||
| + | |||
| + | 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 the conditions of state B0D8 every frame, and that condition checks if the player has requested to roll and returns a new state if so. A breakpoint right after parseEzStateConditions-> | ||
| ===== Editors ===== | ===== Editors ===== | ||