Simulation Core: Difference between revisions

From Tygron Preview Support Wiki
Jump to navigation Jump to search
(Created page with "Each Project in the Tygron Engine has its own Simulation Core responsible for executing updating the excel, triggers and grid overlays. Below an overview of each step executed: A update is triggered either by a User, API call or when the state changes due to e.g. a new building when "auto update" is active. ==Steps== * *")
 
No edit summary
Line 1: Line 1:
Each Project in the Tygron Engine has its own Simulation Core responsible for executing updating the excel, triggers and grid overlays. Below an overview of each step executed:
Each Project in the Tygron Engine has its own Simulation Core responsible for executing updating the excel, triggers and grid overlays. Below an overview of each step executed:


A update is triggered either by a User, API call or when the state changes due to e.g. a new building when "auto update" is active.
An update is initiated by a User, an API call, or when the state changes, such as the addition of a new building, while "auto update" is enabled. Note that the initial project creation must be finished first.


==Steps==
==Steps==
*  
* First API [[Trigger]] (with timing BEFORE) are executed.
*
* Then all TQL updates (with timing BEFORE) from [[Indicators]] and [[Panels]].

Revision as of 10:39, 14 November 2024

Each Project in the Tygron Engine has its own Simulation Core responsible for executing updating the excel, triggers and grid overlays. Below an overview of each step executed:

An update is initiated by a User, an API call, or when the state changes, such as the addition of a new building, while "auto update" is enabled. Note that the initial project creation must be finished first.

Steps

  • First API Trigger (with timing BEFORE) are executed.
  • Then all TQL updates (with timing BEFORE) from Indicators and Panels.